How to Handle a Difficult Interviewer (Silent, Rude or Distracted)
What to do when an interviewer is silent, cold, interrupting, distracted or openly skeptical: why it happens, how to stay composed, and exact phrases that keep the interview on track.
LiveHint.ai team · · 4 min read
Most interviewers are friendly, or at least neutral. But sooner or later you'll meet one who isn't. They don't smile, give no feedback, interrupt you mid-sentence, check their phone, or seem to doubt everything you say.
It throws people off because it feels personal. Usually it isn't. And how you handle it is often part of what's being assessed, whether the interviewer intends it or not.
Why interviewers seem difficult
Before assuming the worst, consider the common, boring explanations:
- They're tired. They may have done four interviews today on top of their real job.
- They're following a rubric. Some companies train interviewers to stay neutral so they don't give hints.
- They're taking notes. Typing while you speak looks like inattention but is often the opposite.
- They're inexperienced. Many engineers interview with little or no training.
- They're testing you. Occasionally an interviewer deliberately pushes back to see how you handle pressure or disagreement.
In almost every case, the right response is the same: stay calm, stay clear, and keep going.
The silent interviewer
You finish an answer and get nothing. No nod, no follow-up, just silence.
What to do: Don't fill the silence by repeating yourself or adding more detail. Check in instead:
- "Does that answer your question, or would you like me to go deeper on any part?"
- "Should I go into the technical details, or is the overview enough?"
In a coding round, silence usually means they're letting you work. Keep thinking out loud so they can follow your reasoning. If you need a hint, ask directly: "I'm deciding between a heap and sorting here. Is there anything about the constraints I should consider?"
The interrupter
You're halfway through a story and the interviewer cuts in with a different question.
What to do: Let it go. Answer the new question. An interruption usually means they've heard enough on that point, or your answer was running long. Take it as a hint to be more concise, not as an insult.
If they cut you off before something important, you can return to it briefly: "Just to finish the earlier point, the result was a 30% drop in errors." Then move on.
Our guide on how long interview answers should be can help you avoid getting interrupted in the first place.
The skeptic
"Are you sure that would work?" "That seems inefficient." "Why wouldn't you just use X?"
What to do: Don't get defensive, and don't immediately cave. Treat it as a technical conversation:
- If you're confident, explain your reasoning calmly: "I think it holds because the input is sorted, so we only ever move the pointer forward. Let me walk through an example."
- If they've found a real problem, acknowledge it: "You're right, that breaks with duplicates. Let me adjust."
- If you're not sure, say so and reason it through: "I'm not certain. Let me think through the case where the list is empty."
Changing your mind for a good reason is a strength. Changing it just because you were challenged is not. Interviewers who push back often want to see whether you can tell the difference.
The distracted interviewer
They're looking at another screen, checking messages, or seem only half present.
What to do: Stay professional and keep your answers tight. Shorter answers with clear structure ("There were three parts to this...") are easier to follow for someone who's distracted. If they ask you to repeat something, do it without any irritation.
If the distraction is extreme, for example they leave the call for several minutes, it's fine to mention it neutrally to the recruiter afterwards. Don't mention it during the interview.
The cold or rude interviewer
Most "rude" interviewers are just blunt or awkward. Occasionally one is genuinely dismissive.
What to do: Stay polite and focus on the questions. Don't match their tone. Your goal is to give the rest of the panel a good report on you, and to leave with your own assessment of the company intact.
If an interviewer crosses a line, such as asking illegal questions about age, family plans, religion or health, or being openly insulting, you can decline politely ("I'd rather focus on my experience for this role") and report it to the recruiter afterwards. You can also reasonably decide that you don't want to work there.
Keep your own state steady
A difficult interviewer is stressful, and stress makes you rush, ramble or blank. A few things help:
- Pause before answering. Two seconds of silence feels long to you and normal to them.
- Slow down. Most people speed up under pressure.
- Use structure. "There are two parts to my answer" gives you a map to follow.
- Don't read their face. Lack of feedback isn't negative feedback.
- Reset between questions. One bad exchange doesn't decide the interview.
For more on managing nerves, see our guide to interview anxiety in live coding.
Remember: you're interviewing them too
A consistently difficult interviewer tells you something about the team, but one interview is a small sample. Use your own questions at the end to learn more: "How does the team handle disagreements in design reviews?" says a lot about the culture. Our list of questions to ask the interviewer has more.
Practice under pressure
It's much easier to stay calm with a tough interviewer if you've experienced one before. In LiveHint's AI mock interview, you can choose a tougher bar-raiser interviewer who pushes back on vague answers and asks hard follow-ups. Rehearsing against that makes a real skeptic far less unsettling.
Keep reading
4 min read
How to Stop Freezing in Live Coding Interviews
Why your mind goes blank in live coding interviews, and practical techniques to stay calm before, during and after: preparation habits, scripts for when you're stuck, and how to recover from mistakes.
- coding interview
- interview anxiety
- interview tips
- software engineering
13 min read
STAR Method Examples: 12 Interview Answers That Work
Twelve full STAR method examples for software engineers, from conflict and failure to tight deadlines and production incidents, plus a checklist to adapt them.
- behavioral interview
- STAR method
- interview tips
- software engineering