The most common way candidates lose an offer early is giving the hiring manager's answer to the recruiter, or the recruiter's answer to the hiring manager.
They ask overlapping questions — tell me about yourself, why this role, walk me through your experience — which makes it feel like one conversation held twice. It isn't. The two people are deciding different things, on different evidence, with different consequences for getting it wrong.
| Recruiter screen | Hiring manager interview | |
|---|---|---|
| What they're deciding | Should this person take up the team's time | Do I want this person on my team |
| What they're afraid of | Passing someone who wastes four people's afternoon | Hiring someone they'll have to manage out |
| Cost of a wrong yes | An hour of someone else's time | Six months of theirs |
| What they can judge | Level, motivation, logistics, communication | The actual work, and whether they'd enjoy the working relationship |
| What a good answer sounds like | Short, concrete, easy to relay to someone else | Specific, with the reasoning and the trade-off visible |
| What ends it | Vagueness, mismatched level, unresolved logistics | Answers with no decisions in them |
What the recruiter is actually doing
A recruiter screen is not a weaker version of a technical interview. It's a different job: deciding whether to spend other people's time on you, and — this is the part candidates miss — assembling the sentence they'll use to introduce you.
That reframes everything. The recruiter is going to summarise you in two or three lines to a hiring manager who has not read your CV closely. Everything you say is being filtered for whether it survives being repeated by someone who doesn't share your vocabulary.
Which is why the most common recruiter-screen failure is depth. A candidate answers "walk me through your last project" with four minutes of architecture, and the recruiter — who cannot evaluate any of it — writes down "worked on backend stuff, seemed technical". You gave them nothing to sell.
Answering at technical depth
“I worked on migrating our monolith to event-driven services, mostly around the ordering domain — we had consistency problems with the outbox pattern and I redesigned how we handled idempotency keys.”
All true and probably impressive to the right person. The recruiter is not that person, and none of it survives the handoff. What reaches the hiring manager is a shrug.
Answering at summary depth
“I spent last year breaking up a system that couldn't handle our order volume. I owned the piece that stopped duplicate charges — it was the part most likely to lose real money, which is why it was mine. Happy to go deeper on the technical side if that's useful.”
Scale, ownership, stakes, one sentence each — and an offer to go deeper that lets the recruiter say no. This is the version that gets written down and repeated accurately.
The offer at the end matters more than it looks. It signals you have depth without spending the screen on it, and it hands the recruiter control of the conversation, which is what they need to get through their list.
What the hiring manager is actually doing
The hiring manager has the opposite problem. They can evaluate the work, so summary answers read as thin. What they're deciding is whether they want to be responsible for you — and the thing they're listening for is decisions.
Not what you worked on. What you chose, what you gave up, and what you'd do differently. A candidate who describes three projects without a single decision in them sounds like someone things happened to.
The other half is quieter: they're imagining disagreeing with you. Most hiring managers have been burned by someone who was technically strong and exhausting to work with, so a large part of that hour is spent finding out how you behave when someone pushes back. That's why they interrupt, and why they occasionally argue with an answer they actually agree with.
The same question, scored twice
Four questions come up in both rounds. The words don't change; the right answer does.
"Tell me about yourself." To the recruiter: ninety seconds, ending on why you're talking to them specifically. To the hiring manager: the same arc, but weighted toward the work most like the job they're hiring for, and ending on a decision you made rather than a title you held.
"Why this role?" The recruiter is checking that you won't drop out in week three, so name something concrete about the company that isn't its funding stage. The hiring manager is checking whether the job you want is the job that exists — the strongest version says what you want to be doing daily, even where that's narrower than the posting.
"Walk me through your experience." For the recruiter, this is a level check: scope, team size, ownership. For the hiring manager, it's a depth check, and you should expect to be stopped and asked to expand on one thing. Getting stopped is a good sign.
"What are you looking for in terms of compensation?" Only the recruiter can act on this, and they usually ask early because it's the cheapest way to end a mismatch. Have a range and a reason for it before the call.
The rule that covers all four: the recruiter needs your answer to be portable — short enough and plain enough to survive being repeated. The hiring manager needs it to be defensible — specific enough to be pushed on without falling apart. Almost every awkward moment in an early-stage interview comes from giving one of those when the other was needed.
The handoff nobody tells you about
Between the two conversations, something gets written down. Usually a few lines in an applicant tracking system, sometimes a message in a channel: level, motivation, salary expectation, and a sentence about how you came across.
The hiring manager reads that before meeting you, and it sets the frame you have to work inside. If it says "strong communicator, wants more ownership, might be slightly junior for the level", the hiring manager will spend their hour testing whether you're junior — regardless of what you'd rather talk about.
Two practical consequences. First, in the recruiter screen, say the thing you want repeated. Explicitly, in plain words, more than once if necessary. Second, if you sense a misread — that they've filed you at the wrong level or misunderstood what you own — correct it there, in that call, not later. It's cheap to fix before it's written down and expensive afterwards.
If you're preparing the screen itself in detail, there's a full walkthrough here: how to ace the recruiter screen. It's written around a PM example, but the structure applies to any role.
What this looks like from the other side
Worth knowing: the recruiter is being measured too. Their metrics are things like how many of the people they pass get an offer, and how quickly roles close. A recruiter who passes weak candidates gets ignored by hiring managers; one who over-filters gets blamed for an empty pipeline.
That's useful to you, because it means the recruiter is not an obstacle — they're looking for someone they can confidently advocate for. Making yourself easy to advocate for is a strategy, not a compromise. If you're curious what the rest of that job looks like, the questions they get asked in their own interviews are here: Recruiter Interview Questions.
Practical target: write your "tell me about yourself" once, then say it out loud twice — once as if to someone who can't evaluate your technical work, once as if to the person who'd manage you. If the two versions come out the same, one of them is wrong for its audience, and it's almost always the recruiter version that needs to get simpler.
