You’ve been doing the job. They just haven’t noticed.
“Hi Poornima, I’ve been at my company for about 5 years as a Senior Software Engineer. I’ve contributed to key projects, helped cross-functional teams, and my performance reviews have been good.
Recently, a manager on our team left. I know my senior manager is looking for a replacement. I haven’t led the entire team, but I’ve been actively mentoring the new college grad since they joined and serving as the go-to person in the absence of a formal manager for the software stack our team is responsible for.
I’m interested in exploring the manager position, but wondering why no one has approached me about it yet? I want to speak up and ask for it but wondering if it will backfire and they’ll think I’m not happy in my current role.”
– Senior Software Engineer, 10 years of experience
Let me name what’s actually happening here because it’s not what this engineer thinks it is.
They aren’t being passed over because they’re unqualified.
They’re being passed over because they’ve been doing the work quietly, assuming someone is watching.
And in most organizations, that assumption is wrong.
Mentoring the new grad. Serving as the de facto team lead. Being the go-to person on the stack. That’s real leadership experience and it’s been invisible, because it was never named, never claimed, never connected to the role they actually want.
This is one of the most common visibility traps in technical careers: doing the job and waiting to be recognized for it are two completely different activities.
Most engineers are exceptional at the first. Almost none are trained in the second.
Good work doesn’t speak for itself. You have to be its translator.
On the fear of backfiring: asking for a role you’re qualified for does not signal unhappiness. It signals ambition, which is exactly what a senior manager wants to see in someone they’re considering for a leadership position.
What actually signals unhappiness is disengagement. Vague dissatisfaction. A drop in quality or availability. A clear, specific, well-reasoned request for a role? That’s exactly the posture a first-time manager needs to demonstrate before they get the job.
Here’s how to approach the conversation:
1. Read the job description then read between the lines. What did your previous manager actually do day-to-day that isn’t in the JD? Ask yourself honestly: can you do 50–80% of it, and what’s your plan to grow into the rest?
2. Name what you’ve already been doing: Mentoring a new grad is management experience. Being the go-to person on the stack is management experience. Make a list of every leadership behavior you’ve demonstrated, not as a brag, as evidence. Your senior manager may not have connected those dots yet. Your job is to connect them.
3. Know what you’re asking for. Don’t go in asking “would you consider me?” Go in with a specific ask: “I’d like to be considered for this role, and I’d also be open to a 3–6 month trial period with clear evaluation criteria.” That framing shows you’ve thought it through and gives your manager a low-risk way to say yes.
4. Prepare for a no and know what to do with it. Ask directly: “What would I need to demonstrate, and over what timeline?” A no without a path is information too.
5. Build outside support before the conversation. Talk to cross-functional managers who’ve worked with you. Sponsors who can speak to your leadership impact before your senior manager makes a decision are often the difference between a yes and a “we’re still evaluating.”
You’ve been doing the job. Now it’s time to say so: clearly, specifically, and without apologizing for wanting it.
That’s not a risk. That’s visibility. And it’s the one skill that makes everything else you’ve built actually count.
