- Software Career Survival Guide/
- Articles/
- Vest and Rest: The Developer Career Trap Nobody Warns You About/
Vest and Rest: The Developer Career Trap Nobody Warns You About
Table of Contents
There’s a phenomenon in tech that nobody talks about because it doesn’t look like a problem from the outside. The salary is good. The equity is vesting. The job is stable. Performance reviews are fine — not great, but fine.
From the inside, it feels like winning. From a few years out, it often looks like the place where a career went to stop moving.
This is vest and rest. And it’s more common than anyone admits.
What It Actually Looks Like #
Vest and rest isn’t about being lazy, exactly. It’s about optimizing for the wrong metric. The engineer has correctly identified that their current package — salary plus unvested equity — is better than what they could get by moving. So they stay. They do enough to not get fired. They collect the checks. They wait for the next cliff.
The work gets done. Deadlines are hit. The manager is mostly happy. But the arc is flat. No hard problems are being taken on. No new skills are being built. No reputation is being made. The engineer is performing adequately at something they’ve mostly already learned.
The equity vests. Time passes. The engineer is now two or three years further into their career with a bank account that looks good and a skill set that hasn’t materially grown.
Why It’s a Trap #
The market moves while you don’t. Technology doesn’t wait. The engineer who spent two years coasting on a comfortable stack is now two years behind on whatever has shifted in their domain. This becomes visible at the worst possible time — during the job search that follows the vest.
Your negotiating position weakens. When you leave after coasting, your recent work is thin. The projects that would make a compelling story during interviews — the hard ones, the visible ones, the ones that demonstrate growth — aren’t there. You’re selling an older version of yourself.
The atrophy is subtle until it isn’t. Most engineers in vest-and-rest mode don’t notice the decline because the day-to-day doesn’t change much. The job still gets done. It’s only when they interview elsewhere — or get laid off and have to interview quickly — that the gap between their current skills and the market expectation becomes apparent.
Comfort is addictive. The longer the vest-and-rest continues, the harder it becomes to leave. The risk of taking a harder role feels bigger. The known quantity of the current situation feels safer. The window where leaving would have been easy gets further away.
The Harder Question #
There’s a legitimate version of staying put that isn’t vest and rest. Sometimes the role is genuinely good, the work is meaningful, the team is excellent, and the compensation is fair. Staying somewhere for the right reasons — including equity — is not a problem.
The test is whether you’re growing. Not dramatically, not every quarter, but over time. Are you taking on harder problems than you were a year ago? Are you learning things you didn’t know? Are you building skills and reputation that would travel if you needed them to?
If the answer is yes, you’re not coasting — you’re earning the equity. If the answer is no, you’re in the trap.
How to Get Out of It #
The fix isn’t necessarily to leave. It’s to start moving again.
Raise your hand for harder work. Most teams have projects nobody wants — the messy integration, the legacy refactor, the cross-team initiative that requires navigating org politics. Take one. Hard visible work is how you restart the career engine.
Build something outside the job. If the day job isn’t providing growth, create it elsewhere. A side project, an open-source contribution, a freelance engagement that requires skills you don’t currently have. The growth compounds regardless of where it happens.
Set a departure deadline. If you find yourself regularly thinking “I’ll leave after this cliff” and then extending the timeline every time, set a hard date. Not a vague intention — an actual date on the calendar. Then treat it seriously.
Have the conversation with your manager. “I want to take on more challenging work. What would that look like here?” Some managers respond well to this. Some don’t have anything to offer. Either way, you learn something useful.
If You’re Watching It Happen to Someone Else #
Vest and rest is visible from the outside before it’s visible from the inside. If a colleague who used to be sharp and engaged has gone quiet, stopped pushing on hard problems, stopped caring about their code quality — they’re probably in it.
This is worth a direct conversation if you’re close enough to have one. Not a lecture — just an honest “I’ve noticed you seem checked out lately, what’s going on?” Sometimes people just need someone to notice.
The Bottom Line #
The equity is real money and it’s worth waiting for. But the cost of coasting while you wait is also real — it just shows up on a different timeline, in your skill set rather than your bank account.
Collect the vest. Earn the rest. Just don’t let the rest eat the career.