How to Rebuild Your Promotion Case With a New Manager

You were close to promotion. Your manager knew your work, had your back, was ready to advocate. Then they left. And your new manager has no idea who you are.

All those 1:1 conversations where you talked about your goals. The context they had on your projects. The two cycles of evidence they watched you build. Gone. Not because you failed. Because someone changed jobs.

On Team Blind, engineers describe this moment with a specific kind of frustration:

"I spent two years building a case with my old manager. New manager shows up and it's like I'm starting from zero."

It's one of the most common ways a promotion timeline gets disrupted. And the worst part is how invisible the damage feels. Nobody tells you your case got reset. There's no formal announcement. You just slowly realize that the person who was going to fight for you in calibration no longer exists in the equation.

Here's the thing: your work didn't disappear. Your wins are still real. But the narrative around them did disappear, and that narrative is what gets you promoted. You have to rebuild it. The good news is that you don't have to start from scratch if you move fast and move deliberately.

Why a manager change disrupts your promotion more than you think

Your promotion case is not a set of facts that transfers automatically. It's a story that lives in your manager's head. They built it over months of watching you operate, hearing about your impact in standups, seeing how you handled incidents. They had opinions about your readiness that weren't written down anywhere.

When that manager leaves, the story leaves with them.

Your new manager walks in with none of that context. They don't know what you shipped last quarter. They don't know you led the migration that saved the team three weeks of manual work. They don't know your skip-level already thinks you're ready. They know your name, your title, and your current level. That's it.

This creates three problems at once:

• The trust gap. Your old manager trusted your judgment because they'd seen it in action. Your new manager hasn't. They need to form their own opinion before they'll stake their credibility on you in a calibration room.

• The evidence gap. Whatever your old manager carried in their head about your wins is now inaccessible. If you didn't document it, it functionally doesn't exist.

• The priority gap. Your new manager has their own first 90 days to worry about. Learning the team, establishing credibility with their own leadership, figuring out the org chart. Your promotion timeline is not their top concern right now.

None of this is personal. It's structural. And once you see it as structural, you can fix it structurally.

Get your old manager's endorsement before they're gone

This is the single most time-sensitive thing on this list. If your old manager is still around, even if they've already announced they're leaving, get something in writing from them.

Ask them to send you an email or a message that covers:

• Your top three to five wins from the time you worked together, framed in terms of impact
• Their assessment of your readiness for the next level
• Specific examples of you operating at or above the level you're targeting

This doesn't have to be formal. A Slack message works. An email works. What matters is that it's written, specific, and attributable.

Why this matters: when your new manager eventually evaluates you for promotion, having a documented endorsement from your previous manager carries weight. It's not the same as your new manager seeing the work firsthand. But it answers the question they'll have in the back of their mind: "Did their previous manager think they were ready?"

If your old manager is already gone, reach out anyway. Most managers are happy to write a few sentences about someone they managed. The window where they remember your work in detail is about 60 to 90 days after leaving the team. After that, the details start fading.

The first 30 days with your new manager

The instinct is to wait. Let the new manager settle in. Don't be the person who walks in on day two asking about their promotion.

That instinct is partially right. Don't lead with promotion in your first conversation. But don't wait three months either. Here's what the first 30 days should look like.

Week 1-2: Establish the working relationship

Your first conversations should be about how your new manager prefers to work. What do they want to see in 1:1s? How do they like to receive updates? What are their priorities for the team?

This isn't filler. You're learning two things: how this person processes information, and what they care about. Both will shape how you present your case later.

Use this window to give them a brief summary of what you're currently working on and what you delivered recently. Keep it factual and concise. You're not pitching yourself. You're filling in context they don't have.

Week 3-4: Bring up your career goals

By the third or fourth week, your new manager should have a basic picture of you as a contributor. This is when you introduce the career conversation.

The framing matters. Don't say: "My old manager was about to promote me." Even if it's true, it puts your new manager in a defensive position. They didn't make that decision. They can't validate it. And it sounds like you're asking them to rubber-stamp someone else's assessment.

Instead, say something like:

"I've been working toward [next level] for the past [timeframe]. I've been documenting my work and building evidence. I'd like to share where I am and get your perspective on what you'd need to see."

This frames you as someone who takes ownership of their career. It invites collaboration instead of demanding validation. And it gives your new manager a role in the process rather than making them feel like they're just inheriting someone else's conclusion.

For a deeper playbook on how to have this career conversation with your manager, that guide covers the exact language, timing, and follow-ups.

How to transfer your case without starting over

The biggest mistake engineers make after a manager change is treating it as a total reset. You don't need to re-prove everything. You need to translate your existing evidence into a format your new manager can evaluate.

Build a case document they can read in 10 minutes

If you haven't already written a promotion case, now is the time. If you have one, update it. Either way, what your new manager needs is a single document that answers:

• What have you delivered in the past 12 to 18 months?
• What was the scope and impact of each project?
• How does your work map to the expectations of the next level?
• Who else can speak to your contributions?

