The technical phone screen: what the first thirty minutes decide
The technical phone screen is the cheapest round the company runs, and it exists to answer one question: is it worth spending four engineers' afternoons on this person? Nothing about it rewards depth for its own sake. Almost everything about it rewards being clear.
What usually happens in the half hour
- Five minutes — introductions and the role. Short.
- Ten to fifteen minutes — your own experience, probed. Usually one project from your CV, taken apart.
- Ten minutes — one small technical question. Sometimes code in a shared document, sometimes a design sketch, sometimes fundamentals.
- Five minutes — your questions, which are also part of the assessment.
The part that actually eliminates people
It is not the coding question. It is the project conversation, and specifically one failure: being unable to say what you personally did.
Have a three-sentence version of one project ready. What it was, what was hard about it, what you did about the hard part. First person singular throughout. Then be ready for the three questions that always follow:
- "Why did you do it that way?" — they want a trade-off, not a justification. Name what you gave up.
- "What would you change now?" — "nothing" is the worst available answer. Have one honest regret with a reason.
- "What broke?" — a real incident, what it looked like in production, and how you found it.
An engineer can tell within two minutes whether you built the thing or sat near it. That is genuinely all this section measures.
The coding question you cannot run
Phone-screen code is usually written somewhere without execution — a shared document, sometimes literally dictation. That changes the tactics.
- Restate the problem in one sentence before writing anything, so you do not solve the wrong one.
- Ask about input size. It tells you which complexity is expected, and asking is itself a signal.
- Talk while you type. On a call, silence is indistinguishable from being lost.
- Walk one example through the finished code, out loud. Since nothing runs, that trace is the only proof the thing works — and it catches the off-by-one you were about to ship.
The logistics people underestimate
Take the call somewhere quiet with a headset, not on speaker in a kitchen. Keep the job description open, plus your own CV — you will be asked about a line from it and "let me remember" costs you more than it should.
If there is a shared document, open it before the call rather than during it. Three minutes of "can you see my cursor" comes out of your coding time, not theirs.
Your questions are scored too
"What does the on-call rotation look like?", "what is in flight for this team this quarter?", "what does the code review process look like day to day?" Those read as someone who has done the job. "What is the culture like?" reads as someone filling a slot.
And ask what the next round contains. It is a perfectly normal question, and the answer tells you exactly what to prepare for.
FAQ
How long is a technical phone screen?
Usually thirty minutes, occasionally forty-five. The compressed timing is why concise project answers matter more here than in any later round.
Will there be coding on a phone screen?
Often, but small — a shared document or a short fundamentals question rather than a full algorithm round. Frequently nothing is executed, so tracing an example out loud is what demonstrates correctness.
Is the phone screen with a recruiter or an engineer?
A technical phone screen is normally with an engineer, sometimes a hiring manager. A recruiter screen is a separate, earlier call about logistics, salary and timing.
What is the most common reason people fail it?
Not being able to explain their own project in plain language — what they personally did, what the trade-off was, and what they would change now.