How do you handle Asshole Superstars ?

• How did you prepare for and initiate the conversation?

• What specific feedback did you provide and how?

• What boundaries, expectations, or improvement plans did you set?

• How did you follow up and monitor progress?

• What decision did you ultimately make about their continued role?

• How did the individual respond and did their behavior change?

• What was the impact on team dynamics and morale?

• What broader lessons did this reinforce about team culture?

• How did this influence your management approach going forward?

Sample Answer (Junior / New Grad) Situation: During my internship, I was leading a small hackathon project team of four people. One teammate was clearly the strongest coder—she built the entire backend in two days—but she would openly criticize other people's code during our standups, saying things like "this is amateur work" or "did you even test this?" Two other team members started contributing less and seemed demotivated.

Task: While I wasn't a formal manager, I was the designated team lead for the project. I needed to address the situation because we only had one week total, and I could see the team dynamics falling apart. I wanted to leverage her technical skills while making sure everyone felt respected and could contribute.

Action: I scheduled a one-on-one coffee chat with her and started by acknowledging her strong technical contributions. Then I shared specific examples of comments that had come across as dismissive and explained how I'd noticed other team members pulling back. I asked if she'd be willing to adjust her communication style—offering constructive feedback privately or through code review comments rather than in group settings. I also proposed that she focus on mentoring rather than criticizing, and I modeled this by asking her to pair program with one of the junior members.

Result: She was actually surprised by the feedback—she hadn't realized how her words were landing. She apologized to the team and started being much more encouraging. The last three days of the hackathon went smoothly, and we ended up winning second place. The experience taught me early on that technical excellence doesn't excuse harmful behavior, and that direct, respectful feedback is essential even in informal leadership roles.

Sample Answer (Mid-Level) Situation: I was managing a team of six engineers, and one senior engineer was consistently our top performer—he delivered complex features 30-40% faster than estimates and mentored junior engineers effectively on technical problems. However, he had a pattern of making dismissive comments during sprint planning, would sometimes bypass our code review process claiming his code didn't need review, and sent several emails with a condescending tone when challenging product decisions. Two team members privately told me they felt uncomfortable speaking up in meetings when he was present.

Task: As the engineering manager, I needed to address this quickly. My responsibility was to maintain both team velocity and team health. I recognized that losing him would be a significant setback for our roadmap, but I also knew that tolerating this behavior would erode team trust and psychological safety. I needed to set clear expectations and see if he could change.

Action: I scheduled a private meeting and came prepared with specific examples and impact data. I led with appreciation for his technical contributions, then clearly stated that his behavior was creating problems—citing the specific instances and their effects on team morale. I explained our company values around collaboration and respect, and made it clear these weren't optional even for top performers. We agreed on a 90-day improvement plan with specific behavioral goals: participation in all code reviews, constructive tone in written communication, and soliciting input from quieter team members in meetings. I scheduled bi-weekly check-ins and also asked our skip-level manager to observe some of our team meetings.

Result: The first month was rocky—he improved in meetings but still had moments of impatience in Slack. I provided real-time feedback each time. By month two, I saw genuine improvement; he even apologized publicly in a retrospective for past behavior. After 90 days, the team's psychological safety scores in our survey improved by 25%, and three team members specifically mentioned feeling more comfortable contributing ideas. He remained a strong technical contributor while becoming a better team player. This experience reinforced that addressing behavior issues early and directly, with clear expectations and accountability, is crucial for maintaining healthy teams.

Common Mistakes

• Avoiding the problem -- waiting too long to address toxic behavior and hoping it will resolve itself naturally
• Overemphasizing performance -- justifying bad behavior because someone delivers results, ignoring the team-wide productivity cost
• Vague feedback -- giving general comments about "attitude" instead of citing specific behaviors and their impacts
• No follow-through -- setting expectations but failing to monitor progress or enforce consequences when behavior doesn't change
• Making it personal -- framing the conversation as a personality conflict rather than specific behaviors that violate team norms
• Ignoring team impact -- focusing only on the individual without acknowledging or measuring the effect on team morale and retention

Result: Terminating a staff engineer was difficult and did create short-term delivery pressure on the data platform. However, within one month, multiple engineers told me the team environment had dramatically improved—our next engagement survey showed a 35% increase in psychological safety scores. The two engineers who had been considering leaving stayed and stepped up to own parts of the platform. We successfully transitioned 90% of her critical knowledge through documentation and pairing. Most importantly, this decision sent a clear message across the engineering organization that brilliant jerks wouldn't be tolerated, which actually helped us attract and retain talent aligned with our values. I learned that protecting team culture sometimes requires making hard personnel decisions, even when there's a short-term cost, and that no individual should be irreplaceable.