A director I mentor built a strong case. Promotion, bigger scope, a clear path from senior to staff engineer. She handed it over like a gift.
He said no.
Not because the money was wrong. Not because the timing was off. He told her, and I’m paraphrasing closely: “I don’t actually want more people depending on me. I want to keep building things and go home at five.”
She didn’t know what to say. In her head, this was the reward. The next rung. Why would anyone say no to that?
If you lead engineers right now, you’ve probably had a version of this conversation, or you’re about to have one soon. And most leaders don’t have a framework for it, because the ladder they climbed isn’t the ladder the person in front of them wants to climb.
The Numbers Behind the “No”
This isn’t one difficult engineer. It’s a pattern, and it’s big enough to show up clearly in the data.
Deloitte’s 2025 Gen Z and Millennial Survey found that only 6% of Gen Zs name reaching a senior leadership position as their primary career goal. Stack Overflow’s 2024 Developer Survey found that 87% of professional developers are individual contributors, and most of them are there by choice, not by default.
Put those two numbers together and the message is hard to miss. A meaningful, growing share of the people on your team don’t see the manager track as the prize. They see it as one option among several, and often not the one they want.
This isn’t laziness. It isn’t a generational insult, whatever framing you’ve heard elsewhere. It’s a different value set.
The Contracting Failure Hiding Inside “No Thanks”
Here’s what’s actually going on underneath that declined promotion. You have a definition of growth in your head: more responsibility, more people, more title. That model worked for you. It’s probably how you got to where you are.
Nobody ever sat down and made that definition explicit with the person you’re trying to promote. You operated as if it was universal and obvious. So when they say no, it reads as confusing, even ungrateful, instead of what it actually is: two people who never agreed on terms.
I write about this often, because it’s the root of most leadership friction: contracting is what happens when you make agreements explicit instead of assumed. What you’re facing with a declined promotion is a contracting failure at the career level. You never asked what growth means to them, so you built a plan around what it means to you.
The fix isn’t a better pitch. It’s a different question, asked without your own answer already sitting in the room.
Ask Better, Not Louder: Tailoring the Conversation With PCM
Walk into the recontracting conversation with a genuine open question: “What does a good next two years look like to you? In your own words, not mine, not the organization’s.” Then let the silence sit. Don’t fill it with your own framework.
How you ask matters as much as what you ask. If you know the person’s PCM base, use it:
- Thinker (driven by logic and competence): frame the conversation around mastery and technical depth, not people leadership. They may want to go deeper, not wider. Ask what they think, not what they feel.
- Persister (driven by conviction and values): ask directly what kind of work actually matters to them. Their answer is anchored in values, and be ready for it to have nothing to do with the traditional ladder.
- Promoter or Rebel (driven by variety and stimulation): a rigid five year plan will feel suffocating, no matter how attractive the title sounds. They may need growth defined as variety and new problems, not vertical progression.
The point isn’t a different speech memorized for every person. It’s dropping the assumption that there’s one universal definition of growth, and actually listening for theirs.
Building the Track Nobody Asked You to Build
Most companies still equate progression with people management, no matter what the “dual ladder” on the careers page claims. If the only visible reward on your team is a manager title, you’re forcing a choice nobody should have to make.
A real non-management growth track needs three ingredients:
- Scope without headcount. More ownership of a hard technical domain, not more direct reports.
- Visible recognition. A senior IC’s decisions and mentorship should show up in performance conversations as clearly as a manager’s team results do.
- A ceiling that isn’t low. If your technical track tops out two levels below your management track, you’ve told people exactly what you actually value, whether you meant to or not.
This connects to something I wrote about job-hugging: a growing number of your engineers plan to stay put for the next two years, whether or not you build them anywhere to grow. The question isn’t whether they’ll stay. It’s whether you’ll give them something worth staying for.
The Real Question
When someone declines the traditional path, resist reading it as a lack of ambition or engagement. Ask what they’re optimizing for instead. Usually there’s a very clear answer, and it usually makes complete sense once you hear it. You just don’t know it yet.
This week, pick one person on your team whose ambitions you’ve been assuming rather than asking about. Have the actual conversation. You might learn the ladder you’ve been offering was never the ladder they were trying to climb, and that’s completely fine.
It’s not about you. It’s about them.
