How do you run a red-flag self-audit over a motivation answer you have drafted?
answer
- Do it on paper, never live
- Before the answer is ever spoken
- One line per warning category
- Six lines, then a very short re-draft
basics
~20 sWrite the answer out as you would say it, then check it against one warning-flag category per line — six lines — marking each pass or fail. Re-draft only the failing lines, quickly, and read the result aloud.
solid answer
~40 sThe audit is a written pass, not a mental one, because none of these flags are audible while you are speaking. Draft the answer in the words you would actually use. Then set out one line per warning category — badmouthing, compensation-only, vagueness, blame-shifting, arrogance, inconsistency — six lines, and mark each one pass or fail against the draft. For anything that fails, re-draft just the offending sentence inside about a half-minute budget: the constraint matters, because a long rewrite produces a polished paragraph nobody can say out loud. Then read the whole thing aloud once. Two or three failures on a first draft is normal and is the point of doing it — the alternative is discovering them from a hiring manager's face mid-answer.
go deeper
Get the habit before the mechanics: write the answer down first. Most first-job candidates rehearse motivation answers only in their head, where every warning sign sounds perfectly reasonable.
Be able to describe the pass concretely — a written draft, one line per warning category, quoted evidence for each failure, and a deliberately short re-draft — and say why each of those constraints exists.
Show judgment about when to stop. Know that a fourth or fifth pass trades one flag for another, since an over-polished motivation answer reads as recited and invites probing you did not need.
Own the choice of what stays in. Some true reasons for a move cannot be re-drafted into safety, and deciding to say one anyway, in the plainest available words, is a position you should be able to defend.
## Why an audit rather than better drafting The six warning signs in a motivation answer — badmouthing a former employer, compensation as the only motive, vagueness, blame-shifting, arrogance, inconsistency — share an inconvenient property: they feel fine from the inside. While you are speaking, a badmouthing sentence feels like candour, a generic sentence feels like enthusiasm, and a blame-shifting sentence feels like accurate context. The signal is only legible from the listener's chair. So the technique is not "try harder to avoid them". It is a mechanical pass over written text, done before the answer is ever spoken, that does not depend on your ear. ## The pass, step by step **1. Draft in speaking voice.** Write the answer the way you would actually say it, contractions and all. A draft written in careful written English audits clean and then falls apart under pressure, because the sentences you fall back on in the room are not the ones you wrote. **2. One line per category.** Set out six lines, one for each warning category, and mark each pass or fail against the draft. Six is the whole list; a seventh line means you have invented a category, and five means you dropped one — usually inconsistency, which is the easiest to forget because it only shows up across answers rather than inside one. **3. Judge by quotation, not impression.** For each fail, copy the exact words that triggered it. 'This bit sounds negative' is not a finding you can act on. 'My last manager had no idea what they were doing' is. A finding you cannot quote is usually nerves rather than a flag. **4. Re-draft inside a short budget.** Give each failing line roughly thirty seconds. That constraint is doing real work: given ten minutes, people rewrite the whole answer into something balanced, defensible and completely unspeakable. Thirty seconds forces a swap of one clause — the fault replaced by the constraint, the person replaced by the situation. **5. Read the whole thing aloud, once.** Not to memorise it. The read-aloud catches the artefacts the edit introduced: a clause that no longer joins, a sentence that has quietly become a paragraph. Then stop. An answer polished past four or five passes starts to fail a different test, sounding recited rather than considered. ## A worked pass, in a testing role Draft: 'Honestly, I'm leaving because our releases were a mess. My last manager had no idea what they were doing, and the developers kept breaking the build the night before sign-off. I'm looking for somewhere that takes quality seriously.' The six lines come back: - Badmouthing — **fail**. 'My last manager had no idea what they were doing.' - Compensation-only — pass. Compensation is not mentioned. - Vagueness — **fail**. 'Somewhere that takes quality seriously' fits any employer. - Blame-shifting — **fail**. 'The developers kept breaking the build' places the whole outcome elsewhere. - Arrogance — pass, narrowly. Nothing claims the candidate was the only capable person. - Inconsistency — pass, but only checkable against what was said earlier in the loop. Three failures, each re-drafted in a half-minute: 'I was hired to build out the automated regression suite and it kept getting deferred behind manual sign-off, so builds were still breaking late. I'm looking for a role where that suite is owned rather than squeezed in — which is the part of this job that interested me.' The facts are unchanged. The manager is gone, the developers are gone, and the generic closing has been replaced by something that could only be said about this role. ## What the audit is not It is not a script generator. The output is a checked draft, not lines to recite; the point is that you know which sentences are load-bearing and which ones you had to fix, so that under pressure you improvise around the same shape. It is also not a one-time exercise — the same six lines run over each of the small number of motivation answers you expect to give, and the inconsistency line is the only one that can only be checked with the others in front of you.
- Why cap the re-draft of a failing line at about thirty seconds?Because an unbounded rewrite produces something you cannot say. Given ten minutes, most people write a balanced, carefully qualified paragraph that reads well and collapses under pressure. A half-minute forces the minimum edit — swapping the fault for the constraint, or the person for the situation — which is the change that actually removes the flag.
- How many failures on a first draft should worry you?Two or three is normal and is the reason the pass exists. Zero on a first draft usually means the draft was written defensively rather than in speaking voice, so it will not survive contact with the room. What should worry you is the same line failing twice after a re-draft, which means the underlying reason still needs rethinking rather than rewording.
- Can you audit an answer you have not written down?Not reliably. Every one of these flags feels acceptable from the inside while you speak, which is exactly why the pass is written. Without a text you can quote from, findings degrade into 'that felt a bit negative', which is not actionable and is as likely to be nerves as an actual problem.
saying these in an interview costs you the question
- Auditing by feel instead of against a written draft
- Leaving a departure explained by what was wrong with the previous employer
- Rewriting the whole answer instead of the one failing line
- Polishing until the answer sounds recited rather than considered
- Recording findings you cannot quote a sentence for
- Dropping the inconsistency check because it needs the other answers