Performance questions in a management interview follow a sequence: how you noticed someone was struggling, the first conversation, the plan and the support behind it, what you did when it was not enough, and how you kept it fair to the rest of the team. Prepare the whole sequence, not one story about a difficult employee. This page gives the question forms at each step, what a strong answer includes, the mistakes that undermine these answers, the follow-ups to expect, how to tell a story that ended in someone leaving, what to say if you have never had to do this, and how the questions vary by role.
Table of Contents
- 10 Performance Management Inte...
- How the interview is evaluated
- What performance questions are...
- Noticing the signal early
- The first conversation
- The plan and the support
- Escalation and letting someone...
- Fairness to the rest of the te...
- The high performer who is diff...
- If you have never had to do th...
- How the questions vary by role...
- Practice the conversation, not...
10 Performance Management Interview Questions and How to Answer Them
Question 1
How do you know when someone on your team is struggling?
What it tests
Whether you watch for concrete signals week to week rather than waiting for a formal review cycle, and whether you can name what you actually track.
What a strong answer includes
Names the specific signals you watch: commitments that miss the date you agreed, work coming back for rework, a quality or throughput number drifting, a change in how someone participates. Says how quickly you act once you see one, and shows you checked the cause before deciding what the problem was.
Sample answer
I watch three things week to week: whether commitments land on the date we agreed, how much work comes back for rework, and how someone shows up in our one to ones. An engineer on my team went from delivering steadily to missing two sprint commitments in a row, and his pull requests started needing several rounds of review. I raised it in our next one to one rather than waiting for the quarterly cycle. I asked what had changed before I said what I had seen. Nothing external had changed. He had taken on bigger tickets, was estimating them the way he estimated small ones, and was not asking for help when he got stuck. That was his to fix, and I said so. We agreed he would break anything over two days into smaller pieces and tell me at the midpoint if it was slipping. The first sprint after that he missed again and did not flag it, so we had a second, more direct conversation about what the agreement meant. It took about two months before his estimates were reliable. Catching it at two missed sprints meant that was a coaching conversation, not a formal one.
Question 2
Tell me about a time you noticed a performance problem before anyone else did.
What it tests
Whether you act on early evidence while the problem is still small, instead of waiting until it is visible to your own manager or the rest of the team.
What a strong answer includes
Gives the sequence with timing in it: what you saw, how long you watched before calling it a pattern, and what you did while nobody else knew. Names the evidence rather than describing a general instinct, and shows the conversation happened early enough that the fix was still cheap.
Sample answer
I ran a team in a call center, and one of my most experienced agents was still inside his handle time and call volume, so nothing showed on the dashboard. But when I listened to his recorded calls, he had started rushing customers to close and skipping the account checks. I listened to calls from two more weeks to be sure it was a pattern, then raised it privately with two specific calls. He told me he had been passed over for a team lead role and had stopped seeing the point of the extras. That was not something I could fix in an afternoon, and I did not pretend it was. I told him the checks were part of the job whatever happened with the promotion, and separately we talked through what the next lead role would need from him. His call quality came back within the month and I kept listening in. Nobody above me had known there was anything to know, and it stayed a conversation between the two of us.
Question 3
Tell me about a time you gave feedback someone did not want to hear.
What it tests
Whether the feedback was specific, private and soon after the event, and whether the person left the conversation able to repeat back what needed to change.
What a strong answer includes
Roughly quotes what you said instead of summarising it as "I gave feedback". Shows you listened for causes you had not seen, that the expectation was concrete rather than a trait like being more proactive, and that the conversation ended with something agreed and a date rather than something announced.
Sample answer
A senior person on my team had started cutting clients off in calls, and one client mentioned it to me. I asked for twenty minutes the same week, in private, and I did not open with praise. I said that in the last two calls he had answered before the client finished the question, gave both examples, and told him the client had noticed. He pushed back and said the questions were repetitive. I let him finish, then asked what would happen if that client stopped raising things at all. We agreed he would let the client finish and summarise the question back before answering, and that I would sit in on the next two calls and tell him what I saw. The second call was noticeably better and I told him so straight afterwards.
Question 4
How do you deliver a hard message without damaging the relationship?
What it tests
Whether you can be direct and still keep someone's trust, and whether your approach adapts to the person instead of following a script like the praise sandwich.
What a strong answer includes
Describes a method you can point at: private, soon, specific to what the person did rather than who they are, with room for them to respond and a plain statement of what happens next. Carries an example where the working relationship survived, and says how you knew it survived.
Sample answer
I keep the message short and the conversation long. I say the thing plainly in the first minute, with the specific example, so nobody is decoding hints, and then I spend the rest of the time listening. When I had to tell a shift lead that his handover notes were leaving the night team guessing, I said exactly that, showed him two shifts where work got redone because of it, and asked what was getting in the way. He was writing the notes at the end of a twelve hour shift with no template, which was a fair answer. We built a template together and I read the notes for two weeks. He told me later that being told straight was easier than the hinting he had had before, and he started bringing me his own problems earlier, which is how I knew the relationship was intact.
Question 5
Describe a performance improvement plan you ran. What happened?
What it tests
Whether accountability in your hands has dates, specific changes and checkpoints, and whether you can describe the outcome honestly whichever way it went.
What a strong answer includes
Sets out what had to change, by when, and how it would be measured, alongside what you provided to make the change possible. Walks each checkpoint and what you adjusted after it. Ends with the real outcome, whether the person recovered or left, without dressing it up.
Sample answer
A support lead on my team was missing response targets and escalating tickets she should have closed herself. We wrote a thirty day plan with three specific things in it: response time inside the agreed threshold on her own queue, no more than two escalations a week, and one call review with me every Friday. I cut her ticket load for the first fortnight and paired her with the strongest person on the team for the escalation calls. At the first checkpoint response times had improved and escalations had not, so we narrowed it to the two ticket types she was escalating most and I sat with her on each one. By day thirty she was inside all three measures, and she is still doing the job. What made it work was that she knew on day one exactly what success looked like and what I was giving her to get there.
Question 6
How do you support someone who is trying but not getting there?
What it tests
Whether you separate effort from capability and can say what support you actually provided, rather than restating the same expectation louder.
What a strong answer includes
Names the concrete support: time, training, a narrower scope, a different mix of work, a pairing, a change to how work reaches the person. Shows you diagnosed whether the gap was skill, scope or fit, and says how long you gave it before you were willing to conclude something else was needed.
Sample answer
An analyst on my team worked longer hours than anyone and still missed the mark, so more effort was obviously not the fix. I sat with her through one full piece of work to see where the time went, and she was rebuilding every query from scratch because nobody had shown her the shared library. That was a gap in how we onboarded her rather than a capability problem. I gave her two weeks with the person who wrote the library, cut her active projects from four to two while she learned it, and moved one deadline out to make room. Her turnaround on routine work roughly halved over the following month, but the open ended analysis, where she had to decide what question to ask, stayed hard for her after another six weeks of pairing. At that point I stopped treating it as a training gap and said so. We agreed to shift her mix towards the reporting and data quality work she was now fast at, and I moved the exploratory projects to others. It was not the job she was hired for, and we were both honest about that, but it stopped her spending another quarter trying harder at the wrong thing.
Question 7
Tell me about a time you had to let someone go.
What it tests
Whether you can tell the hardest story plainly: what you tried, over what period, how the process stayed fair, and what you took from it afterwards.
What a strong answer includes
Gives the sequence and the timeline, says when you brought in HR or your own manager under your organisation's process, and covers the day itself and the team afterwards. Ends on what you changed in how you hire, onboard or act early. Does not blame the person or the process, and does not linger on the drama.
Sample answer
I had a coordinator who did not recover after a clear conversation and the plan that followed it. The whole thing ran about four months: the first conversation, a six week plan with weekly checkpoints, and a change of scope towards the part of the job he was better at. He improved on some of it and not on the part the role most needed. Under our process I brought my HR partner in when the plan started, which meant he knew from the first week how it would run. The final conversation was short, in person, and contained no surprises, because everything in it had already been said. I told the team that day that he had left, gave them no details, and reallocated his work that week. What I changed afterwards was our hiring loop, because we had never tested the part of the job he could not do.
Question 8
When do you involve HR, and when is it too early?
What it tests
Whether you use your organisation's process as support for a fair sequence, or as somewhere to hand the problem off before you have had the conversation yourself.
What a strong answer includes
Draws a line you can defend under your organisation's process. Shows you had the direct conversation yourself first, can say when and why HR or your own manager came in, and never presented HR as the reason for the outcome.
Sample answer
The first conversation and the plan are mine. Going to HR before I have said anything directly to the person would be avoiding my own job. Where I work now, the process is that HR joins once a formal plan starts, and I follow it. The last time I ran a plan I called my HR partner the week we drafted it, not the week I concluded it had not worked, and she flagged that two of my checkpoints were too vague to be fair to the person. We rewrote them before he saw it. I have also had several situations that never went near HR because the conversation fixed the problem in a fortnight, which is the outcome I am aiming for every time.
Question 9
How do you keep things fair to the rest of the team while you are managing one person's underperformance?
What it tests
Whether you account for the people covering the gap, and whether you can keep one person's situation confidential while still making the standard visible to everyone else.
What a strong answer includes
Says what the team could see anyway, such as redistributed work or missed handovers, and what you told them: that a standard exists and is being held, with no details about the individual. Shows you rebalanced the workload deliberately rather than letting the strongest people absorb it quietly, and that the outcome left the standard credible.
Sample answer
The team usually knows before you say anything, because they are the ones redoing the work. While I was working through this with one of my technicians, two other people had quietly started checking his output before it shipped. I stopped that, because it was unrecognized work and it hid the problem from me. I told the team I was aware of the quality issue, that I was dealing with it directly, and that I would not discuss anyone's performance with them. Then I moved the checks onto a rota everyone shared for six weeks, so the extra load was visible and had an end date rather than being invisible and permanent. Nobody got details. What they got was evidence that the standard was real and that covering for it was not going to become their permanent job.
Question 10
How do you handle a top performer who treats colleagues badly?
What it tests
Whether the standard applies to everyone or bends for results, and whether you can weigh the trade-off out loud instead of avoiding the conversation.
What a strong answer includes
Treats behaviour as part of performance and runs the same private, specific conversation you would run about missed work. Names what the behaviour costs the rest of the team, states the trade-off you weighed and how you decided, and says plainly what would have happened if nothing changed.
Sample answer
A salesperson at the top of the board was rude to the operations team whenever orders slipped, and two of them had started routing his work around themselves to avoid dealing with him. I treated it as a performance problem, because it was costing the company hours every week. I told him privately, with two specific incidents and what each had cost, that his numbers did not buy him a different standard, and I asked what was driving it. He said he only found out about slipped orders from angry customers, which was fair, so I fixed the notification that week. The behaviour was still his to fix and I said what would happen if it did not. It did change, mostly, and I kept checking with the operations team rather than taking his word for it.
How the interview is evaluated
What performance questions are testing
Managing someone's performance is the part of the job that most clearly needs a manager rather than a senior colleague: a peer can advise, but setting the expectation, holding the line and deciding what happens next are normally part of the manager's role. That is why it is worth preparing this competency carefully, with specific stories rather than general principles.
A strong performance answer has a shape, and it is the shape of the work itself: the signal you saw, the conversation you had, the plan you agreed, the support you gave, and the outcome, whichever way it went. Prepare a story that covers the whole sequence and you can answer many performance questions from it, choosing where to start.
This competency sits inside the wider set of manager behavioral interview questions, and the management interviews guide covers how the whole interview is evaluated. The sections below follow the sequence.
Noticing the signal early
Question forms:
- How do you know when someone on your team is struggling?
- Tell me about a time you noticed a performance problem before anyone else did.
A strong answer names the signals you actually watch: missed commitments, work that needs rework, a change in how someone shows up, a number that drifted. It shows that you acted on the signal soon after you saw it, not at the next review cycle, and that you checked the cause before assuming it.
Failure modes: waiting for the review cycle or for someone else to raise it; treating one bad week as a pattern; and describing a system for monitoring people without a single example of using it.
The first conversation
Question forms:
- Tell me about a time you gave feedback someone did not want to hear.
- How do you deliver a hard message without damaging the relationship?
A strong answer shows a conversation that was private, held soon after the signal, and specific enough that the person could repeat back what you expected. It shows you listened for causes you had not seen, and that you ended with something agreed rather than something announced.
Failure modes: vague feedback ("be more proactive"); feedback delivered in public, by email, or wrapped in so much praise the message disappears; and a conversation that never happened because you fixed the work yourself.
Follow-ups to expect: "How did the person react?", "What did you learn about the cause?", and "What would you do differently?" When the conversation turns into a disagreement rather than a plan, the conflict management interview questions page covers how to tell that part.
The plan and the support
Question forms:
- Describe a performance improvement plan you ran. What happened?
- How do you support someone who is trying but not getting there?
A strong answer has dates, specific changes, and checkpoints, and it says what you provided: time, training, a clearer scope, a different mix of work, a pairing. It describes what you saw at each checkpoint and how you adjusted. A plan that ends with the person succeeding and one that ends with them leaving can both be strong answers if the process was fair and visible.
Failure modes: a plan that is a form rather than a conversation; no support, only expectations; and no checkpoints, so the next conversation is the final one.
When the real fix was giving someone ownership rather than more oversight, the delegation interview questions page covers how to tell that story.
Escalation and letting someone go
Question forms:
- Tell me about a time you had to let someone go.
- When do you involve HR, and when is it too early?
A strong answer tells the story plainly: what you tried, over what period, when and why you involved HR or your own manager under your organisation's process, how you made the process fair, and how you handled the day itself and the team afterwards. It ends with what you learned, ideally about hiring, onboarding or how early you act, because that is the part that shows you will manage differently next time.
Failure modes: hiding the story ("I have never had to do that") when you have; dwelling on it as a war story; and blaming HR for the process or the person for the outcome.
Follow-ups to expect: "How long did the whole thing take?", "What did the rest of the team know?", and "Would you act sooner now?"
Fairness to the rest of the team
The dimension easiest to leave out of a performance story is everyone else on the team. They see the missed work, they cover for it, and they watch what you do about it.
A strong answer says what the team saw and what you told them: that a standard exists and applies to everyone, without sharing what is confidential. It shows you protected the person's privacy and the team's trust at the same time, and that the outcome, either way, left the team believing the standard was real. Setting and holding that standard is leadership as much as performance management; the leadership interview questions page covers it from that side.
The high performer who is difficult
Question forms:
- How do you handle a top performer who treats colleagues badly?
This variant tests whether standards apply to everyone. A strong answer treats behaviour as performance, has the same private, specific conversation, and is honest about the trade-off you weighed and how you decided. An answer that makes an exception for results tends to read as a manager who will make the same exception again.
Failure modes: "their results speak for themselves"; delegating the problem to the people who suffer from it; and treating the behaviour as a personality issue rather than a standard.
If you have never had to do this
If you have never managed formal performance, say so, and bring the closest honest substitute: feedback you gave a peer that they did not want, a project member who was not delivering and what you did about it, someone you mentored through a rough patch. State the scope plainly, including what authority you did not have. The first-time manager interview guide covers how to draw this kind of evidence from experience that did not come with the title.
How the questions vary by role and level
The sequence is the same everywhere; what changes is the vocabulary and the numbers.
- Operations: shift leads and supervisors missing targets, with throughput or quality numbers as the signal. See the operations manager interview questions.
- Sales: reps under quota, with pipeline and activity as the early signal and coaching as the support. See the sales manager interview questions.
- Engineering: technical quality and delivery, where the hard part is often separating a skills gap from a scope or expectations problem. See the engineering manager interview questions.
- Senior managers: managing managers who themselves manage performance. Prepare for questions about a manager who avoids these conversations, and how you coached them through it.
Practice the conversation, not just the story
Performance questions have an unusual property: you can be asked to do the thing, not only describe it. "Show me how you would open that conversation" is a fair question and a hard one. Rehearse the feedback conversation itself out loud, in the first person, as well as the story about it.
A manager mock interview built for your target role can run both, the question about the conversation and the conversation itself, with feedback on each, so the vague opening or the missing expectation shows up before it matters.
Practice these questions out loud
Reading a list is silent rehearsal. Run a mock interview for your target role and get feedback on every answer.
Start a mock interview
About the author
Mock Interview Pro team · Interview coaching and practice
Mock Interview Pro runs mock interviews and practice sessions with per-answer feedback, so you can rehearse questions like these out loud before the real interview.
