EM: People Management

What was the most challenging performance management that you had to handle?

By Interview Clozo · Published 27 October 2026 · Last verified 26 October 2026 · 11 min read

The interview question "What was the most challenging performance management that you had to handle?" asks for one real case of a struggling employee, told in about a minute: what was wrong, what you did yourself and how it ended. The rubric line that separates levels is the diagnosis, meaning whether you ruled out unclear expectations first.

In this article

Before you start
Why interviewers ask this
Performance management from first principles
The Staff-level answer
The rubric
Three variants of this question
Common mistakes
Follow-up questions
Sources

Before you start

This page is one question in the engineering manager interview questions guide. It assumes you have managed or led at least one person, or can tell a case from a lead role.

Why interviewers ask this

A case story shows how a manager treats a person when the stakes are real, and that is hard to fake with principles alone. Underperformance does not only hurt one person's output; the Fair Work Ombudsman guide says it can also affect co-workers, customers and business productivity. A manager who avoids the conversation therefore costs the whole team.

Candidates report this question in engineering manager loops, usually inside the people-management round described on the people management round page. In our judgment, not a published scoring standard, a strong answer shows four things: a diagnosis of the cause, fair process, your own actions and an honest result. A weak answer blames the employee, says "we" throughout, or jumps straight to firing. A Staff-level answer adds what you would change next time.

Choose the case with care. Pick one that was hard for a reason you can name in one sentence: a former high performer who declined, a senior or well-liked engineer, a case you inherited, or a personal or health cause that needed human resources (HR) support.

Performance management from first principles

Underperformance: Underperformance is the failure of an employee to meet the requirements of the job at an acceptable level, as the guide for managers from the International Labour Organization (ILO) describes it. It is handled differently from misconduct, which is a breach of a workplace rule, because the cause and the fair response differ.

In plain words

Think of a football coach whose player keeps dropping passes. A good coach first asks why. Maybe the player lacks the skill. Maybe the play was never explained, or morale is low. Only then does the coach choose between extra drills and a harder talk about the squad.

The analogy breaks in one place. Workplace rules and employment law apply to an employee, and they vary by country and employer. So the process must also be fair and written down.

In one sentence: performance management is the set of steps a manager takes to close the gap between the work expected and the work delivered, starting with conversation and moving to a written plan only if needed.

Step 1: Diagnose whether it is can't do or won't do

Diagnose first whether the person can't do the work or won't do it. The guide for managers frames this as "Won't do" versus "Can't do". Misconduct is generally a failure to follow a workplace rule, and it follows a different route from underperformance.

Look for causes outside the person. The Fair Work Ombudsman guide lists low morale, a poor work environment, interpersonal differences and cultural misunderstandings. One cause is easy to overlook: unclear expectations. The ILO guide for managers says an employee "may legitimately argue that they did not know what was expected of them".

For an engineer, the evidence is concrete: missed sprint commitments, slow code reviews, defects that reach production. Collect facts, not impressions. Input: the pattern of work. Output: a hypothesis of skill gap, unclear goal, workload, morale or will. You now know which response fits.

Step 2: Clarify expectations and coach informally

The informal stage comes before any formal process. The University of Glasgow guidance note says good performance management uses a combination of formal and informal methods, and its note covers the informal stage specifically. Practice differs: at the University of Glasgow the informal discussion is itself recorded in a performance improvement plan (PIP) form, while the U.S. Office of Personnel Management (OPM) guide describes the PIP as a written document that states the consequences of not improving.

Meet the employee to discuss the problem once you have assessed it, as the Fair Work Ombudsman guide advises. Say what you observed, give examples, ask for their view and write the expectations down together. Then support them: pair them with a stronger colleague, remove a blocker, fix tooling or reduce load.

Meet often enough that feedback is never a surprise. The one-on-ones and hard feedback page covers how to say difficult things plainly. Input: your diagnosis. Output: written expectations and a support plan that the person has seen. Many cases end here, and your answer should say so if yours did.

Step 3: Use a formal plan only if informal coaching has not worked

A PIP is a written document, and the U.S. Office of Personnel Management quick guide says it includes the expectations and success criteria, the support to be provided and a description of the consequences of not improving. A written plan lists expectations, support and consequences. The same guide gives a typical duration of 30 business days; private-sector guidance such as Lattice says 30, 60 or 90 days, with check-ins typically weekly or biweekly. A plan of 30 calendar days with weekly check-ins gives 4 check-ins; the OPM figure counts business days, so it runs longer.¹

Make the goals measurable. An illustrative goal is cutting report revisions from an average of 5 edits to no more than 2, a 60% reduction.¹ PeopleGoal warns that a PIP should not be used for unclear expectations, lack of training or workload problems. Lattice puts the spirit this way: "A PIP isn't meant to punish employees, it's an opportunity to help them get back on track." Involve human resources (HR) early, because rules differ by country and employer.

Step 4: Close with the result and the lesson

Report what happened with a measure and an honest ending. In this illustrative case, the sprint-commitment hit rate rose from 50% to 80%, a gain of 30 percentage points, and review turnaround fell from 3 days to 1 day.¹ Pick measures that fit your case; the numbers here are hypothetical.

A mixed result is acceptable. The University of Cincinnati STAR guide says to highlight what you accomplished, learned or how you grew, even if the overall result was not positive. It also says to use "I" instead of "we", because here the interviewer is judging your own actions.

End with what you would change. That sentence is what makes a story read as judgment instead of luck. For the wider view of how you track a team over time, see team health as an engineering manager question.

Diagnosis comes first, and a formal plan is the third move, not the first.CC BY 4.0 — source: What was the most challenging performance management that you had to handle?

Step-by-step description

Decide can't do or won't do.
Write expectations and support.
Use a formal plan if coaching falls short.
Report the measure and the lesson.

Diagnose first whether the person can't do the work or won't do it.
A written plan lists expectations, support and consequences.

Knowing it is half the job. Saying it is the other half.

Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.

Start Free Trial →

The Staff-level answer

The answer below is illustrative. Replace the case with your own, keep the order and say it in your own words.