Reviews
Part of Resumes and cover letters for people who want the details
Interview questions drawn from your resume: how to prepare and what to avoid
A guide to the interview questions your own resume invites, how to handle gaps and short stints, and how to turn each line into a clear answer.
Half the questions in an interview come straight off your own resume. The panel reads it an hour beforehand, marks the things that do not add up, and asks about those. That is predictable enough to prepare for, and preparing for it is more useful than rehearsing answers to generic questions.
What to take away
- Every line on your resume is a question you have invited. Read it back as an interviewer would before you send it.
- The awkward items, a gap, a short stint, a step backward, are handled by a plain sentence and a change of subject to scope.
- A line you cannot expand into two minutes of specific detail should not be on the page.
Reading your own document as an interviewer
Print it and mark three things: anything vague, anything impressive, and anything that raises a question about time. Those three categories generate nearly every resume-driven question.
Resume line to interview question
What is on the page
- "Improved the process"
- Which process, what was wrong
- "Led a project"
- Who reported, what went wrong
- Six-month role between long ones
- What happened
- A gap of a year
- What you were doing
- Title outranks duties
- What authority you actually had
- Tool listed with no context
- Prove it, sometimes on the spot
What gets asked
- "Improved the process"
- "Led a project"
- Six-month role between long ones
- A gap of a year
- Title outranks duties
- Tool listed with no context
| What is on the page | What gets asked |
|---|---|
| "Improved the process" | Which process, what was wrong with it, how do you know it improved |
| "Led a project" | Who reported to you, what you decided, what went wrong |
| A six-month role between two long ones | What happened |
| A gap of a year | What you were doing |
| A title that outranks the described duties | What you actually had authority over |
| A tool or system listed with no context | Prove it, sometimes on the spot |
The last row catches people constantly. A skills list is a set of claims, and any of them can be tested. Anything you would not want examined should not be listed.
The awkward items, handled
A gap: state the period and one clause of reason, then move to what you did with it or what you did before it. Illness, care, redundancy, study, travel. No apology and no elaboration.
Handling awkward resume items
- Gapstate period, one clause of reason, move on
- Short stintkeep it, one plain sentence ready
- Step backwarddescribe scope, say why
- Change of fieldthree transfers, one still learning
A short stint: keep it, and have a plain sentence ready. "The role was not what was described and I said so early" is a complete answer. Attacking the former employer is not.
A step backward in title: describe the scope, which is often larger than the title implies, and say why the move was made. A deliberate move for scope, location or industry is a decision; a move you cannot explain reads as one that was made for you.
A change of field: give the map yourself. Three things that transfer, one thing you are still learning, and where you are with it. Doing this before you are asked is stronger than doing it under pressure.
None of these is unusual and all are worse when concealed. The versions of the document that suit each career stage are set out in the resumes and cover letters career path page.
Turning a line into an answer
A resume line is a headline. The answer behind it needs four parts: the situation in one sentence, the constraint you were under, what you decided, and what changed. Add the part that went wrong, because an account in which everything worked is either about a trivial problem or is incomplete.
Four parts of a resume answer
- Situation in one sentence
- The constraint you were under
- What you decided
- What changed
- Add the part that went wrong
This is what a structured interview is designed to elicit, and it is why the same categories recur across employers. The federal guidance on structured interviews describes the method and why it is used, and reading it from the candidate's side tells you what a well-run panel is trying to get from each question.
The qualities being scored are usually named in advance rather than invented in the room. The same body's material on competencies is a usable inventory of what those qualities are called, and matching a resume line to a defined quality is how you make an answer land rather than merely be true.
The claims that fail a check
- A figure you cannot source. If you cannot say where it came from, take it off the page.
- A title you were not given. Acting in a role is a fine thing to say; holding it when you did not is not.
- A qualification in progress, described as complete. Say "in progress" and the date.
- A team size that counts people you coordinated but did not manage. Say "coordinated".
- Dates rounded to hide a gap. References and background checks work from exact dates.
Any of these can end a process on a question of honesty rather than of capability, which is a much worse way to lose. The document that keeps you clear of all five is one built from scope rather than from adjectives, in the way the resumes and cover letters guide sets out.
Claims that fail a check
- A figure you cannot source
- A title you were not given
- Qualification in progress called complete
- Team size counting coordinated people
- Dates rounded to hide a gap
What to bring, and what to leave
Bring your own copy, marked up, and the record of what you actually did if you keep one. Do not bring a former employer's material: producing real internal documents in an interview answers a confidentiality question in the worst way, and panels notice.
If a take-home task or a work sample is requested instead, that is a different exercise with its own rules, and the interviews jobs page covers what to establish before agreeing to one. The general preparation that applies to any format is in the interviews guide.
Common questions
They asked about a job I left off. What now?
Answer honestly and briefly. Omission is usually forgiven; a second inconsistency is not. If a role is short or irrelevant, it is safer on the page with a one-line explanation than absent.
How much detail should an answer have?
Ninety seconds, then stop and let them ask. Long answers are the most common way candidates lose a panel's attention, and the follow-up question tells you what they actually wanted.
What if I genuinely cannot remember the details of an old project?
Say so and offer the shape of it, then move to something recent you can describe fully. Fabricating detail under pressure is how people contradict themselves twenty minutes later.
Should I explain a gap in the cover letter or wait to be asked?
In the letter, in one sentence, if it is long or recent. It removes the question from the interview and it reads as confidence rather than as anticipation of criticism.
Is it worth listing every system I have used?
No. List the ones you would be comfortable being tested on and describe the others in the body of the experience if they matter. A long list is read as padding and is examined as a set of claims.
