Most people handle the reason-for-leaving question twice: once out loud, and once in writing. The spoken version gets all the preparation. The written one, the line on a CV or the box on an application form, usually gets typed in thirty seconds, and it is the one that ends up stored on your candidate record for as long as that file exists.
Should your CV carry a reason for leaving at all?
In most markets, no. A standard CV lists the employer, the job title, the dates and what you achieved. There is no column for why each role ended, and recruiters do not expect one. When a reason appears next to every entry, it reads as defensive, as if you expect to be challenged before anyone has asked.
Candidates keep adding it anyway, and the motive is understandable. You had three short contracts in a row and you worry they look like three failures. So you write "(contract ended)" after each one to get ahead of the doubt. The instinct is right; the placement is wrong. A CV is a sales document, and every line spent explaining an exit is a line not spent on what you did in the job.
There are a few narrow exceptions where a short note on the CV helps more than it costs:
- Fixed-term or project roles that look like job-hopping without context. Putting "12-month contract" or "fixed-term, project delivered" in the job title line explains the pattern without a separate reason column.
- A site closure or company failure that is public knowledge. "Office closed, 2023" is a fact, not an excuse.
- Relocation when the next role is in another country or region. The move explains the break before the reader invents a worse story.
- Markets where it is customary. Some public-sector templates and a few national CV conventions still ask for it. If the template has the field, fill it. If it does not, do not create one.
Notice that every exception is framed as a fact about the role, not a justification. That is the test. If your note sounds like an argument, remove it.
The application form field is a different animal
The form is where the question becomes unavoidable. Many online application systems, and a lot of paper forms in the public sector, care homes, retail and finance, ask for a reason for leaving against every previous job. Some make it a required field. Some give you a dropdown; others give you a free-text box with a character limit that barely fits a sentence.
This is the constraint that matters. In an interview you have a minute, a tone of voice and a listener who can see you are relaxed about it. In the form you have perhaps forty characters and no tone at all. Whatever you type is read cold, by a screener who may be skimming fifty applications, and often by a filter before any human sees it.
Leaving the field blank is rarely a good idea when it is optional and never possible when it is required. A blank reads as avoidance. Writing "see CV" is worse, because the CV, correctly, does not say.
Short neutral formulations that work
The goal is a line that is true, short and closes the topic rather than opening it. Here are formulations that do that job:
- "End of fixed-term contract" for any contract that simply reached its end date.
- "Role made redundant (restructuring)" when the position disappeared.
- "Relocation" or "Relocated to [city]" when you moved.
- "Seeking a step up in responsibility" when you left for growth.
- "Company closure" or "Business ceased trading" when the employer is gone.
- "Returned to study" or "Career break, family" for a planned break.
- "Still employed" or "Currently employed, notice period X weeks" when you have not left yet. This one is forgotten surprisingly often, and it is the most useful thing a recruiter can read in that box.
What these have in common: they describe the situation, not your feelings about it. None of them names a manager, a salary or a disagreement. If a dropdown offers a close option, pick it and add nothing in the comments unless the form requires detail.
Avoid the lines that feel honest but land badly on paper: "personal reasons" (vague, invites a question), "better opportunity" (fine spoken, faintly transactional written), "management issues" (a red flag in any length), "mutual agreement" with no context (reads like a settlement you would rather not discuss).
Why the written version is read so literally
A spoken answer is judged as a performance. The listener weighs your tone, your ease, whether you pause, and forgives a clumsy word because the overall impression is calm. A written answer has none of that support. Every word is taken at face value.
"Left due to conflict with new director" might be a fair summary of a messy situation that you could explain in thirty relaxed seconds. On a form, it is simply a record that you had a conflict with your boss. Nobody reading it can hear that you have moved on.
The written line also travels. It is saved in the applicant tracking system, it may be forwarded to the hiring manager, it can resurface if you apply to the same employer next year, and it is the thing a reference check or a background screening firm compares against what your former employer reports. That is the practical reason to keep it boring. A boring line never becomes a problem six months later.
A spoken reason is heard once. A written reason is filed, forwarded and compared. Write it for the person who reads it last, not first.
Redundancy, and the one line for a dismissal
Redundancy is the easy case, even though it rarely feels easy. The role was removed, not you. "Role made redundant" or "Position eliminated in restructuring" is accurate and carries no stigma in any serious hiring process. Resist the urge to add a list of how many colleagues went with you or how unfair the process felt. If the form asks for detail, one clause is plenty: "Role made redundant following merger."
If you were dismissed
This deserves a separate, careful note, and only a short one here. If an employer ended your contract for performance or conduct, the written line must still be true, because the form often carries a declaration you sign, and because references and screening checks can contradict it. False statements on an application can be grounds for withdrawing an offer or for dismissal later, depending on the country and the contract.
True does not mean detailed. A short, neutral, factual line is enough: "Employment ended by employer" or "Contract terminated", and, where there is space, a few words that point forward, such as "happy to discuss at interview". That moves the conversation to the one place where you have tone and time on your side. Rules around what employers may disclose, and what you must declare, differ widely by jurisdiction, so check what applies where you are.
The written field and the spoken answer must match
Here is the rule candidates break most often. The screener reads the form. Later, the interviewer asks why you left, with that same form printed or open on screen. If the form says "End of contract" and you say you resigned to find something more senior, you have not given a bad answer. You have given two answers, and the gap between them is what gets noticed.
So write the form line first, then build your spoken explanation as a longer version of it, never a different one. The spoken answer can add context, colour and what you learned. It cannot change the facts. The same goes for your CV dates, your LinkedIn profile and whatever the reference will say. If you generate your CV from your LinkedIn data with a tool like Postulit, the dates at least will be consistent by construction, which removes one easy way for the two versions to drift apart.
What to do before your next application
Open a plain text file and write one reason-for-leaving line per past role, each under forty characters, each a fact rather than an opinion. Read them out loud and check that every one matches what you would say in an interview and what your former employer would confirm. Then remove any reasons you had added to your CV, keep only the context notes for fixed-term or closed roles, and paste from the file every time a form asks. Ten minutes of work, and the question stops being something you improvise under pressure.