Useful guide to managing smart brats

Some of the most difficult people I’ve had to manage were also the most technically capable. Brilliant, productive, endlessly curious, but somewhere along the way, they decided that being right mattered more than being helpful. That challenging everything was the same as thinking clearly. That building something impressive alone was better than building something useful together.

I’ve been that person. Early in my career, I loved pushing back on everything. I thought it was bold and sharp to question the status quo in deliberately provocative ways. I wanted to shake things up. What I was actually doing was exhausting the people around me. It didn’t help my career, and more importantly, it didn’t help the teams I was supposed to be contributing to.

What it actually looks like

I worked with a developer who was smart, thoughtful, and genuinely one of the better teammates I’d had. I helped him grow into a tech lead role. He was doing well. Then he invited me to collaborate on a startup he was building, and something shifted. He started calling himself “director” without understanding what that role meant. He dismissed questions, pushed his opinions without making room for others, and became progressively harder to work with. The technical ability was still there. The humility and openness were gone.

The behavior I’ve seen on the more severe end was less gradual. A tech lead who deliberately excluded me from team meetings. Who dismissed contributions in technical conversations and asserted his decisions were always correct. Who would physically turn away at social events rather than engage. That wasn’t disagreement about code. It was control.

These people aren’t malicious. But they become genuinely harmful to teams when no one holds them accountable, because their behavior teaches other people that assertiveness and collaboration are in opposition. They create silence in people who could have contributed. They build resentment that accumulates and then surfaces in departures or disengagement.

What they usually don’t see

The brilliant jerk tends to measure their value in individual output: lines of code, bugs fixed, decisions won. They don’t register the silence they create in others. They don’t see the engineer who stopped sharing ideas after getting dismissed one too many times, or the team member who started deferring in meetings even when they had the better answer.

They often want influence. But they don’t understand that influence is given, not taken. When people follow you because they feel heard and respected, that influence is real and durable. When they defer to you because it’s less painful than engaging, that’s not leadership. It’s avoidance.

What to do about it

Address it early. Hoping someone will outgrow behavior that’s gone unchallenged for months is not a strategy.

Be specific in the feedback, not general. “You can be too blunt” is easy to dismiss. “In last Thursday’s architecture review, you interrupted two people who were mid-sentence and told them their approach was wrong before they finished explaining it” is harder to argue with. Specific observations about specific behaviors in specific contexts are what give feedback traction.

Then show them what growth actually looks like for someone at their level. If they want to lead, define what that requires in behavioral terms, not just technical ones. It means helping others succeed, not just making better decisions. It means listening with real attention, not waiting for the other person to finish so you can respond. It means earning trust through consistency, not assuming it because of seniority.

Some people receive this kind of feedback and genuinely change. The conversation is the turning point. Others receive it, nod, and continue the same patterns. At that point, the question becomes what the team costs are of keeping a high-output contributor who is quietly damaging the people around them. The technical output is usually outweighed by the departure risk, the chilling effect on team voice, and the message it sends about what’s acceptable.

Protecting the team is the job. Sometimes that means having a hard conversation with the highest performer on the team and making clear that technical contribution alone isn’t sufficient.