How to prepare for an interview using your evidence

Interviews are where evidence gets tested

A resume makes claims. An interview tests them. Most interviewers, whether they think of it this way or not, are trying to answer two questions: is what's on paper true, and what's missing from the paper that matters for this role?

That makes preparation more predictable than it feels. You don't need to guess at every possible question. You need to know which parts of your evidence are solid, which parts an interviewer will want to verify, and which gaps they're likely to probe — and have a real story ready for each.

Step 1: Predict what will be probed

Start with the job's critical and important requirements and line them up against your evidence. The places an interviewer is most likely to dig are predictable:

• Items that need verification — experience your resume suggests but doesn't clearly prove. Expect "tell me more about…" questions here.
• Unknowns — requirements your resume is silent on. Expect direct questions: "Have you ever had to…?"
• Big claims — your most impressive numbers. A good interviewer will ask how you measured them and what your part was.
• Transitions and gaps — changes of direction, short tenures or time away. Usually asked out of curiosity, not suspicion; a clear, brief answer is enough.

Your Career DNA is a useful starting point: its inferred, potential and unknown items are a close preview of where questions will land. If you've run a match or a fit check for the role, the "needs verification" and "not evidenced" rows are your preparation list.

Step 2: Build stories with STAR, tied to evidence

STAR — Situation, Task, Action, Result — is a common way to structure answers to behavioral questions. It works because it forces the same ingredients that make a resume bullet credible: context, ownership, method and outcome.

• Situation — one or two sentences of context. Where were you, what was going on, how big was it?
• Task — what you specifically were responsible for. This is where ownership becomes clear.
• Action — what you did, step by step. Spend most of your time here. Say "I" for your actions and "we" for the team's, and be precise about which is which.
• Result — what changed, with numbers you can explain. Include what you'd do differently; it shows judgment.

For example, for an invented operations coordinator role: the situation might be a backlog of late shipments during a system change; the task, owning the daily exception report; the actions, building a shared tracker, setting a morning triage call and escalating carrier issues; the result, the backlog cleared within a few weeks and the tracker kept in use afterward. Every element maps to something on the resume — which is exactly why it's believable.

Aim for six to eight stories that together cover the role's critical requirements. Many stories can answer several questions; a good one about a difficult rollout may cover leadership, conflict and prioritization.

Step 3: Prepare for the numbers

If a figure is on your resume, assume you'll be asked about it. For each one, know:

• Where the number came from and over what period.
• What the baseline was before your work.
• What part of the change was yours versus the team's or other factors.
• What you'd measure differently next time.

If you can't answer these for a number, consider softening it on the resume before the interview rather than during it.

Step 4: Handle gaps honestly

Every candidate has gaps against some requirement. Interviewers generally aren't looking for a perfect match; they're looking for an accurate picture and a sense of how you'd handle what's new. A structure that works:

• Acknowledge it plainly: "I haven't managed a budget directly."
• Give the closest real evidence: "I built the quarterly cost forecast my manager used for the team's budget, and tracked spend against it."
• Show how you'd close it: what you'd learn, who you'd learn from, and how quickly.

What tends to hurt candidates isn't the gap — it's an answer that tries to talk around it. Clear, specific honesty reads as confidence.

Step 5: Ask questions that test the fit from your side

Your questions are part of the evaluation in both directions. Good ones show you've thought about the work, and they tell you whether the role is right for you. A few that tend to produce useful answers:

• What would success look like in the first 90 days? In the first year?
• Which of the requirements in the job description matters most in practice?
• What's the hardest part of this role that isn't obvious from the description?
• How is performance in this role measured, and who measures it?
• What did the last person in this role do especially well — or what is the team hoping changes?
• Based on what we've discussed, is there anything about my background you'd want to understand better?

That last question is especially valuable. It invites the interviewer to name a concern while you're still in the room to address it — with evidence.

A one-page prep sheet

The night before, condense everything onto one page: the role's critical requirements, your best story for each, the two or three numbers you'll likely be asked about, your honest answers on the main gaps, and the questions you want to ask. Reading it once is better than rehearsing scripts — you want to remember the evidence, not memorize the words.

If an employer shared a Match Code with you, running the match also gives you their side of the picture: the requirements they weighted most and where your evidence is strong, partial or still to be verified. That is the most direct preparation list you can get.