The Question

Managing High-Impact, Low-Collaboration Individual

Describe a situation where a technically competent team member was not collaborating effectively or was negatively impacting team culture. How did you diagnose the issue, what actions did you take to coach them, and what was the ultimate impact on the team's performance?

Senior Level

Leadership

Conflict Resolution

Coaching

Teamwork

Performance Management

Emotional Intelligence

Questions & Insights

Clarifying Questions

How is the "non-team player" behavior specifically manifesting? Are they a "brilliant jerk" who delivers high-quality code but is toxic in PRs, or are they a low-performer who is disengaged and missing deadlines?

Is this a sudden change in behavior or a long-standing pattern? Understanding if external factors (burnout, personal issues) are at play vs. a fundamental misalignment with company values is crucial.

What is the current impact on the team? Is it affecting velocity, causing attrition, or simply creating a slight friction in communication?

Assumptions for this response:

I am assuming the individual is a technically strong "silo" worker who ignores team processes (skipping standups, dismissive in code reviews, and gatekeeping knowledge), which has started to demoralize junior members and slow down cross-functional projects.

Coach Strategy

Signals: Emotional Intelligence (EQ), Conflict Resolution, Coaching/Mentorship, Performance Management, Objectivity, Courageous Conversations, Root Cause Analysis, and Culture Setting.

The Core Focus: As a Senior/Lead, you are expected to move beyond "tattling" to a manager. You must show you can diagnose the issue, provide direct feedback, and attempt to coach the individual toward alignment with team goals.

"Cheat Code" Tip: Never frame the person as "bad." Frame the behavior as a "blocker to the team's mission." Interviewers love the "Brilliant Jerk" test—they want to see if you have the backbone to address high-performers who are toxic, as these individuals often cost the company more in "culture debt" than they provide in code.

Strategy Breakdown

The STAR Narrative

Situation – Context

I was the Tech Lead for a 7-person platform engineering team during a high-stakes migration to a microservices architecture.

One of our most senior developers, "John," was technically elite but had become a significant bottleneck; he refused to document his work, was frequently condescending in code reviews, and often went "rogue," building features that weren't in the sprint backlog.

This behavior caused two junior engineers to stop speaking up in meetings and delayed our integration phase by two weeks because John’s siloed components didn't align with the team's standards.

Task – Your Responsibility

My goal was to reintegrate John into the team's workflow without losing his deep technical expertise or damaging his motivation.

I needed to protect the team's psychological safety and ensure we met our quarterly migration milestone, which was at risk due to the lack of collaboration.

Action – What You Did

Diagnostic 1:1: I scheduled a private 1:1 to understand the root cause. I discovered John felt the "process" (meetings/documentation) was slowing him down and that he felt more productive working alone.

Objective Feedback: I used specific examples rather than generalizations. I showed him the "Review Cycles" data where his PRs took 4x longer to merge because of the friction he created, explaining that while his individual velocity was high, the team's net velocity was suffering.

The "Ownership" Pivot: To lean into his strengths, I assigned him as the "Quality Lead" for the new architecture. I made him responsible for defining the documentation standards he previously ignored, framing it as a way to "level up" the rest of the team so they wouldn't "bother" him with basic questions.

Setting Clear Boundaries: I explicitly stated that "Teamwork" was a core technical requirement of his role, as essential as his coding ability, and we agreed on a 30-day trial of new communication norms (e.g., 24-hour PR turnaround, mandatory documentation).

Result – Outcome & Impact

Within six weeks, the team’s sprint velocity increased by 22% because knowledge was no longer siloed in John's head.

John’s tone in code reviews shifted from critical to educational; he actually authored a "Best Practices" guide that became the gold standard for the department.

Most importantly, the junior developers regained their confidence, and our "Team Health" survey scores for "Collaboration" rose from 3/5 to 4.8/5.

Learning / Reflection – Growth

I learned that "non-team players" are often just high-achievers who feel constrained by poorly explained processes.

I realized that as a Lead, my job isn't just to manage code, but to manage the "social API" between developers. Addressing these issues early prevents "cultural rot" that is much harder to fix later.