The Ladder We Forget: Why We Need to Retire the "Brilliant Jerk" Persona
Principal Software Engineers aren’t born overnight. The title is forged through years of grinding tedium, late-night debugging, and the persistent struggle to master ever-shifting stacks. Yet, there is a recurring amnesia in our industry: many who reach the top seem to have forgotten exactly how long and difficult the climb actually was.
This memory lapse manifests as the "Brilliant Jerk" syndrome, and it’s a culture killer.
The Double Standard of Excellence
I often see senior leaders who are short with their mentees, holding them to standards they themselves couldn't have met at the same stage of their careers. It’s an unfair projection of current mastery onto someone else’s "Day One."
We see this most clearly in the hiring process. Engineers design interview questions so convoluted and abstract that if they were put on the spot, even without the stress of a live interview, they likely couldn't solve them satisfactorily themselves. We’ve turned technical assessment into a gauntlet of ego rather than a measure of potential.
Empathy as a Technical Skill
When we lose sight of our own growth process, we lose the ability to lead. Being a "Brilliant Jerk" isn't a badge of honor; it’s a failure of mentorship.
We should strive to remember that growth is the point. Seeing a student or a junior engineer bridge a gap in their knowledge is objectively more rewarding than being bitter that they haven’t reached the finish line yet.
The Bottom Line: Our job as seasoned engineers isn't just to ship code, it’s to build the people who will ship the code of the future. Let’s stop building pedestals and start lowering the ladder.
If you can’t remember what it felt like to be confused, you’ve forgotten how to be a leader.