OfferDrill.

Interview questions

The hard ones

What would your last manager say about you?

This is the question that feels like a trap when your last manager is part of the reason you're gone. Here's what the interviewer is actually listening for, the four answers that sink people, and a way to tell the truth about a rough relationship without sounding bitter or evasive.

Why they ask it

They're checking three things at once. First, whether your view of yourself matches what someone who watched you work every day would say. Second, whether you can hear feedback without getting defensive. Third — and this is the big one when the relationship went badly — how you talk about people who aren't in the room.

That third thing carries most of the weight. Interviewers know that about half of all managers are below average, and that plenty of good people leave because of one. Nobody expects you to have loved your boss. What they're watching is whether you can describe a hard situation in flat, factual language, or whether the temperature in the room goes up when you talk about it.

There's also a quiet practical piece. They may call this person. So they want to know what you think that call would sound like. An answer that matches the eventual reference is worth far more than a glowing one that doesn't.

What not to say

Any version of "honestly, we didn't get along, and here's why." Then two minutes about the reorg, the credit they took, the way they ran meetings.

Even when every word is true, the interviewer only sees one person in the room with a complaint. They have no way to check your story, so they file it under risk. The cost is real: hiring managers routinely say the badmouthing answer is what ended the interview in their head, even if they finished it politely.

"You'd have to ask them." Or a laugh and "probably nothing good."

It reads as a dodge, and it tells them the relationship was bad without giving them a single reassuring fact. You've paid the whole price of the awkward truth and gotten none of the credit for handling it.

The flawless review. "She'd say I was her strongest performer, always went above and beyond, great attitude."

No manager talks like that, and three superlatives in a row sounds like a press release. It also sets up a bad moment if they ask for the other half — "and what would she say you needed to work on?" — and you have nothing ready.

Generic adjectives with nothing under them. "Hardworking, reliable, team player."

That answer never scores a point. It's what everyone says, so it tells the interviewer nothing about you and gets forgotten before you leave the parking lot.

How to build a strong answer

  1. Lead with what they'd actually say about your work.
    Not your personality — your work. Two or three specifics they saw with their own eyes. "He'd say I was the person who caught problems in the data before they went out," or "She'd say I ran the month-end close and she stopped checking it after the first quarter." If you got written feedback or a review, borrow the language from it. Real detail is what makes this believable, and it's what they remember.
  2. Name one real development area, then say what you did about it.
    Pick something genuine and low-stakes for the job you want. "He'd say I was slow to ask for help — I'd sit with a problem too long before flagging it. I've gotten better at that; now I set a rule that if I'm stuck two hours, I raise it." The fix at the end is what turns a weakness into evidence that you can take feedback. Don't pick something central to the role, and don't do the fake weakness. "Too much of a perfectionist" is heard as "I won't answer this."
  3. If the relationship was genuinely bad, say so in one short, neutral sentence — then go back to the work.
    You don't hide it and you don't dwell on it. Something like: "I'll be straight with you — he and I didn't work well together, and that's part of why I started looking. On the work itself, I think he'd tell you [the specific thing]." One sentence. No story, no evidence, no proving you were right. If you can name a structural reason rather than a character one — different working styles, a change in what the role was after the reorg, a new manager who wanted the function run a different way — use it. That's honest and it's harder to argue with. Then stop talking. The silence after a short, calm answer works in your favor. Most interviewers move on.
  4. Say what a good working relationship looks like for you.
    Ten seconds, forward-looking. "What works best for me is a manager who tells me what the priority is and lets me figure out the how, with a standing check-in." This quietly answers the question they haven't asked — will this happen again with us — and it shifts the conversation from your last job to this one. It also gives them useful information. If they can't offer that, better you both know.

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.

The relationship was bad, and it's part of why you left.

I'll be honest with you — my last manager and I didn't work well together. He came in during the reorg and wanted the team run more hands-on than I'd been used to, and we never really got in sync on that. That's part of why I started looking. On the work, I think he'd tell you I owned [the specific process or account] and it ran clean — he'd also say I was slower than he wanted to loop him in on things. That's fair. I've changed how I work on that: I send a short Friday summary now whether anyone asks for it or not, and it's headed off a lot. What I'm looking for here is a manager who sets the priorities clearly and then lets me run at them, with a regular check-in so nothing's a surprise.

The hard fact is out in the first ten seconds, in neutral language, with a structural reason instead of a character attack. Then it moves to specifics about the work and ends looking forward. Adapt it with your own details — this is an example, not a script, and it will sound wrong if you memorize it.

Laid off, and the manager relationship was fine or good.

She'd say I was the one she handed the messy problems to. When [the system migration] went sideways, she put me on it because she knew I'd stay with it until it was sorted. She'd also say I take on too much — I had a hard time saying no when other teams asked for things, and it stretched me thin a couple of quarters. She told me that directly in my last review. I've gotten more deliberate about it since; I ask what it would push back before I say yes. The layoff was [the whole department / a 15 percent cut across the company] — she actually offered to be a reference, and I can put you in touch.

Concrete, includes a real flaw with a real fix, and the reference offer at the end is the strongest possible proof. Only say that last part if it's true and you've asked her.

Early career — the only manager you've had was at an internship or a first job.

My manager at [the internship] would say I picked things up fast and asked a lot of questions — maybe too many at first. I didn't want to guess and get it wrong. By the second month I'd figured out which things I could just look up and which ones actually needed her, and she noticed that. The thing she'd probably lead with is that I finished the [competitive analysis / weekly reporting] she'd been putting off for months, and it was still being used after I left. What I'd want from a manager here is someone who'll tell me straight when something isn't good enough, because that's how I got better there.

Doesn't pretend to more experience than you have. The learning curve is the story, which is the right story at this stage, and the ask at the end reads as someone who wants to be coached.

What comes next

Answer this one well and the interviewer usually goes here:

  • What would they say you needed to improve? (Have this ready even if you already gave one — they sometimes ask twice.)
  • Can we contact them for a reference?
  • Why did you leave, then? (Your answer here has to match what you just said about the manager.)
  • What kind of manager do you work best with?
  • Tell me about a time you got feedback you disagreed with.
  • How did you handle it when you and your manager saw something differently?
  • Was there anything you could have done differently in that relationship?

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

You don't have to make your last manager sound great, and you don't have to pretend it was fine — you just have to say one true, short thing about it and then talk about your work, which is the part they're hiring.