Motivation & Fit

Tests whether the thing pushing you out also exists here, and how you talk about people you are leaving. Give one honest, specific reason without blame, credit what the role gave you, then land on the pull toward this job.

Three kinds of source: how the company builds (its public engineering writing), what it sells (the product itself), and how it is funded or performing. Capture the findings on one page as hooks and questions, not as memorised facts.

Asks you to make your own case out loud. Give one claim, two pieces of evidence closest to the job's hardest task, one thing the resume does not show, and an honest note on what you would need early.

Tests whether you want this job or any job. Answer with two or three specifics from the posting, evidence you have already done that kind of work, and what the role gives you next.

Tests whether you chose this employer deliberately or are mass-applying. Answer with one specific, checkable hook about their work, evidence you engaged with it, the bridge to something you have actually done, and why the move makes sense now.

Six recurring warning signs: badmouthing a former employer, compensation named as the only driver, a generic answer that would fit any employer, blame-shifting, arrogance, and a motivation that changes between rounds.

Tests whether you know your own working conditions and whether they match this team's reality. Name two or three specific conditions, back each with evidence from work you shipped, and connect them honestly to how this role actually runs.

Probes genuine curiosity and whether you will keep growing with the team. Answer with two or three habits you actually practise, one taken a level deep, and a link to the stack this role runs.

Turn the finding into an inference about what that team now deals with daily, then write two things: a hook linking it to your own experience, and a question that only makes sense if you read the post.

Name the constraint you were working under rather than the fault you were escaping, keep it to one short clause, then move to what you are going toward. Describe situations, never characterise people.

Probes honesty and whether the time off left you rusty. Name the gap plainly in one sentence, say what the months were actually spent on, and close on why you are ready now.

Screens for whether the separation was really about performance and how you handle a setback you did not choose. State the scope of the cut in one flat sentence, stay unbothered, show what you completed, then move the conversation forward.

Checks whether you read the values and can connect one to something you actually did. Pick a single value, restate it in your own words, prove it with a decision you made, and name where living it costs something.

Probes how you will be managed and whether you can state your needs without sounding high-maintenance. Give two or three concrete asks — feedback cadence, decision clarity, escalation — each with a short example, then say what you handle yourself.

Probes learning speed and self-direction under a real constraint. Pick one thing you learned on the clock, describe how you reached working knowledge, and finish with what shipped because of it.

Tests whether your enthusiasm is specific enough to be real. Pick a project you owned a real slice of, spend the airtime on the part you kept choosing to work on, and close with the thing you would look for again.

Probes whether your motivation is specific and durable rather than performed. Name one narrow class of problem, prove it with a concrete thing you built or chased, then bridge it to what this role does daily.

Screens for attrition risk against months of ramp-up cost. Separate the moves the business made from the ones you chose, prove depth inside a short stint, then name the conditions under which you stay.

Tests self-knowledge and whether the track you want exists here. Answer the fork directly, back the choice with something you have already tried rather than imagined, and say when you would revisit it.

A badmouthing trap dressed as a candour test. Name one real structural frustration you can describe without contempt, give the charitable reason it exists, say what you did about it, and stop at one rather than opening a list.

Tests whether the move is considered or accidental. Name the gap plainly, show what genuinely transfers, point at self-directed work proving you started already, and give a measurable ramp you would be held to.

Probes whether your interest survives comparison. Name the two or three criteria you are actually deciding on, place this employer against them with evidence from the process, admit one honest tradeoff, and never disparage the alternatives.

Write 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.

Published engineering writing is partly recruitment marketing, so corroborate it. Check whether the post admits costs, whether later posts and open roles build on it, whether the product shows it, and whether the people you meet can discuss it unprompted.

Interviewers compare notes, so two different motives given to two different people surface side by side. The fix is one true through-line re-expressed in each listener's vocabulary, never a different motive per listener.

Substitute observable artefacts for absent writing: the product itself, the shape of the open roles, public docs and changelogs, and what a recruiter can tell you before the loop. Expect fewer hooks and lean harder on questions.