The Question
BehavioralManaging the Brilliant Jerk
Tell me about a time you worked with a highly talented individual who was not a team player. How did you identify the impact of their behavior, what specific steps did you take to coach them or address the situation, and what was the ultimate outcome for both the individual and the team?
Senior Level
Conflict Resolution
Emotional Intelligence
Performance Management
Coaching
Leadership
Accountability
Psychological Safety
Questions & Insights
Clarifying Questions
Is the individual a direct report or a peer? The leverage and approach for feedback differ significantly between coaching a subordinate and influencing a peer.
Is this a sudden change in behavior or a long-term pattern? Sudden changes usually signal external stressors or burnout, while patterns suggest a cultural or personality misalignment.
How is their technical performance? Are we dealing with a "brilliant jerk" (high output, low collaboration) or someone who is underperforming across the board?
Assumptions for this answer: I am the Team Lead. The individual is a Senior Engineer who is technically excellent but works in a silo, ignores communication protocols, and is becoming a bottleneck. This is a long-term pattern that is beginning to affect team morale.
Coach Strategy
Signals: Emotional Intelligence (EQ), Conflict Resolution, Coaching, Performance Management, Accountability, Psychological Safety, and Values Alignment.
Objective Diagnosis: A leader must distinguish between "lack of skill" (doesn't know how to collaborate) and "lack of will" (doesn't want to).
The "Brilliant Jerk" Trap: The interviewer wants to see if you have the courage to address toxic behavior even if the person is a high technical achiever. Neglecting this destroys team culture.
Cheat Code: Use the "Impact over Intent" framework. Don't attack the person's character; describe the measurable impact their behavior has on the project's velocity and the team's well-being.
Strategy Breakdown
The STAR Narrative
Situation – Context
I was leading a high-priority architectural migration with a team of eight engineers.
One Senior Engineer, "David," was arguably the most technically gifted person on the team but was a classic "silo."
He frequently bypassed our agreed-upon RFC (Request for Comments) process, committed large chunks of code without peer review, and was often dismissive of more junior members during stand-ups.
Task – Your Responsibility
As the Tech Lead, my goal was to maintain project velocity without sacrificing team cohesion or code quality.
I needed to transition David from being an "individual hero" to a "team multiplier."
The stakes were high: two junior engineers had expressed frustration, and our "Bus Factor" was dangerously low because David was the only one who understood the core logic of the new system.
Action – What You Did
Data Gathering & Preparation: Before speaking with him, I documented three specific instances where his lack of collaboration led to rework or delayed the team, ensuring the conversation remained objective and fact-based.
The Radical Candor 1:1: I held a private meeting where I used the "Situation-Behavior-Impact" (SBI) model. I told him: "When you push code without an RFC, the team cannot plan their dependencies, which led to a 2-day delay last week."
Identifying the Root Cause: I asked open-ended questions to understand his perspective. It turned out he felt the "process" was a bureaucratic hurdle that slowed his creativity.
Setting the Bar: I redefined his performance expectations. I explained that at a Senior level, his "output" was no longer just his code, but the team's ability to ship. I made "mentorship" and "code review quality" explicit KPIs for his next cycle.
Systemic Changes: To make it easier for him to comply, I streamlined the RFC template and invited him to lead the "Architecture Review Board" so he felt a sense of ownership over the processes he previously ignored.
Result – Outcome & Impact
Within one quarter, David’s PR participation increased by 60%.
He successfully mentored a mid-level engineer to take over the core module, increasing our team’s Bus Factor.
Team sentiment scores in our anonymous monthly pulse survey rose from 3.4/5 to 4.6/5.
We delivered the migration on schedule, with a significantly lower defect rate due to the increased peer oversight.
Learning / Reflection – Growth
I learned that "Technical Leadership" is 20% technology and 80% psychology.
Ignoring a high-performing non-team player is a debt that eventually bankrupts a team's culture.
I now integrate "collaboration expectations" into the very first week of onboarding for any new hire to prevent these patterns from forming.