Engineering Manager Behavioral: Struggling Engineers and Sustained Underperformance

The people-management part of an engineering manager screening interview probes, in depth, how you handle team members who are not doing well. Three prompts from the loop belong together: a story about supporting an engineer on your team through a rough patch, a story about managing someone whose performance fell below the bar, and the toughest people-management problem you have had to handle. Answer the two Parts below with real situations from your own experience, and treat the third prompt as asking which of them was the hardest challenge for you as a manager, and why. Expect the interviewer to dig into one story with many follow-up questions rather than accept a polished summary. ### Clarifying Questions - Should the stories involve your direct reports, or do engineers you led without formal authority count? - Does the interviewer want two different people for the two Parts, or one person whose situation moved from struggling to formal underperformance? - How much detail about formal performance processes is appropriate to share? ### Part 1 — Helping a team member who was struggling Describe a specific time an engineer on your team was struggling, and what you did. Explain how you noticed, how you found the cause, what support you put in place, and how it turned out. ```hint Symptom versus cause Separate what you observed from why it was happening; the right support for an unclear expectation, a skill gap, overload or a personal issue is very different. ``` #### What This Part Should Cover - The early signals and the first conversation - A diagnosis of the cause made together with the person - A concrete support plan and how progress was checked - The outcome for the person and for the team ### Part 2 — Dealing with sustained underperformance Describe a time when someone's performance stayed below expectations and you had to act as their manager. Walk through how you set expectations, gave feedback, documented progress and escalated, and what the outcome was, whether the person recovered or left the team. ```hint When coaching becomes a plan Show the point at which informal coaching turned into clear written expectations with a timeline, and how you stayed fair to both the person and the rest of the team. ``` #### What This Part Should Cover - Specific expectations and feedback grounded in examples - A structured plan with a timeline, in partnership with HR and your own manager - Balancing empathy and accountability, and managing the impact on the team - A decisive outcome and what the manager learned ### What a Strong Answer Covers - Real, specific stories in which the manager's own actions are clear - Early detection through regular one-on-ones and attention to the work itself - Fairness: the same bar for everyone, documented evidence, no surprises - Protecting the team's workload while respecting the individual's privacy - Reflection on what the manager would do earlier next time, and any systemic fix ### Follow-up Questions - At what point did you decide coaching was not working, and what evidence did you use? - How did you handle the rest of the team, who could see the impact but not the process? - Tell me about a time your diagnosis of a struggling engineer was wrong. What did you miss? - How would you handle the same situation if the underperformer were a senior engineer the team relied on?