What's actually going through their head while you talk — from someone who's sat in that chair 50+ times.
I've conducted more than fifty interviews. Backend roles, mostly — junior engineers fresh out of college, senior people with a decade on me, the occasional brilliant candidate who completely fell apart in front of me for no good reason.
And here's the thing nobody tells you when you're the one being interviewed: the person across the table is not the cold, objective judge you imagine. They're a tired human with three more meetings today, a half-finished coffee, and one quiet fear running in the background the entire time.
If you understood what was actually happening in their head, you'd prepare completely differently. So let me show you.
The decision happens faster than you think
I made up my mind about most candidates in the first five minutes.
I'm not proud of it, and good interviewers fight hard against it, but it's true and the research backs it up. We form a gut impression almost immediately, and then we spend the rest of the interview unconsciously looking for evidence that confirms it. Psychologists call it confirmation bias. In an interview room it means the first five minutes set a trajectory, and everything after either reinforces it or slowly fights against it.
This sounds unfair. It is. But it's also a gift, because it tells you where to spend your energy.
The opening — how you introduce yourself, how you answer "tell me about yourself," whether you seem comfortable in your own skin — matters far more than its airtime suggests. Most candidates sleepwalk through it, treating it as a warm-up before the "real" questions. It is the real question. By the time you get to the hard technical part, the interviewer has often already decided which way they're leaning. Your job in the back half is usually to protect a good first impression, not to build one from scratch.
So win the opening. Then give them no reason to flip.
They're not hunting for the best — they're avoiding the worst
Here's the reframe that changes everything.
When I interviewed people, I was almost never thinking "is this the best candidate I could possibly find?" I was thinking "will hiring this person make my life easier or harder?"
A bad hire is expensive in a way that's deeply personal to the interviewer. It's months of onboarding wasted. It's awkward performance conversations. It's me having to explain to my manager why I vouched for someone who didn't work out. The downside of a bad hire lands squarely on the person who said yes.
So most interviewers are quietly running a risk-reduction exercise, not a talent search. Every answer you give nudges a mental dial in one of two directions: safer to hire or riskier to hire.
This is why a candidate who is merely solid and completely clear often beats a candidate who is brilliant but erratic. Brilliance with rough edges reads as risk. Competence with calm reads as safety. When you're preparing, stop trying to look like a genius. Try to look like someone who will quietly make the team better and never become a problem. Remove risk at every turn.
They can only judge what you say out loud
This is the one that breaks my heart the most, because I watched it happen again and again.
I have interviewed people who clearly knew the answer — you could see it behind their eyes — and who still failed, because they couldn't get it out of their head and into the room. And I've advanced people who knew slightly less but explained what they did know with such clarity that I trusted them instantly.
An interviewer cannot grade your knowledge. They can only grade your expression of it. Whatever stays trapped in your head, unsaid or mumbled or buried in a tangent, does not exist as far as the evaluation is concerned.
This is why I'm convinced the interview is fundamentally a translation test, not a knowledge test. The skill being measured — whether anyone admits it or not — is your ability to take something you understand and render it clearly, out loud, under pressure, often in a second language. You can be the better engineer and still lose to the better translator.
The fix is not to know more. It's to practice saying what you already know, out loud, until the path from thought to sentence is smooth and fast. Almost nobody does this. They rehearse silently in their head, which is useless, because the head is a generous grader and the room is not.
The interviewer is a nervous human too
We forget this completely when we're the ones sweating.
The person interviewing you is often not a trained interviewer. They're an engineer who got pulled into a hiring loop, who would rather be coding, who isn't entirely sure what they're allowed to ask, and who is a little anxious about getting it wrong themselves.
And critically: your discomfort is contagious. When you freeze and the silence stretches, the interviewer feels that awkwardness too. They start wondering whether to throw you a lifeline, whether they asked a bad question, whether this is going to be a painful forty minutes. When you stay calm and think out loud — "okay, let me work through this, my first instinct is X, though I want to check Y" — the tension drains out of the room for both of you. They relax. And a relaxed interviewer starts, almost without noticing, to root for you.
That's the goal you should actually be chasing: not to dazzle them, but to get them on your side. Make them want you to do well. A candidate the interviewer is silently cheering for gets the benefit of the doubt on every borderline moment — and there are always borderline moments.
What actually makes them root for you
After fifty-plus of these, the candidates I walked away wanting to hire had very little in common technically. But they shared a few human things.
They were easy to follow. They structured their answers so I never had to work to understand them. They made their thinking visible instead of presenting finished conclusions out of nowhere. When they didn't know something, they said so plainly and then reasoned toward it, instead of bluffing — bluffing is the single fastest way to lose an experienced interviewer's trust. They asked clarifying questions before diving in, which signals exactly the instinct you want on a real team. And they were memorable in one specific way: one strong story, one sharp insight, one moment of genuine enthusiasm that I could carry into the debrief and use to advocate for them.
Because that's the last thing worth understanding. After you leave, the interviewer often has to argue for you to other people — in a debrief, on a hiring panel, in a Slack thread. You want to hand them ammunition. The candidate who gave me one clear, repeatable reason to say yes was far easier to champion than the one who was vaguely fine across the board.
How to use all of this
None of this is about gaming anyone. It's about understanding the actual game so you can show your real ability instead of letting it get lost in translation.
Win the first five minutes, because the decision starts forming faster than you think. Spend the rest removing risk rather than performing brilliance. Say what you know out loud, clearly, because nothing in your head counts until it reaches the room. Stay calm so the human across from you can relax and start rooting for you. And leave them with one clear reason to advocate for you when you're not there to do it yourself.
The best candidates aren't the ones who beat the interview. They're the ones who let the interviewer see clearly what was true all along.
That's the whole reason I'm building Intervues — a voice interviewer patient enough to let you practice exactly this translation, out loud, before it counts. Because an interview isn't a test to be beaten. It's the first conversation of the job. Earned, not gamed.