You’re going to blank on a question. Not might. Will. What matters isn’t the gap in your knowledge. It’s the 4 seconds after you realise the gap exists.
The Blank, the Panic, and What Actually Costs You the Offer
The interviewer asks something. A framework you’ve heard of but can’t place, a scenario you’ve never faced, a term that sounds familiar but the definition is gone. Like a word stuck on the tip of your tongue except the stakes are ₹6 Lacs per annum and your mother already asked about this interview twice this morning.
Your face gets warm. Brain goes quiet. Not dramatically quiet. That useless kind of quiet, like a browser tab that’s frozen mid-load.
And then, almost every time, the panic makes you do something worse than just not knowing.
Most candidates start rambling. Talking in circles hoping something useful accidentally falls out. The interviewer has watched this happen 200 times. It doesn’t buy time. It confirms the gap and adds a second problem on top: this person can’t sit with discomfort for 5 seconds without filling the air.
Some candidates fake it. This is worse. A guy interviewing at a fintech in Bandra confidently described a concept that doesn’t exist. Good vocabulary. Steady voice. The interviewer let him finish the whole explanation, then said: “That’s not a real thing.” Conversation over. Not because of the gap. Because he decided to lie about it, and if he’ll lie about a definition in an interview room, what does he do when a deliverable is behind schedule?
Here’s what nobody tells you before your first interview: the interviewer already knows you don’t know. They knew the moment your expression changed. Most interviewers decide whether you know the answer within 2 seconds of asking the question. Everything after that is them watching how you handle it.
So handle it.
“I’m not sure about that, but here’s how I’d approach it.” Thirteen words. No recruiter has ever, in the history of hiring in India or anywhere else, rejected someone for that sentence. What gets people rejected is the performance that follows the panic. The ramble. The fake. The freeze where your eyes drop to the table and the energy in the room shifts from “interview” to “rescue.”
But delivery matters here. “I don’t know” mumbled with a shrug is apathy. “I’m not sure, but let me think through this” while leaning forward and actually working through it? Completely different read. The interviewer sees someone who’d flag a problem early at work instead of hiding it until a client meeting explodes.
The next move, and this is where people who’ve done 3 or 4 interviews start separating from people who’ve done 1, is saying what you do know. Partial knowledge counts for a lot more than candidates realise. Someone interviewing for a DevOps role in Pune got asked about Kubernetes. Hadn’t used it. Said so. Then: “I’ve used Docker for 14 months and I understand how container orchestration works conceptually. Give me a week with the docs and a sandbox environment and I’d be functional.” That’s not a dodge. That’s a map. Here’s where knowledge stops, here’s where it’d resume, here’s the timeline. Interviewers at product companies in Hinjewadi hear that kind of answer maybe once in 15 interviews. Maybe.
Asking a clarifying question works too, but it’s not always what people think it is. “Could you clarify whether you’re asking about implementation or strategy?” isn’t stalling. It’s precision. Half the time the blank happened because the question was ambiguous, not because the candidate was underqualified. But asking “Could you repeat the question?” when you clearly heard it and just don’t know the answer? That’s stalling. The interviewer knows the difference.
One thing that never works: “That’s a great question.” Skip it. Every candidate uses it. Every interviewer hears it as a stall. Just go straight to honest.
And something worth mentioning even though it breaks the flow of the advice a little. Sometimes the blank isn’t about knowledge at all. You took a 6 AM Rajdhani. You’re in round 3 back-to-back and it’s 4 PM and you skipped lunch and your brain is running on Parle-G and lukewarm coffee from the office pantry. That kind of blank feels the same but it isn’t. “I think I know the answer to this but my mind is blanking, could I come back to it after the next question?” Most interviewers say yes. The ones who won’t were never going to give you a fair shot regardless.
What about the “that’s a great question” cousins? “Hmm, interesting” before answering. “Let me think about that for a second” said 4 times in the same interview. “Could you give me a moment?” once is fine. Twice is pushing it. Three times and the interviewer’s mental scorecard is already being filled in. These aren’t tips from a manual. This is pattern recognition from watching hundreds of interviews go sideways over the same small things.
The sentence candidates don’t want to hear: the person who blanked and recovered well almost always outscores the person who answered everything but answered it generically. Because the blank forced a real moment. And real moments are rare in interviews.
Technical Blanks vs Behavioural Blanks
Different animals.
Technical blanks are simpler. When you don’t know a caching algorithm or a SQL join type, walk through your reasoning. “I know this relates to how the system handles concurrent requests, so I’d start with the locking mechanism.” You might not arrive anywhere useful. Doesn’t matter. The interviewer saw your instinct. At startups in Indiranagar and HSR Layout where the team is 8 people and everyone’s solving problems that don’t have Stack Overflow answers yet, that instinct is the hire.
A business analyst candidate in Bangalore was asked about a SQL join she hadn’t used. She drew the line: “I’ve used inner joins and left joins for reporting dashboards. This one I’d need to learn.” The hiring manager mentioned that answer specifically in the offer feedback. Not because the gap didn’t matter. Because the honesty told him she’d raise a flag early instead of shipping broken queries and hoping nobody checks.
Behavioural blanks are harder because there’s no correct answer. Only real and fake. “Tell me about a time you dealt with a difficult team member” doesn’t have a model response. When you blank on this, it’s usually because you’re searching for the perfect story.
Stop. Pick something true. A college group project where someone ghosted and you rebuilt their section at 2 AM the night before. A colleague at PQR Corporation who kept missing standup calls and you had to bring it up with the team lead. It doesn’t need to be impressive. Interviewers can tell real from rehearsed in about 10 seconds, the same way you can tell a Zomato review written by a real customer from one written by the restaurant owner’s cousin.
One thing that genuinely worries interviewers but nobody discusses. If you can’t think of a single conflict or challenge from your entire past? That’s a bigger concern than any technical blank. It reads as either avoidance (you’ve dodged every hard thing) or lack of self-awareness (hard things happened and you didn’t register them). Both are harder to fix on the job than a missing Python library.
FAQ’S About Handling Unknown Interview Questions
What should you say when you don’t know the answer in an interview? “I’m not sure about that, but here’s what I do know” or “I haven’t encountered that, but here’s how I’d approach it.” Honesty plus reasoning. Every industry. Every role level. Every city.
Will admitting you don’t know cost you the job? Almost never. One honest blank with a calm recovery weighs less than you think across a 40-minute interview. What costs you the job is when the panic from one blank bleeds into every answer after it. That spiral, not the gap, is what interviewers remember when they’re comparing 4 candidates at 6 PM over chai.
Is it okay to ask the interviewer for a hint? Depends. Conversational interview? Yes. Structured panel with a scoring rubric? Probably not, the interviewer might not be allowed to help even if they want to.
What if you blank on multiple questions in the same interview? Treat each one individually. The interviewer is.
All the Best!
