Your resume is the interview script

Before most interviews, the person sitting across from you has read your resume and marked the things they want to probe. Not because they are trying to trip you up -- because it is the most efficient way to verify that what you wrote matches who you are.

That means every bullet you wrote is a potential question. Every gap in your timeline is a question. Every impressive-sounding claim without context is a question. Every company you left after a short tenure is a question.

The interview is often a structured walk through your document. Treating it like a freeform conversation you can improvise through is how people get caught out by things they wrote about themselves three years ago.

The interviewer is not winging it. They prepared from your resume. You should prepare from it too.

Three types of questions your resume creates

Resume-based interview questions fall into three categories. Each one requires a different kind of preparation.

Verification

"Tell me more about that project." They want to confirm the claim is real and you were actually involved.

Depth

"How specifically did you achieve that result?" They want to know if you understand what you did or just know how to describe it.

Gap

"I notice you left after eight months." They want context for anything that looks unusual, short, or inconsistent.

Verification questions are the most common. Depth questions are the ones that separate prepared candidates from unprepared ones. Gap questions are the ones people dread but are actually the easiest to handle if you have thought about them in advance.

How to prepare before the interview

Sit down with your resume two to three days before the interview. Not the night before. You need time to think through the answers and let them settle before you are in the room.

1

Read every bullet you wrote as if you are the interviewer. Which ones are vague? Which ones make a claim you would want to probe? Which ones raise an obvious follow-up question? Mark them.

2

For each marked bullet, build one specific story. Name the project, the context, your specific role, the result. Not a polished narrative -- just the facts you need to have ready so you are not reconstructing them on the spot.

3

Look at your timeline for anything that might flag a question. Short tenures, gaps, role changes, company names they might not recognise. Have a simple, direct answer ready for each.

4

Read the job description and find where it maps to your resume. The overlap points are where the depth questions will come from. Those are the bullets you most need to be able to defend with specifics.

What to do about bullets you cannot defend

Go through your resume and identify any bullet where, if asked to walk through it in detail, you would struggle to give a specific example. Those are a problem not just for this interview -- for every interview until you fix them.

You have two options. Find the real experience behind the claim and rewrite the bullet to reflect what actually happened. Or remove the bullet. A shorter, more accurate resume is less risky than a longer one with claims that do not hold up under basic questioning.

The worst outcome is discovering mid-interview that a claim you wrote does not have a story behind it. There is no smooth recovery from that.

If you wrote it, you need to be able to defend it. That is the whole game.