Leading an Engineering Team Back From Low Morale

You are interviewing for an engineering manager role, and the interviewer asks about leading people through a hard stretch: tell me about a time a team you led had low morale. How did you notice, what was causing it, what did you do about it, and what changed as a result? ```hint Cause before cure Separate the symptoms you saw from the causes you confirmed, and be ready to explain how you told the two apart. ``` ### Clarifying Questions - Should the example be a team I inherited in that state, or one whose morale dropped while I was leading it? - Is a case where the main cause came from outside the team, such as a reorganization, a good fit? - How much detail do you want on the outcome compared with the actions? ### What a Strong Answer Covers - Concrete signals of low morale (departures, transfer requests, disengaged meetings, missed commitments, survey or one-on-one themes) rather than "people seemed down" - A diagnosis drawn from one-on-ones and data that distinguishes causes such as unclear purpose, overload, lack of recognition, broken process or a difficult individual - Actions matched to causes, including at least one that required influencing the candidate's own management or peers - Honest handling of what could not be fixed, and how that was communicated to the team - Observable or measurable outcomes, and what the candidate would do differently next time ### Follow-up Questions - One senior engineer's negativity is spreading to the rest of the team. How do you handle that person? - How did you know morale had actually recovered rather than just gone quiet? - What did you tell the team when the cause was a leadership decision you disagreed with?