How to explain a disputed firing on your CV

What does the contested OpenAI firing show about wording your exit?

A contested firing turns into a document problem almost immediately: the employer's account of why you left can be public before you've written a single line of your new CV. On or around 1 October 2026, three OpenAI safety researchers — Jasmine Wang, Tomek Korbak and Mikita Balesni — were dismissed, with the company pointing to violations of its policies on accessing and handling sensitive company information. On 8 October, the three published an open letter addressed to OpenAI's board and its safety committees, denying that they had mishandled sensitive information outside established procedures and warning that terminations carried out and communicated so abruptly were chilling the open culture the company had long prized.

OpenAI's side didn't match theirs. An internal memo attributed to a research leader praised the three researchers' contributions while rejecting any suggestion of retaliation, stating plainly that the company does not terminate employees for raising concerns. A spokesperson separately referred to an investigation that found a pattern of misconduct going beyond sharing information with an outside evaluation group, without specifying which policies had been breached. Wang said publicly that her access to an executive's email had been granted for recruiting work and that she asked IT to revoke it once she was finished. Balesni said he believed the group was let go for putting safety ahead of the company's near-term commercial interests.

Two irreconcilable accounts, no adjudication, and no neutral referee — that's the shape of almost every disputed dismissal, even the quiet ones. Most people in this position don't get an open letter or a news cycle. They get a termination date, a half-finished severance conversation, and an application form to fill in by Friday. The CV has to carry a version of events that survives an employment verification without trying to re-litigate the dispute in a bullet point. That's a writing problem with a right answer, and the right answer is far more restrained than most people's instinct when they feel wronged.

What should your CV actually say about being fired?

Your CV should say nothing about it. List the role exactly as you would any other: job title, employer, honest start and end dates, and three to five achievement bullets. There is no "reason for leaving" field on a CV, there never was, and adding one — even phrased sympathetically — invites a conversation you can't control on paper. Recruiters skimming a shortlist are not looking for an explanation of your exit; they're looking for whether you did the work. Volunteering "role ended following a disagreement over internal policy" in a bullet achieves one thing: it moves the firing to the top of the reader's mind before a single accomplishment registers.

Where people get into real trouble is the small, tempting edits around the edges. Don't stretch the end date to close a gap — verification pulls dates from payroll and HR records, and a two-month discrepancy reads as deception about something far more serious than the firing itself. Don't downgrade or inflate a job title either, because the title your former employer confirms is the title on file. Keep the entry boringly accurate and let the achievements do the work. If you were mid-project when it ended, write the bullet in the past tense around what you delivered, not around how the role concluded.

If months have passed since the exit, it's the gap recruiters notice first, not the dismissal. One plain line in your summary or cover letter covers it — a sentence naming what you've done since, whether that's contract work, a certification or caring responsibilities — and there's more detail in this guide on how to account for a long employment gap. My advice if the old CV was built for the job you just lost: rebuild the entry rather than patching it. Starting fresh in a clean, single-column layout and rewriting the role from scratch strips out the defensive hedging that creeps into edited files.

When the same facts have to appear in four different places, consistency matters more than eloquence. Here's the split that works.

How do you word a dismissal tied to confidentiality or policy allegations?

Describe the shape of the dispute, never its subject matter. For a dismissal involving confidentiality, data access or an internal policy, the correct wording names the category and stops: "My employment ended after a disagreement about how an internal policy applied to work I'd been assigned." That sentence is true, it's brief, and it doesn't repeat the allegation in your own voice — which matters, because an interviewer who hears you summarise the accusation will remember your summary, not your rebuttal. Resist the urge to prove the technical details were innocuous. Explaining precisely which system you accessed and why usually demonstrates exactly the thing a nervous hiring manager fears: that you'll discuss sensitive internal matters with outsiders.

Before you write anything, read what you signed. A separation agreement may contain a mutual non-disparagement clause, which constrains your wording but also constrains theirs — useful leverage when you ask HR what they'll confirm. Your NDA almost certainly survives the termination, so anything covered by it stays off the table regardless of how unfair the exit felt. If a claim, grievance or arbitration is live, run your interview wording past your lawyer once; a single sentence that contradicts your filing is a genuinely expensive mistake. And check whether the separation was recorded as a termination or a resignation in lieu, because that label is what shows up later.

The phrase that does the most work is a controlled refusal paired with an open offer. Something like: "I'm limited in what I can discuss about the circumstances, and I don't share my former employer's characterisation of them. What I can do is walk you through the work itself and introduce you to two people who managed it." You've acknowledged the dispute exists, declined to argue it, and redirected to verifiable evidence. In regulated fields where disclosure obligations bite — finance, healthcare, security clearance work, or roles with statutory background checks — find out what you're legally required to declare before you decide what to volunteer.

Which script should you use when the interviewer asks directly?

Use one of three scripts, chosen by how much you can say and how much you're prepared to own: the neutral-facts script, the accountability script, or the constrained script. All three run to two or three sentences and roughly twenty to thirty seconds. All three end by moving forward rather than inviting follow-up. Pick one before the interview, say it out loud until it sounds like speech instead of recitation, and don't improvise a fourth version under pressure. The structure is always the same: one sentence on what happened, one on what you took from it or what you'd do differently, one on what you've done since.

The neutral-facts script suits a dismissal where you genuinely did nothing wrong and can't prove it: "My employment ended at my employer's decision after a disagreement over an internal process. I'd handle the escalation differently now — I'd put it in writing to my manager earlier. Since then I've been contracting with two clients in the same space." The accountability script fits when there's a sliver you can own: "I was let go after a policy breach I didn't agree was a breach. I should have asked for written sign-off before I started, and that's now the first thing I do on anything sensitive."

The constrained script is for live legal matters or binding agreements: "My employment was terminated and I'm not in a position to discuss the circumstances in detail. I'd rather not characterise it unfairly to either side. I'm happy to put you in touch with the two managers I reported to on the project." Now the blunt part, and it's the thing people most resist hearing: winning the argument costs you the job. Every time you explain why the firing was unjust, the interviewer hears someone who blames others. Being right is not a hiring criterion; being safe to employ is.

When is staying silent the smarter move?

Stay silent on the CV and in the cover letter always. Stay silent in the interview until you're asked directly, or until a question makes the departure obviously relevant. Never stay silent on a form that asks you a direct yes-or-no question — that's where silence stops being discretion and becomes a falsified application, which is the one version of this that costs you an offer after you've already accepted it. The distinction is simple: declining to volunteer information is normal and expected. Answering a specific question falsely, or ticking "resigned" when the record says otherwise, is a different category of problem entirely.

The three silences that reliably backfire are worth naming. Dropping the job from your CV creates an unexplained gap plus a verification mismatch, and unexplained gaps combined with an employer nobody can reach read as a red flag to any experienced recruiter. Recasting a dismissal as a layoff looks safe until a screening vendor asks about rehire eligibility and gets a "no". And telling three slightly different stories across the form, the interview and your referees does more damage than the firing ever would. If disclosure rules are part of your situation, the mechanics of sequencing an admission are covered in this walkthrough of when disclosure is actually required and how screening is sequenced.

Do three things before you send the next application. Call whoever handles employment verification at your former employer and ask what they release — many companies confirm dates and title only as a matter of risk policy, though some screening vendors also ask about rehire eligibility and whether the separation was voluntary. Line up a referee who wasn't part of the decision: a peer, a client, a manager from the project rather than the panel. Then read the file as a stranger would. A free CV check gives you a score out of 100, five category scores including ATS compatibility, and a layout analysis; the paid Full Analysis adds the fix list and a "why you might be rejected" read.

Frequently asked questions