The Interview Questions Your Resume Invites

An interviewer with your resume in front of them is looking for things to ask about, and the things they find are the specifics: the number, the strong verb, the unusual title, the short tenure, the tool you listed once. You can predict most of it. Read your own page marking every claim that would make you ask a follow-up, and you have produced the agenda for a large part of the conversation.

This is the same work as checking your resume for accuracy, viewed from the other side. A claim you can evidence produces an answer you can give.

How an interviewer reads the page

Not top to bottom. They skim for anchors — the most concrete or most surprising items — and build questions around those. In practice the anchors are:

Any number. A figure is the easiest thing in the world to ask about, because there is an obvious follow-up: how was it measured, over what period, what else changed at the same time. If you cannot answer those three, the number is a liability rather than an asset. This is why an unsourced figure should come out of the draft entirely rather than being softened.

Strong ownership verbs. “Led the migration” produces “tell me how you ran that.” The answer needs names, decisions and a disagreement you resolved. If your honest answer is that you did a large share of the work while someone else ran it, the verb was wrong.

A tool listed but not used elsewhere. Anything in the skills section that never appears in the experience section stands out as available to probe, and it is often probed for exactly that reason.

Short tenures and gaps. Not suspiciously, usually — just because they are the most obviously unexplained thing on the page.

Titles that do not match the described work. A junior title with senior-sounding bullets invites a question about what the role actually was, and it is better to have answered that on the page by showing the official title alongside the working one.

Anything phrased in resume-speak. Vague constructions like “drove alignment across stakeholders” get asked about because they are unclear, and the answer is always a plainer sentence you could have written in the first place.

Doing the pass

Print the resume or read it in a window on its own. For each line, write the question you would ask if you had never met yourself, then write your answer in a sentence or two. Not a rehearsed script — enough to know the answer exists.

You will find three categories:

1. Claims with an easy, specific answer. These are your strong lines. Notice which they are; they are the ones to steer towards.
2. Claims where the answer needs a detail you do not have to hand. Go and find it, or accept that you will be answering from memory and phrase the bullet accordingly.
3. Claims where you do not have an answer at all. These need changing before the interview, not preparing for.

The third category is the point of the exercise. A bullet you cannot discuss is worse than no bullet, because it consumes interview time and produces a bad impression while a stronger line sits further down the page unread.

Prepare the specifics, not the story

The failure mode in interview prep is rehearsing narratives. The questions your resume generates are mostly requests for detail — who else was involved, how long it took, what you would do differently, what the constraint was. Those are answered by remembering the work, not by having a polished paragraph.

For each of your top handful of bullets, be able to say: what the situation was, what you specifically did, who else was involved, and how it turned out including the parts that did not work. That last element is disproportionately valuable, and it is only available to people describing something real.

The bullets that come from AI drafts

Pay particular attention to lines you did not write from scratch. A generated bullet can read as an accurate description of your work while containing a specific you never supplied, and because the sentence feels familiar you will not spot it under time pressure. Reading generated lines cold, weeks later, is how the invented specifics get caught — the same reason checking is best done as a separate pass on a different day.

If a line survives the interview-question test, it is genuinely yours regardless of who drafted it. If it does not, no amount of preparation will fix it.

Where your answers will be cross-checked

Some of what you say will be compared against other sources: a referee’s account, your public profile, an application form. Where your interview answer, your resume and your profile all describe the same work slightly differently, the differences are visible to whoever is collating notes. Being consistent is easier than being careful, which is the argument for maintaining one version of the story everywhere.

The useful side effect

People who do this pass report the same thing: the resume gets shorter and the interviews get easier. Shorter because a handful of lines fail the test and come off. Easier because the questions arrive as expected and the answers are already in mind, which frees attention for the parts of the conversation you genuinely cannot predict.

If you only do one review before an interview, do this one. It is a sceptical read of your own page with a specific output: the list of questions you are about to be asked.