Walk me through your resume.
answer
- frame the through-line in one sentence
- early roles: a sentence each
- state why every move happened
- half the airtime on the recent role
- land the arc on this job
basics
~20 sTests whether your career reads as a trajectory rather than a list. Narrate roughly three minutes chronologically, give a reason for every move, weight the recent roles heaviest, and land on why this job is the next step.
how to answer
5 beats- frame the whole arc in one sentenceOpen by naming the through-line you are about to demonstrate — the kind of problem you keep moving toward — and say where you will start. This tells the interviewer how to listen and earns you permission to compress the early years.
- early roles, one or two sentences eachCompress everything more than two jobs back into what you learned and what it set up. A role irrelevant to this job gets a clause, not a paragraph. Together the early years should take under a quarter of your airtime.
- each transition, with its reason statedSay why every move happened as you pass it — growth, scope, a relocation, a layoff. An unexplained move is the thing the interviewer writes down. Keep the reason forward-looking and never make a former employer the villain.
- the most recent role in real detailSpend roughly half the total time here: what you own, the scale of it, and one result with a number in it. This is the role you are being hired against, so it should be the only part with real texture.
- land the arc on this roleClose by connecting the direction you have just traced to the job you are interviewing for, in one or two sentences. Then stop and let them ask; do not tack on extra roles or pre-emptive explanations.
your answer
4 story prompts- Write one sentence for why you left each role on your resume, including the current one.
- Name the through-line that connects at least three of your roles, in your own words.
- Mark the two roles closest to this job; they get half your airtime.
- Read it aloud with a timer and cut whatever pushes you past three minutes.
draft and rehearse your own answer in a learn session
go deeper
This prompt probes trajectory and self-awareness: whether your moves add up to a direction or read as drift, and whether you can narrate your own history without defensiveness. The edit you make — what you compress, what you dwell on — is itself the signal about judgment. A strong answer explains every transition and lands on why this role is the next step.
I will keep this to the arc rather than every line. I started as a reporting analyst at a home-goods retailer, mostly SQL, and I got curious about why my numbers were always a day behind. That curiosity is basically what moved me. After fourteen months I joined a data consultancy as a junior data engineer, because I wanted to build the pipelines rather than wait on them. That is where I have spent the last ten months, on a five-person pod delivering a warehouse for a grocery client. I own the ingestion for three of the eleven source systems. The honest part of that project is that we missed our first delivery date by five weeks — the client's order system came out far messier than the spec suggested. I rewrote my loaders to reconcile on a natural key instead of a row hash, and freshness lag on my feeds went from about nine hours to fifty minutes. What I want next is to stay with one product instead of rotating off when an engagement ends. That is what drew me to this role — the pipeline work is the product here, and I would get to see what my own decisions cost six months later.
The arc is short but it points somewhere, and both moves carry a stated reason. This is the spine at about half length: spoken for real it runs near three minutes, and the extra time goes to the current role, never to the first one. Reciting the analyst job's duties instead would flatten it into a list.
The through-line is that I keep landing where data delivery is unreliable, and each move has taken me further up that chain. I started in analytics engineering, writing models on top of somebody else's ingestion. I left after two years because every incident I got paged for was upstream of anything I could change. A data consultancy gave me that upstream half, and I have been there four years — first as an engineer on one account, now leading the delivery pod across three. The part worth dwelling on is the retail account we nearly lost. Scope had grown well past the plan and we had to tell them the date was moving by seven weeks. That conversation is the piece of the job I got measurably better at. I split delivery into a thin freshness-first slice and everything else, so they had hourly inventory data eleven weeks before the full warehouse landed. Median freshness lag across their feeds settled at twenty-two minutes against a four-hour commitment. I am looking to leave the agency model now. Consulting taught me to ramp fast on messy domains, but I want to carry a platform past its first year and live with my own tradeoffs, which is exactly the shape of this team.
The framing sentence tells the interviewer how to listen, and the airtime lands on growing scope rather than titles. Read aloud this is roughly ninety seconds — half the target; the missing half belongs to the recent role. Skipping the reason for a move, or narrating titles instead of scope, would downlevel it.
With one or two roles behind you the arc is short, so make it about direction rather than volume. Name what pulled you toward this kind of work and one thing you have actually built; keep coursework to a sentence unless it maps directly onto the job.
Editing is now the skill being watched. Compress the first role hard, make the most recent one the centre of gravity, and be ready to defend one transition in detail — why you moved, not merely that you did.
Narrate scope growth instead of job titles: how much system, how many people and how much ambiguity you owned at each step. Interviewers are listening for whether your decisions got bigger or only your years did.
Frame the arc around a thesis — the class of problem you have chosen and the bets you made to get closer to it. Include at least one move that cost you money, title or comfort, and say what it bought.
saying these in an interview costs you the question
- Reading the resume line by line instead of narrating a trajectory
- Spending half the time on the oldest and least relevant job
- Leaving a move unexplained and hoping it goes unnoticed
- Badmouthing a former employer while explaining a transition
- Ending at the current job with no link to the role being discussed
- Running past four minutes without pausing or checking in
- Which of those moves was the hardest decision to make?Pick a genuine one and name the tradeoff out loud — money, title, stability, learning. Say what you gave up, not only what you gained; a move with no cost sounds rehearsed. Close with whether you would make it again, and answer that without hedging.
- You have changed jobs every couple of years — what would keep you here longer?Do not get defensive about the rhythm. Describe it accurately, give the reason it happened, then answer the real question with something checkable: the kind of ownership, timescale or product continuity you want. Asking what tenure looks like on the team is a fair return.
- Which role on there is closest to what we are hiring for?Name one role, not two, and say which parts map and which do not. Volunteering the mismatch buys credibility for the parts you do claim. Then bridge — name the largest gap and how you would cover it in the first months.
## Three situations, one prompt Interviewers reach for this prompt in three different situations, and the wording barely changes: - a recruiter screen where they have the document open, - a hiring-manager call where it replaces the opener, - and a final round where someone joined late and wants the shape of you in three minutes. Common variants are: - 'walk me through your resume', - 'take me through your career so far', - 'talk me through this CV top to bottom' and - 'how did you get from there to here'. The tell that you are being asked for the resume walkthrough rather than the general opener is that **the interviewer is looking at a document** and will follow you down the page. When you cannot tell which one you are being asked, start with the arc sentence and the first role; if they wanted the shorter opener, they will steer you, and you will have lost fifteen seconds rather than three minutes. ## Chronological or thematic **Chronological** is the safe default and the one most interviewers expect, because they are reading down the page while you talk and any other order makes them hunt. **Thematic** narration — grouping by the kind of problem rather than by date — earns its place in exactly two cases: - a career change, where the chronology tells a story about your old field, and - a long history where three of your roles are irrelevant to this job. If you go thematic, say so out loud in the first sentence, name the themes, and still give the dates as you pass them. An unannounced non-chronological walkthrough reads as evasion, because the interviewer's first thought is which part you are trying to skip. ## The airtime math is the whole discipline Aim for two and a half to four minutes. Roughly: - fifteen seconds for the framing sentence, - a sentence or two per early role, - and half the total on the most recent one or two roles. The commonest failure is the reverse — a rich, affectionate account of a first job because it has been told most often, and then a rushed thirty seconds on the role the interviewer actually cares about. Rehearse it once with a timer and once out loud to a person, because the drift only shows up aloud. ## Transitions are the load-bearing part Every move needs **a stated reason**, given as you pass it, in a clause or a sentence. Growth, scope, a relocation, a layoff, a company that stopped funding the work. The reason should point forward — toward what the next role offered — rather than backward at what was wrong. An unexplained move is the one thing an interviewer reliably writes down, and it turns into a probe later that you will answer under more pressure than if you had volunteered it. ## Gaps and short tenures follow the same rule at higher stakes 1. State the length, 2. state the reason once, 3. and close it. The instinct to bury a gap in vague year-only date ranges backfires: it survives the interview and dies at the reference check. ## A career change needs a bridge, not an apology The strong version names **the transferable substance** — the domain knowledge, the data literacy, the customer contact — and then names **the deliberate step** you took to convert it, so the change reads as a decision with evidence behind it rather than a hope. ## How the bar shifts - **Early on**, the arc is short and direction is what is being assessed. - In the **middle**, the skill is editing: what you compress signals what you think matters. - **Senior**, the narration should track scope — system size, people, ambiguity — instead of titles. - **Principal**, the arc should carry a thesis about the class of problem you have chosen, including at least one move that cost you something.