The worst manager interview question checks how you handle a gap above you. Describe one management practice that didn’t work for you. Leave the person out of it. Then give four things in order. Name the practice in neutral words. Say what it cost on one real piece of work. Say what you did about it at the time. Finish with what you now ask for from a manager, or do yourself. Two answers fail. Venting tells the interviewer you might talk about them the same way one day. “I’ve never had a bad manager” fails too. It gives them nothing to score and suggests you’d hide problems. The interviewer wants to know if you noticed the gap, worked around it calmly and told someone. The rest of this post builds one Android engineer’s answer. Their manager made decisions out loud and never wrote them down.
Answer the question about practices, even if they asked about a person
Alison Green runs the advice column Ask a Manager. In a March 2015 post, she called the blunt version of this question terrible. Her fix was a better question to answer. Ask yourself which management styles or practices haven’t worked well for you. Then answer that one, even if the interviewer phrased it as “your worst manager.”
Ten years on, the reframe still holds. A practice can be described without judging anyone. “Decisions were made verbally and not recorded” is a fact about a process. “My manager was disorganized” is a verdict on a person. The interviewer can’t check either one. They can only hear which kind of sentence you reach for first.
The reframe also keeps the bad part short. The practice gets one or two sentences. Most of the answer goes to what you did. An answer weighted that way sounds fair.
Name a practice a good manager would recognize as missing
It helps to borrow a neutral vocabulary for what managers do. Google’s re:Work guide on the research behind great managers lists ten behaviors from its Project Oxygen study. The guide is dated August 2025. The list includes being a strong decision maker and a good communicator. It also includes supporting career development and not micromanaging.
Pick the behavior that was missing and describe its absence. A manager who never discussed your growth maps to career development. A manager who rewrote your pull requests maps to micromanagement. Each version names a gap any hiring manager knows. None of them needs an adjective about the person.
Avoid two choices. One is a practice the hiring manager clearly uses. If they mention daily check-ins, don’t make daily check-ins your complaint. The other is anything personal, legal or ethical. If your worst manager behaved badly in that way, this question isn’t the place for the details. Say the working relationship wasn’t a fit and talk about a smaller practice instead.
One Android team, one decision that was never written down
Take an Android engineer who worked under an engineering manager. The manager made decisions in one-on-ones and hallway chats. The manager was smart and approachable. But nothing was written down, so the decisions drifted.
The cost came on an image caching project. In a one-on-one, the manager agreed the team would use the image library’s built-in disk cache. Three weeks later, a product lead pushed for a custom cache with offline support. The manager agreed to that too. Nobody connected the two decisions. The engineer had already shipped the first approach behind a feature flag. The team spent two sprints building the second one. The first was then thrown away.
After every one-on-one, the engineer posted a short decision note in the team channel. It said what was decided, who decided and what it replaced. They also asked the manager for a thumbs-up on each note. Within a month, the manager started linking those notes in planning. The engineer now asks about decision records in every interview loop.
A full sample answer to the worst manager interview question
The practice that worked least well for me was decisions made verbally and never recorded. My manager at the time was approachable and quick to decide. But the decisions lived in one-on-ones. They could shift without anyone noticing.
It cost us on an image caching project. In one meeting we agreed to use our image library’s disk cache. Three weeks later, product asked for a custom offline cache. That was approved too. I’d already shipped the first version behind a flag. We spent two sprints on the second. Then the first was thrown away.
I should have caught the conflict sooner, because I was in both conversations. So I started posting a decision note after each one-on-one. It listed what we decided, who made the call and what it replaced. I asked my manager to react to each one. Within a month, they were linking the notes in planning.
Now I ask about decision records when I join a team. If there aren’t any, I start keeping them for my own area.
This is a sample answer written for this post. Swap in your own practice, project and numbers. Keep them true.
Each paragraph answers the follow-up that comes next
The first paragraph names the practice and gives the manager one real strength. The strength shows you can see a whole person while describing one gap. It also stops the answer from reading as a grievance.
The second paragraph is the cost. Two sprints and a discarded feature are things a team feels. Without a cost, the interviewer has to ask “so what?” With it, the gap is concrete and the answer stays short.
The third paragraph is the longest. It opens with what the candidate missed. Amazon’s Leadership Principles ask leaders to be “vocally self-critical,” under Earn Trust. Other companies phrase it differently. Owning your share keeps the answer from sounding like a complaint. The rest of the paragraph shows a fix the candidate made without waiting for permission. The manager approved each note, so the fix ran through them.
The last paragraph turns the story into what you need from the next team. It also shows you’d fill the gap yourself if no one else does. A hiring manager can picture that habit on their own team.
If the interviewer keeps pushing for something negative
Some interviewers will press after a practice-level answer. They may ask what you’d say about the person directly. Stay with behavior. Repeat the practice in one sentence and add how it felt to work under it. For example, “It was frustrating to rebuild work we’d already shipped.” Leave out any judgment of the person’s character.
If they ask a close cousin, like how you handled feedback from that manager, keep the stories separate. Our post on answering the critical feedback question covers that case. For a question about pushing back on a decision, see influence that ends in escalation.
Before the interview, write your own version in four short paragraphs. Read the first one alone. If it contains an adjective about the person, rewrite it as a practice. Then read the third one alone. If it doesn’t say what you did and what you missed, fix that one first.