This is the document that replaces the months of context your old manager had. It won't be as rich as firsthand observation. But it gives your new manager something concrete to evaluate, and it separates you from every other engineer on the team who's hoping their work speaks for itself.

How to write a promotion case walks through the structure, framing, and common mistakes in detail.

Name your witnesses

Your new manager can't verify your past work by watching you do it again. But they can talk to people who were there.

Give them names. Specifically: the tech lead you partnered with on the migration. The product manager whose launch you unblocked. The senior engineer who reviewed your design docs. Your skip-level, if they're still the same person.

You're not asking your new manager to conduct a reference check. You're making it easy for them to triangulate. When three different people confirm the same picture of your work, it becomes much harder for your new manager to dismiss your case as unverified.

Connect your past work to their priorities

New managers come in with a mandate. Maybe it's improving reliability. Maybe it's shipping a product faster. Maybe it's reducing technical debt.

Whatever their priorities are, find the connection to your existing body of work. If you led a reliability initiative last year, and your new manager's focus is reliability, that's not a coincidence you should leave unspoken. Make the link explicit. "I led the alerting overhaul last quarter that cut oncall noise by 40%. Happy to walk you through what we changed and where the remaining gaps are."

You're doing two things at once: demonstrating competence in an area they care about, and showing that your past work is directly relevant to their current goals.

Avoid the re-proving trap

The most demoralizing pattern after a manager change is the feeling that you have to do twice the work. You already demonstrated senior-level scope. Now you have to demonstrate it again because the person evaluating you wasn't there.

This is the re-proving trap, and it burns out good engineers.

The trap looks like this. Your new manager says something like: "I need to see you operate at the next level myself before I can support your case." Fair enough. But if that means another full cycle of building evidence from scratch while the evidence from the last two cycles sits unused, you're effectively being penalized for a personnel change you didn't cause.

How to avoid it. You need to reframe the conversation. The question isn't "can you prove it again?" The question is "how can we validate the evidence that already exists while you observe me going forward?"

This means:

• Point to the documented evidence. Your case document, your old manager's endorsement, your peer feedback from previous cycles. These are real artifacts.
• Propose a validation plan. Tell your new manager: "I understand you need to see this firsthand. Here's what I have documented from the past 18 months. What would help you feel confident in the next 60 to 90 days?"
• Set a timeline together. Don't leave the timeline open-ended. An open-ended "let me get to know your work" can turn into six months of limbo. A shared 60- to 90-day evaluation window creates mutual accountability.

When your new manager has different standards

Sometimes the issue isn't just missing context. Your new manager might genuinely evaluate things differently than your old one.

Your old manager valued technical depth. Your new manager cares more about cross-team influence. Your old manager thought your migration was senior-level work. Your new manager thinks it was expected at your current level.

This is frustrating, but it's real. Different managers calibrate differently, and there's no appeals process for that.

What you can do:

• Ask directly what they value. In your career conversation, ask: "When you think about engineers at the next level, what separates them from the rest?" Their answer tells you exactly what evidence they'll find compelling.
• Map your existing wins to their framework. You may have the same accomplishments but need to frame them differently. If your new manager values influence, reframe your migration as a cross-team coordination effort, not just a technical execution.
• Fill genuine gaps. If your new manager identifies something that was never required by your old manager, be honest about whether it's a real gap. Sometimes a fresh perspective reveals something you actually do need to work on.

The goal is not to argue with their standards. It's to understand what evidence this specific person will find compelling and make sure you have it.

What happens if the timeline slips

Let's be honest. A manager change usually costs you at least one review cycle. Sometimes two. That's not failure. That's the structural reality of how promotion decisions work.

The engineers who recover fastest share a few patterns:

• They document everything independently. Their case doesn't live in any single manager's memory. It lives in a document they own and update.
• They move fast on the career conversation. They don't wait three months hoping the new manager figures it out on their own.
• They get endorsements from their old manager in writing. Before the context fades.
• They treat the new manager as a partner. Not as an obstacle to convince, but as someone who needs to be equipped to fight for them in calibration.

The engineers who struggle the longest are the ones who wait silently for the new manager to recognize their work the way the old manager did. That recognition took months to build the first time. It won't happen faster the second time unless you actively transfer the context.

The real lesson here

A manager change reveals something important about how most engineers manage their careers: they store their promotion case in someone else's head.

Your wins, your evidence, your narrative. If all of that lives exclusively in your manager's memory, you're one reorg away from starting over.

The engineers who don't get derailed by manager changes are the ones who own their own case. They keep a running document. They collect peer feedback. They write down their wins in real time, with specific outcomes and context. When the manager changes, they hand over a document, not a verbal history that died with the last reporting relationship.

That's not being political. That's being prepared.

---

CareerClimb keeps your promotion case independent of any single manager. Your wins, your evidence, your plan -- all documented and portable. When your manager changes, your case doesn't. Download CareerClimb