OfferDrill.

Interview questions

The hard ones

How to explain being fired, without losing the room.

Being fired is a fact you can say out loud in about twenty seconds and then move past. This page shows you how to name it plainly, take the part that was yours, show what changed, and get back to the job you're interviewing for.

Why they ask it

They're not trying to catch you. By the time they ask, they usually already know something ended badly — either you told them, or the dates don't line up, or they're going to ask every candidate the same question. What they want to know is whether it's going to happen again on their team.

There are really three questions inside the one question. Do you understand what went wrong? Do you own your share of it without either collapsing into blame-taking or dumping it on someone else? And is it in the past — did something actually change?

There's a fourth thing they're watching that nobody says out loud: how you handle a hard moment in real time. If you get defensive, go vague, or talk for four minutes, they learn something about how you'll handle a hard moment on the job. If you answer it calmly and move on, they learn something better. A lot of people have been fired. The firing is rarely the disqualifier. The flinch is.

What not to say

How to build a strong answer

  1. Say it happened, in one clear sentence.
    "I was let go" or "I was fired" — pick one and say it early. Don't bury it in a story about reorganizations and new managers. Burying it makes the interviewer dig, and digging feels like catching. Leading with it takes the charge out of the room. If it helps, give the timing plainly too: "I was fired in March of [year], after [length of time] there."
  2. Give the real reason in a plain sentence or two.
    Not the legal language from the paperwork. Not a euphemism. The actual thing: you missed deadlines on a project, you and your manager couldn't get aligned after a reorg, your numbers were below target for two quarters, you made a judgment call that cost the company money. Say it at the level of detail you'd use telling a friend. If the story genuinely requires context — a role that changed under you, a manager conflict — give it in one clause, not one paragraph. Context stated once sounds like insight. Context repeated sounds like defense.
  3. Name your part. Just yours.
    This is the step that decides the answer. You're looking for the piece that was in your control — because that's the only piece you can promise to handle differently. "I should have raised the problem in week two instead of week eight." "I assumed I was meeting the bar and never asked directly." "I didn't build a relationship with my new manager and I waited for that to fix itself." Even in a firing you think was unfair, there's almost always something. Find it. If you genuinely believe there wasn't one, the honest version is: "I've thought about it a lot and the piece I keep coming back to is [the thing]" — but do the thinking first, because "nothing, it was all them" ends the conversation.
  4. Show what changed, then stop talking.
    One concrete thing. Not a personality claim — a behavior. "In my next role I set up a standing biweekly with my manager and brought a written status every time." "I started flagging risk the week I saw it, not the month it landed." If you've had a job since, point at the evidence there. If you haven't, say what you'd do differently and make it specific enough to be checkable. Then stop. Silence after a hard answer reads as steady. Filling it reads as worried. Let them ask the next question.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Fired for performance, and you've since worked somewhere else.

I was fired from [company] in [month, year]. I was in a sales role and my numbers were under target two quarters running. Looking back, the real problem was that I knew by week three of the first quarter that my pipeline was thin, and I didn't say anything — I kept thinking I'd close the gap before anyone noticed. By the time my manager and I talked about it, it was a review conversation instead of a fixable one. At [next company] I ran my pipeline review with my manager every other week whether the news was good or not, and when I was going to miss, she heard it from me first. That's the part I'd never do differently again.

The reason is stated flatly, the ownership is specific and behavioral rather than a vague apology, and the fix comes with evidence from a real job. It runs about forty seconds.

Fired after a conflict with a manager, and it's your most recent job.

I should be upfront — I was let go from [company] in [month, year]. My team got reorganized under a new manager about eight months in, and the two of us never got on the same page about what my role was supposed to be. I read her hands-off style as trust and kept my head down. She wanted a lot more visibility than I was giving her. That's on me — I never just asked her how she wanted to work, and I let it drift for months when a fifteen-minute conversation would have fixed it. It's the first thing I do now with anyone I report to. Honestly, I'd want to do that here in the first week.

It names a conflict without making the manager a villain, takes a piece that's genuinely the candidate's, and turns forward into the new job instead of lingering. No hedging about "differences in style."

Fired for a specific mistake, early career, and you don't have much track record since.

I was fired from my first job out of school, about [length of time] in. I was handling client scheduling and I made an error that cost a client a shipment window, and then — this is the part that actually got me fired — I tried to fix it quietly instead of telling my supervisor. She found out from the client. I was twenty-three and I thought admitting a mistake was worse than the mistake. It isn't, and I learned that the hard way. Since then, when I get something wrong, the person who needs to know hears it from me within the hour. I know I don't have years of track record to point at yet. But that one's settled for me.

It doesn't soften the worst detail — it leads with it. The self-awareness is real without being self-punishing, and it acknowledges the thin track record instead of hoping nobody notices.

What comes next

Answer this one well and the interviewer usually goes here:

  • What would you do differently if you were in that situation again?
  • How did your manager describe the problem at the time — what words did they use?
  • May we contact anyone from that company?
  • What did you do in the time between that job and now?
  • How do you handle feedback you disagree with?
  • What kind of manager do you work best with?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

Being fired is a thing that happened to you, not a description of you, and once you can say it in thirty calm seconds it stops being the thing you're dreading and becomes just another question on the list.