Coding is a perishable skill.
I’ve placed hundreds of engineering leaders.
And I see the same pattern:
The moment a tech lead or principal stops writing production code, their career clock starts ticking.
Not dramatically. Not overnight. But within 18 months, they realize they’re no longer the person peers would hire as an IC — and that stings.
They can’t debug a production outage without help. They can’t contribute to a design doc with confidence. They can’t pass a senior IC interview — at their own company.
And worst of all: Their engineers notice.
The Two Traps (Time + Skill Decay)
Trap #1: The Calendar Takeover
You get promoted. Your calendar fills:
- 1:1s
- Planning
- Stakeholder syncs
- Performance reviews
You tell yourself:
“I’m unblocking the team.” “I’m thinking strategically.”
But you’re not coding. And no one’s forcing you to.
The reality check: Forward-thinking companies are noticing this pattern too. Pedro Franceschi, co-founder of Brex, explains why Brex doesn’t hire “people managers” anymore — because they’ve seen what happens when leaders stop being hands-on. The market is shifting toward leaders who stay technical.
Trap #2: The Skill Fade
Six months in, you realize:
“I haven’t touched the backend in 90 days.” “I don’t know how the new auth system works.” “I couldn’t build this feature from scratch.”
You’re not incompetent. You’re just out of practice.
And the longer you wait, the harder it is to get back.
The 20–30% Rule (With Context)
You must stay hands-on. But how much?
Role: Hands-On Target |——|—————–| Startup CTO: 40–50% EM at <50 people: 30–40% Director at 100+: 20–25% VP at 500+: 10–15%
It’s not about volume. It’s about impact.
You’re not on the critical path. You’re not hoarding features. You’re proving you still understand the craft.
Real Hands-On (Not Fake)
Fake Hands-On: Real Hands-On |—————|—————| Code reviews (passive): Shipping production features Pair programming (directing): Fixing a P0 bug at 2am Writing scripts: Building an internal tool used daily Attending standup: Rotating on-call
Rule: If it doesn’t ship to customers or save the team hours, it doesn’t count.
Master Delegation (The 80/20 Rule)
You can’t do everything. But you can’t do nothing.
The 80/20 Framework
Delegate (80%): Own (20%) |—————-|———–| Routine features: System architecture Bug triage: Critical path decisions Onboarding: Tech debt strategy Documentation: Tooling that scales the team
Example:
Bad: “Here’s how to implement rate limiting.” Good: “We need rate limiting to handle 10x traffic. Build it. I’ll review.” Warning: The 20% you own should compound over time — not keep you firefighting. If you’re always on the critical path, you’ve picked the wrong 20%.
What Actually Motivates Engineers
Need: How to Deliver |——|—————-| Interesting problems: No legacy maintenance. No make-work. Visible impact: “Your PR unblocked 50K users” Growth: Stretch projects. New tech. Mentorship. Respect: Value their opinion. Protect deep work. Kill bad processes.
Why leaders miss this: They optimize for velocity metrics — but ignore satisfaction.
The paradox: Teams with high satisfaction also ship faster long-term. Burnout-driven velocity is a 6-month illusion. Make the business case to your leadership.
How to Stay Current When Tech Moves Fast
You can’t know everything. But you can stay dangerous in one domain.
Strategy: Action |——–|——–| Pick a lane: Infra? AI? Payments? Go deep — that’s your competitive advantage. Rotate through codebases: Spend 1 week/quarter shipping code in a different service. Not observing — contributing. Learn with your team: “I don’t know Next.js 15 — let’s build this together.” Accept obsolescence: Delegate what you’re behind on. Own what you’re ahead on.
Tactical Habits That Work
Habit: Why |——|—–| Block 4–6 hours/week for coding: Non-negotiable. Like a 1:1. Rotate on-call: Nothing keeps you real like a 2am page. Do the boring work: Update deps. Write docs. Review PRs. Build one internal tool/quarter: Saves team time. Proves value. Go to one meetup/month: Stay connected outside your company. Admit gaps selectively: “I’m behind on this, let’s learn together” works. But don’t admit gaps on your core domain. That erodes trust.
Failure Case Study: The “Strategic” VP
Name: Jordan (VP Engineering, Series C startup) Year 1: Hands-on. Ships features. Respected. Year 2: “I’m strategic now.” Stops coding. Year 3: Can’t debug auth. Team bypasses him. Year 4: Laid off in downturn. No offers.
Why? During those 4 years, the stack evolved:
- Monolith → microservices
- Node.js → Kotlin
- Manual deploys → GitOps
Jordan wasn’t there. When candidates asked about architecture decisions, he deferred to his EMs. A VP who can’t defend the stack isn’t hireable.
Recovery time: 9 months of deliberate practice to become IC-relevant again.
The industry is catching on: This isn’t just an individual problem — it’s a systemic one. Companies like Brex have made it policy to avoid hiring pure “people managers” because they’ve seen the pattern too many times. Pedro Franceschi, Brex’s co-founder, explains their approach: leaders who stay technical are the ones who can actually scale with the company. The companies that get this right are the ones that win.
Start Today (If You’re at Zero)
If you’ve already disengaged, here’s how to restart:
- Block 4 hours this week for code (don’t plan — just commit)
- Pick ONE domain to own deeply
- Rotate on-call next month
- Ask your team: “What’s frustrating you that I could fix?”
The Long Game
The best leaders I place can switch between IC and management — because they never stopped being engineers.
They just became engineers who:
- Multiply impact through people
- Build leverage through systems
- Stay dangerous in code
That’s the goal.
Stay technical enough to earn respect. Lead well enough to earn loyalty. Build systems that outlast you.
Do that — and you’ll have a career that lasts decades, not years.
Ready to Hire a Leader Who Refuses to Become Obsolete?
We place CTOs, VPs of Engineering, and Tech Leads who:
- Still code
- Delegate smart
- Earn respect
- Scale with you
Because staying dangerous in code is non-negotiable.
Book a 15-minute strategy call →
What’s one habit you use to stay technical? Drop your take in the comments — I read all of them.
