Voca Voca

Every Line of Your CV Is an Interview Question

2026-08-07 · 9 min read

There is a step between finishing a CV and sitting the interview that almost nobody does, and it is the cheapest preparation available: read your own CV the way the interviewer will.

Because that is where the questions come from. Not from a generic list — from your document, line by line, especially the lines with numbers in them.

Why your CV is the question bank

Interviewers are usually busy and often under-prepared. Ten minutes before the call they open the CV and mark the things they want to ask about. The selection is predictable:

That is close to the whole interview. Which means you can predict most of it from a document you wrote yourself.

The compression problem

Here is why this catches out capable people.

A CV bullet is extremely compressed. "Led the migration of a payments platform from a monolith to event-driven services, cutting checkout latency 40%" is nineteen words standing in for perhaps six months of work, forty decisions, two arguments, and one incident at 3am.

Writing that sentence is a compression skill. Answering "walk me through that migration" is a decompression skill — expanding it back into two minutes of structured, spoken narrative. These are genuinely different abilities, and being good at the first tells you nothing about the second.

The failure mode is specific and common: you know the project completely, you start answering confidently, and about forty seconds in you realise you are three levels deep in a technical detail with no idea how to get back out. You trail off. The interviewer forms an impression that has nothing to do with your actual competence.

Audit your own CV in fifteen minutes

Print it, or open it beside a blank document. Go line by line and mark every bullet with one of three labels:

Green — I could talk about this for two minutes right now, with a beginning, a middle, and a result.

Amber — I know this well but have never said it out loud. I would probably ramble.

Red — I would struggle. It was a while ago, or I have overstated it, or I genuinely cannot remember the numbers.

Most people find their CV is roughly 20% green, 60% amber, and 20% red. The amber lines are the ones that lose interviews, because you never notice they are a problem — you do know the material, so nothing feels wrong until you are speaking.

For the red lines, you have two honest options: learn the detail properly, or take the line off the CV. Leaving a claim you cannot defend on the page is setting a trap for yourself.

The five follow-ups to prepare for any bullet

For every green and amber bullet, an interviewer can reasonably ask:

  1. "Walk me through that." — the two-minute narrative
  2. "Why did you do it that way?" — the alternatives you rejected, and why
  3. "What went wrong?" — there is always something; having no answer reads as either dishonesty or lack of reflection
  4. "What was your specific contribution?" — especially for anything phrased as "we" or "the team"
  5. "How did you measure that?" — for every single number on the page

Question five is the one that punishes invented metrics. If your CV says 40% and you cannot say what the baseline was, over what period, and how it was measured, the number does more damage than its absence would have.

A structure for the two-minute answer

Most CV-derived questions are asking for a story, and stories need shape. Situation, what you did, result — roughly the STAR frame, without being mechanical about it:

Situation (20 seconds). "Checkout was a single Rails monolith, and p95 was about 1.9 seconds. The provider calls were synchronous, so a slow bank meant a slow checkout for everyone."

Action (60–80 seconds). "I pulled settlement out into a queued worker first, because it was the biggest contributor and the easiest to make idempotent. The hard part was ordering — we needed exactly-once settlement, so I built a reconciliation step keyed on the provider's transaction ID rather than trusting callback order."

Result (20 seconds). "p95 came down to about 1.1 seconds over two months. The unexpected win was that double-charge incidents went to zero, because the idempotency key fixed a class of bug we had been chasing separately."

Note what makes it good: it names a specific technical decision, admits what was hard, and ends with a result including something that surprised them. That is a memorable answer, and it came directly off one CV bullet.

Practise out loud. Actually out loud.

This is the part people skip, and it does not work when skipped.

Rehearsing in your head trains the wrong thing. Your brain shortcuts — it marks a section as "and then I'd explain the architecture" and moves on, because you know what you mean. Out loud, that shortcut has to become forty seconds of real sentences you do not have yet. You only discover the gap by speaking.

Three ways to do it, in increasing order of usefulness:

Talk to yourself. Genuinely better than nothing. Set a timer for two minutes per bullet and speak until it goes off. You will hear yourself trail off, which is the information you wanted.

Record yourself. Play it back. Painful and effective — you will hear the filler, the circling, and the answers that never reached a result.

Have someone ask you. The best version, because real questions arrive in an order you did not choose and follow-ups you did not anticipate. The friction is finding someone willing to sit through it more than once, which is why most people do it approximately zero times.

Do this the day you finish the CV

The best moment for this audit is right after writing the document, while every project is still loaded in your head. Not the night before the interview, when your options narrow to panic.

Write the CV. Then take fifteen minutes to mark it green, amber, red. Then start saying the amber ones out loud until they turn green.

The document gets you into the room. The decompression gets you the offer, and it is the half almost nobody rehearses.

Practise it out loud

Voca runs a real spoken mock interview for the role you are applying for, then scores it and tells you which answers were weak. Your first 10-minute session is free.

Try a mock interview free