Engineering under pressure is hard. Engineering under pressure with a Team Lead who uses condescension as a management style is a different level of exhausting.
A while back, I found myself in a situation where the stakes were genuinely high. The technical challenge was solvable—the human challenge was much harder.
1. The Red Flags
It didn’t start all at once, but the pattern became clear fast:
- Public callouts over quiet coaching: Mistakes were highlighted in open channels rather than handled privately.
- Condescending tone disguised as “high standards”: Technical questions were met with eye-rolls and dismissal.
- Moving goalposts: Expectations shifted without warning or documentation.
When leadership relies on fear and condescension, team communication doesn’t improve—it shuts down. People stop asking questions and hide blockers until they become fires.
2. How We Survived (And Still Delivered)
We couldn’t fix the TL’s personality mid-sprint, so we built our own protective layer to get the job done:
- Peer-to-peer psychological safety: The rest of the devs huddled privately to validate edge cases and review each other’s code before it ever reached the TL.
- Ruthless documentation: Every requirement, decision, and verbal instruction went straight into written logs so nothing could be denied later.
- Decoupling ego from code: Learning not to take personal offense at condescending comments allowed us to filter out the noise and extract whatever technical signal was hidden underneath.
3. What I Took Away From It
Looking back, that project taught me more about engineering culture than any smooth launch ever could:
- Technical competence without empathy is a liability. A lead who knows the architecture inside-out but paralyzes their team will always be a net negative on velocity.
- Protecting your team is part of the job. Whether you’re a senior dev or a peer, creating a safe space for people to ask “stupid questions” is how complex systems actually get built.
- High stakes don’t justify bad behavior. Panic is contagious, but so is calm.