OfferDrill.

Interview questions

The hard ones

How to explain wanting to go back to an individual contributor role.

You managed people, you don't want to anymore, and you're afraid the interviewer will hear that as "couldn't hack it." This page gives you a short, honest way to say it that points forward instead of backward, plus answers for the follow-ups that come next.

Why they ask it

They're not judging you. They're doing math. Hiring an ex-manager into an IC seat raises three practical questions, and the interviewer needs all three answered before they can move on.

First: will you be bored or resentful in six months and leave? Backfilling a role twice in a year is expensive, and that fear is the real one behind the question. Second: can you actually still do the work? If you spent four years in one-on-ones and roadmap meetings, they want to know your hands still work. Third: will you be hard to manage? Some ex-managers second-guess their new boss, hold onto authority they no longer have, or treat the team as their former team. That's a real pattern and they've seen it.

Notice that none of those questions are "were you a good manager?" The interviewer mostly doesn't care. They care about what happens after they hire you. Answer those three things and the question dies quietly.

What not to say

How to build a strong answer

  1. Say the choice out loud, in one sentence, without apology.
    Start with the decision, not the backstory. "I moved into management for [number] years, and I've decided I want to go back to building." Flat tone. No wince. The way you say it teaches them how to hear it. If you deliver it like a confession, they'll receive it as one. If you deliver it like a preference, like saying you prefer working in the office, they'll receive it that way too.
  2. Give one real reason, and make it about the work you want, not the work you're escaping.
    Pick the truest thing and say it plainly: you liked the days you spent solving problems more than the days you spent in meetings. You found the management work drained you and the technical work fed you. Both of those are honest and neither one blames anyone. One reason is enough. Two is a list. Three sounds like you're arguing with yourself.
  3. Prove your hands still work.
    This is the part most people skip, and it's the part that actually moves the needle. Name something concrete you did recently that's hands-on. A project you kept a piece of yourself. A tool you learned. A certification, a side build, contract work, the messy migration you personally ran because nobody else could. Give the specific thing, not "I stayed close to the work." If you've been away from the tools for a while, say that honestly and say what you've done to close the gap.
  4. Close the door on the fear: you're not waiting for a management seat.
    Say it directly, once. "To be clear, I'm not looking at this as a step toward managing again. I want this job, as it's written." If that's not true, don't say it. But if it is true, saying it out loud removes the single biggest objection they have, and nothing else in your answer does that job.
  5. Then stop talking.
    The whole answer is forty-five seconds. Over-explaining is what makes it sound like a wound. Say your piece, close your mouth, let them ask the next thing.

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.

You chose to step down, or you're choosing it now, and nothing bad happened.

I managed a team of [number] for about [number] years. I was decent at it, and I'm glad I did it — I understand now how decisions get made above me, and that's made me better at my actual craft. But the honest version is that the parts of the job I looked forward to were the parts I was doing at seven in the morning before anyone else logged on. That was the building. Everything else was fine, but it wasn't what I wanted my day to be. So I'm going back to it on purpose. I've kept my hands in — last year I [the specific project or technical work you personally did]. And to be clear, I'm not treating this as a stop on the way back to managing. I want to do this work.

It's short, it credits the management years instead of trashing them, it gives one concrete proof you can still do the job, and it kills the "he'll want my seat in a year" worry in a single sentence.

You were laid off from a management role and you're applying to IC jobs, partly because that's what's open.

My role was cut in [month/year] when they flattened the org — my whole layer went. So I've been thinking hard about what I actually want next, and I keep landing on the same place. I got into this field because I liked doing the work, and managing moved me further from it every year. I'm not going to pretend market conditions aren't part of why I'm looking at IC roles. They are. But when I read this job description, my reaction was genuine interest, not compromise. I've spent the last [number] months [the specific thing — a course, a build, contract work, refreshing a skill], because I knew I'd need to be sharp, not just experienced. If you hire me, you're getting someone who's relieved to be back on the tools.

It names the layoff with a date and moves on. It admits the market is a factor — which the interviewer already suspected, so denying it costs you credibility — and then gives a real reason that stands on its own.

Management genuinely didn't suit you, and you'd rather not pretend otherwise.

I'll be straight with you. I took the management job because it was the only promotion available, and it turned out not to fit me. I could do the work, but carrying other people's performance problems and running that much of my day in meetings wore me down in a way the technical work never has. I stayed [length of time], did the job properly, and then made the call that I'd rather be good at something I'm suited for than adequate at something I'm not. Since then I've [the specific hands-on work you've done]. I know exactly what I'm signing up for here, and it's what I want.

"It turned out not to fit me" is honest without being self-destructive. Owning a mismatch reads as self-knowledge. Most interviewers respect it more than a polished story, because they've seen the polished story a hundred times.

What comes next

Answer this one well and the interviewer usually goes here:

  • "What will you do when you disagree with your manager's decision?"
  • "How do you feel about reporting to someone younger or less experienced than you?"
  • "How current are your skills? Walk me through the last thing you built or shipped yourself."
  • "If a lead or management role opened up here in a year, would you take it?"
  • "What did you like about managing?"
  • "Why should we believe you won't get restless?"
  • "This role pays less than your last one. Is that going to be a problem?"

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

Wanting to do the work instead of supervising it isn't a step down, and the people worth working for already know that — your job in the room is just to say it once, clearly, and let it be ordinary.