The Art of Saying No as a Senior Engineer
Why the most valuable skill I've developed isn't technical—it's knowing when to push back and how to do it effectively.
Early in my career, I said yes to everything. Every feature request, every meeting, every "quick favor." I thought this made me valuable. It made me exhausted and ineffective.
The Realization
The senior engineers I admired weren't the ones who did the most—they were the ones who did the right things. They had an uncanny ability to filter signal from noise.
How to Say No Effectively
Saying no isn't about being difficult. It's about protecting your capacity to do excellent work. Here's how I approach it:
Understand first. Before declining, make sure you truly understand the request. Often, the stated need isn't the real need.
Offer alternatives. "No, but here's what I can do" is more useful than a flat refusal. Maybe there's a simpler solution, or someone better suited.
Explain the tradeoff. "If I do this, I can't do that" makes the cost visible. Let stakeholders make informed decisions.
"The goal isn't to do less. It's to do better."
What to Protect
- Deep work time—context switching is expensive
- Technical debt repayment—it compounds like interest
- Learning time—stagnation is career death
- Energy—burnout helps no one
Topics:
