Do not explain the change. Transfer one behaviour. Give about ten seconds to why you left, then spend the rest of the answer on a single concrete thing you did in the old job that is the same thing this job pays for, and land on something you have built recently. Sixty seconds, roughly 140 spoken words, with no apology anywhere in it.
What the question is actually checking
Four checks, and none of them is whether your reason is good enough. They run in the interviewer's head in roughly this order.
| Check | Passes when you say | Fails when you say |
|---|---|---|
| Do you know what the job is? | "Most of the work is narrowing down where an assumption broke." | "I love solving problems and building things." |
| Are you moving toward or away? | "The part of the old job I was best at had the least time in it." | "The pay was bad and management was a mess." |
| Will you be junior without resenting it? | A recent instance of being corrected in a code review, and what you changed. | "I managed a team of twelve, so I am used to responsibility." |
| Will you leave again in a year? | A dated history: started in 2024, still doing it after the novelty went. | "This is definitely what I want to do long term." |
The load-bearing sentence is the bridge, and there is one rule for it: name a behaviour, not a trait. "I am detail-oriented" is a trait, and every candidate in the loop claims it. "I reconciled two systems to the penny every month and once chased a 43p break for two days" is a behaviour, and only one person in the loop has done it. A behaviour has a noun, a number and a verb that can be followed up on. Pick exactly one. Two bridges reads as neither being real.
Script one: secondary teacher to software engineer
I taught secondary maths for six years. I moved because the part of the job I was best at was the part the timetable had the least room for. [Ten seconds, forward-facing. No complaint about workload or pay, both of which are true for almost everyone and therefore score nothing.] When a class got a topic wrong I did not reteach the topic. I sorted the thirty scripts by which wrong answer they gave, and usually around twenty of them shared one false assumption three steps before the mistake they actually wrote down. So I taught that step. [The bridge. One behaviour, with a number in it, described as a method rather than as a personality.] That is the same move as reading a stack trace: the exception surfaces at line 400 and the wrong assumption sits at line 12, and the work is finding the first point where your model of the system stopped matching the system. I started doing that on my own data in 2024, worked through [course or units], and the last thing I shipped was [project], where about ninety per cent of the time went on locating where the assumption broke rather than on writing the fix. I want to do that against something a few hundred people use instead of thirty.
Notice what is not in it: nothing about patience, nothing about communication skills, nothing about caring. That is where most teacher answers go, and it is where they stop being distinguishable from one another. The claim here is a technical one, and it invites a technical follow-up, which is exactly what you want from this question.
Script two: finance operations to software engineer
I spent four years in finance operations, most of it on month end close. [Plain, past tense, one clause. No preamble about a non-traditional background.] The centre of that job was reconciliation: two systems that are supposed to agree, and a difference of 43p that you can neither sign off nor ignore, because a 43p break and a 43,000 break are found in exactly the same way and you do not know which one you have until you have found it. [The bridge, given as a rule with a consequence attached rather than as a claim about being thorough.] I got tired of finding those by eye, so I wrote the comparison in Python, rebuilt it in SQL when the volume grew, and close went from [n] days to [n]. That is the reason I now write the assertion before the feature. The first thing in any pipeline I build is the invariant, rows in equals rows out plus rejects, and it fails loudly instead of quietly writing a wrong number into a dashboard someone will make a decision on. Nearly every incident I have been near since has been that same shape.
The finance route has one specific trap. Do not lead with Excel, and do not lead with the word accuracy. Both put you in the analyst pile before the second question. Reconciliation is the strong bridge because it is genuinely the same discipline as data integrity work, and because "quietly wrong" is a failure mode every engineer in the room has been burned by at least once.
Script three: mechanical engineer to software engineer
I was a mechanical design engineer for five years, mostly on [pumps, enclosures, assemblies]. What I do not miss is the six week lead time on being wrong. [A reason about the feedback loop. Another engineer respects it, and it cannot be misread as running away from difficulty.] The habit I brought with me is the FMEA. Before release we would sit with the drawing and list every way each part could fail, score severity, likelihood and whether we would even detect it, and the items that scored worst on detection got the work, not the ones that scored worst on severity. [The bridge. The counterintuitive detail is the proof that you ran these rather than read about them.] I write software the same way. Before I add a retry I ask what happens when the call succeeded and only the response was lost, because that is a high severity silent failure and it will never show up in an error log. On [project] that turned into idempotency keys on [endpoint] plus an alert on duplicate writes. Undetectable failure is the same enemy in both jobs. The difference is that here I can fix one on the same afternoon I find it.
| Previous career | Bridge that dies on contact | Bridge that lands |
|---|---|---|
| Teaching | "I am good at explaining things." | Error analysis: finding the shared false assumption behind a set of wrong answers. |
| Finance operations | "I have strong attention to detail." | Reconciliation: two sources must agree, and the break gets chased whatever its size. |
| Mechanical engineering | "Engineering is engineering." | FMEA: ranking failure modes by detectability, then designing for the silent ones. |
| Nursing or clinical | "I work well under pressure." | Handover: a fixed protocol for transferring state so nothing is lost between shifts. |
| Retail or hospitality management | "I am a people person." | Rota and stock forecasting under a constraint you had to defend to a district manager. |
Getting the same story into a resume-grounded copilot
If you plan to lean on a live tool during the call, the thing that goes wrong is almost never latency. It is that the drafted answer tells a different story from the one you rehearsed, because a copilot can only work from what your resume actually says. OfferPilot AI's Interview Copilot drafts from your own document and the company and role you set, so the fix sits upstream of the interview, in the document.
Rewrite the old-job bullets in engineering nouns
"Taught Year 9 science" gives a model nothing to reach for. "Ran item analysis across 120 scripts to locate the first wrong assumption before reteaching" gives it the bridge. Same job, same truth, retrievable content.
Put the bridge sentence on the resume verbatim
One line, phrased the way you would say it out loud. Anything a draft has to paraphrase comes back generic, and generic is the precise failure you are trying to avoid on this question.
Build the bank for that company and role
The company Q&A generator produces a question set for a named company and role. The motivation questions are the ones to read first here.
Read the draft and check it names your bridge
If the drafted answer says you are passionate about technology, the resume is still the problem. Edit the document, regenerate, and repeat until the draft reaches for reconciliation, or FMEA, or error analysis, by name.
Rehearse against it once, then stop reading it
In the call, use it as a reminder of the three beats for the moment your mind goes blank. Reading a paragraph aloud on this specific question sounds rehearsed in a way it does not on a technical one.
Three follow-ups arrive often enough to prepare for. "Why not just do software where you were?" is answered by naming the thing you did automate there and the ceiling you hit. "Are you comfortable being the most junior person again?" wants a recent instance of being corrected and what you changed, not a statement about your ego. "What if you get bored of this too?" is best answered with what specifically stopped working in the old field, because that is checkable and a promise is not. The interview questions bank covers the wider behavioural set these sit inside.
Where a live copilot is the wrong tool for this question
Worth saying plainly, given a vendor wrote this page. The bridge is a claim about your own history, and no model reading your resume can tell which of the four things you did last year a former manager would actually vouch for. That judgement is yours and it has to be made before the call, because this is the question most likely to be followed by "tell me more about that" thirty seconds later. There is a delivery cost too: a drafted answer read aloud sounds careful, and careful is the wrong texture for the one answer an interviewer expects to sound personal. Take the beats from it and say the rest in your own words.
Two hard limits. OfferPilot AI runs on Windows 10 and 11 only, with no macOS, Linux or mobile build, so on a Mac this page is a preparation exercise and nothing more. And if the honest reason for the switch is that you were pushed out of the old field, the three-beat structure still holds, but do not dress it up as a passion story. Say the field contracted, then go straight to the bridge. An interviewer who suspects a rewritten motive will spend the rest of the loop testing it, which costs you more time than the truth ever would.
Write one bridge sentence tonight. Say it out loud, and if it survives the question "would my old manager sign this?", put it on the resume word for word and build the rest of the answer around it. If you want the copilot in the call as well, the Windows download is free for five minutes a day with no card, and the clock only moves while it is actually hearing the interviewer, which is enough to work out whether a live draft helps you or gets in your way.
Related guides
- Bootcamp Grad Interview Questions: The 4 CS Grads Never Get
- Explaining a Career Gap in an Interview: 7 Scripts by Reason
- Tech Interviews Over 50: Reframes for the Five Coded Questions
- Technical Phone Screen: What to Expect in a 30-Minute Call
- Threat Modeling Interview Question: STRIDE on a Real System