An interview example is worth using when it is true, shows you personally taking action, has a clear result, fits the skill the question is testing, and holds up under follow-up questions. If an example fails two or more of those tests, keep it in reserve or drop it. The best examples are usually specific, moderately sized and fairly recent, not the biggest or most dramatic thing you have done.
Many candidates pick examples by gut feeling or by which story sounds most impressive. That often backfires: a grand story where your role is unclear can raise more doubts than a modest one where your actions are obvious. A quick scoring method lets you choose on purpose.
Why example choice matters
Behavioral questions ask for evidence. Structured-interview guidance from the US Office of Personnel Management describes the idea as the “behavioral consistency” principle: past behavior in a relevant situation is used as a guide to future performance. A weak example gives the interviewer nothing to work with, however well you tell it, while a strong one answers the question and several follow-ups with the same material. That is the interviewer’s logic, not a guarantee, and it is why a detailed, checkable example beats an impressive vague one.
The six-point test
Run each candidate example through these questions, scoring each yes as 1 and each no as 0.
- Is it true and fully defensible? You should be able to answer detailed follow-ups: who, when, what exactly you did, what went wrong.
- Were you the main actor? Can you describe specific actions you took, using “I,” not only what the team did?
- Is there a clear result? An outcome, a change or a lesson. A figure helps when it is real; a plain description is fine.
- Is it relevant to the role? Does it show a skill the job needs, such as prioritizing, communicating, solving technical problems or leading?
- Is it reasonably recent? Many coaches suggest the last five to seven years, a rule of thumb rather than a standard. Exceptions: you are early in your career, or the story is unusually strong.
- Is it safe to share? No confidential information, no bad-mouthing a former employer, nothing that raises ethical red flags.
| Score | What to do |
|---|---|
| 6 | Strong. Make it a core story. |
| 4 to 5 | Usable. Fix the weak points if you can. |
| 3 or fewer | Reserve or cut. |
The score is a way to make your gut feeling visible, not a validated measure. Ten minutes on paper is enough.
“I” versus “we”
Teams do the work, but interviewers are assessing you. If every sentence is “we decided” and “we built,” they cannot tell what you contributed. Rewrite with your own actions:
| Before | After |
|---|---|
| “We improved our onboarding process and reduced complaints.” | “I noticed new customers asking the same three questions, so I wrote a short guide and worked with two teammates to test it. Setup complaints dropped over the next two months.” |
| “The team fixed the bug before launch.” | “I traced the bug to a data format mismatch and wrote the fix, and a colleague reviewed it. We shipped on schedule.” |
These are invented illustrations. Crediting others is fine (“I worked with two teammates”), and it shows collaboration while keeping your role visible. Only claim what you truly did.
Size: why medium beats massive
Candidates often assume the biggest project is the best story. Huge projects create problems: your role is hard to isolate, results involve many factors, and follow-ups get complicated. A medium-sized example where you owned a clear piece is usually easier to explain and to believe.
Signs of the right size: you can explain it in about two minutes without a background lecture, the stakes were real but contained (a deadline, a customer issue, a process problem), and you can name two or three specific actions. It is too big if it needs lots of context or you can only describe your role vaguely. It is too small if there was no real obstacle or decision.
Matching examples to question types
Different questions need different evidence. Use this to check coverage.
| Question theme | What the example should show |
|---|---|
| Conflict | You listened, stayed professional and reached a workable outcome |
| Failure | You took responsibility, learned something and changed behavior |
| Leadership | You influenced others, with or without a title |
| Deadline pressure | You prioritized and communicated |
| Initiative | You spotted a gap and acted without being told |
| Adaptability | You adjusted to a change and kept performing |
One example can serve more than one theme, but check that it answers the specific question rather than forcing it. To tag stories and spot gaps across your whole set, use the method in building a story bank.
Red flags
Drop or rework an example if:
- The ending is unclear. If you cannot say what happened, it sounds unfinished.
- You are the hero and everyone else is incompetent. Interviewers may wonder how you would talk about them.
- The lesson is “I worked really hard.” Effort alone is not a specific skill.
- It hinges on an exaggeration. Follow-ups will expose it.
- It reveals an unresolved conflict with a past employer or colleague.
- It comes from a very different field and you cannot link it to the job. For a career changer this can work if you name the transferable skill.
If you have few examples
Early-career candidates and career changers often worry they have nothing. Widen the pool: look at group projects, clubs, part-time jobs and community roles; consider small situations such as fixing a recurring problem or organizing an event; ask a friend or former colleague what they remember you doing well; and review old emails and project notes. A modest example told clearly beats a large one told vaguely. For shaping raw material into answers, see preparing better stories for behavioral questions.
A worked scoring example
Suppose you are applying for a project coordinator role with two candidate examples (both invented).
Example A: led a company-wide software migration. True (1), main actor (0, many leads), clear result (1), relevant (1), recent (1), safe (1) = 5. But your part is unclear and follow-ups would be complex.
Example B: took over scheduling for a small team when a coordinator left, built a shared calendar and weekly check-in, and reduced missed handoffs. All six yes = 6.
Example B is likely stronger for this role even though it sounds less impressive. Keep A as a backup for a question about change management if you can describe your own part clearly.
Before committing to any example, say it aloud in under two minutes, list five follow-up questions an interviewer could ask and see if you can answer them, and ask a friend “What did I personally do?” If they struggle, tighten your actions. The article on what makes an answer sound stronger and more credible explains how specifics and ownership build trust.
Where this comes from
The behavioral-consistency idea and the situation, action, result format come from the structured-interview guidance published by the US Office of Personnel Management. The six-point test, the score bands, the size guidance and the recency window are practical judgment from common interview coaching, not research results, and every example here is invented for illustration. Interviewers differ, so use these as a checklist, not a guarantee.