How do you handle a prospect who goes silent after a demo?
Assesses fundamental understanding of Sales conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Silence usually means something changed, not that they dislike me. I do not flood their inbox.
First I send a short, low pressure note that gives them an easy way to reply: "Have you deprioritised this, or is there something I can clarify?" I offer a specific reason to reconnect, such as a relevant case study or a change in terms.
If there is still no response, I try a different channel, a call, a message or a brief voicemail, and I space contacts out. I also check whether the deal was ever real. Did we confirm a problem and a timeline, or did I mistake politeness for interest?
After three or four attempts over a few weeks I move them to nurture and keep adding value through useful content. Many come back when budget or priorities shift.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.