Transforming a Tech 'Gatekeeper' Into a Mentor
Years ago, as a new Engineering Manager, I inherited a stable project with a hidden human risk. Our core system was gatekept by a brilliant senior engineer. His code was flawless, but his aggressive communication style created a culture of fear. Juniors stopped asking questions.
Managing this was tricky because I was a "Player-Coach," splitting 50% of my time coding on another track. I couldn't afford to get dragged into daily arguments, so I focused on changing the system architecture of the team, not just the code.
First, I partnered with the PM to track PR review metrics, shifting the conversation from personal bias to team performance. Second, I set hard boundaries on my own schedule to protect my management time from critical-path dev tasks.
Finally, in a 1-on-1, I challenged the senior’s ego: "Your job isn't to protect the codebase from the team; it's to scale the team to support the codebase." We replaced rigid, top-down code reviews with collaborative, question-based guardrails.
Eventually, the wall vanished. The senior engineer earned genuine respect as a true mentor, and the juniors gained confidence. Our greatest tool as managers is not code—it is building an environment where growth isn't blocked by personality.