How Reorgs Affect Your Promotion Timeline

You were one review cycle away from promotion. Then the reorg happened. Now you're reporting to someone who's never seen your work, on a team with different priorities.

This is one of the most common and least discussed ways engineers lose momentum on promotion. Not because they stopped performing. Not because the bar changed. Because the organizational context around them shifted, and the system that decides promotions doesn't have a good way to account for that.

On Team Blind, this story shows up constantly. One engineer described it this way:

"My skip-level told me I was 'on the list' for next cycle. Then the reorg happened. New skip-level had their own list."

Reorgs don't just move boxes on an org chart. They disrupt the human relationships, institutional memory, and political capital that promotions actually depend on. Here's exactly how that works, and what you can do about it.

How reorgs mechanically break the promotion process

Promotion decisions don't happen in a vacuum. They depend on a chain of people who know your work, believe in your trajectory, and are willing to spend political capital arguing for you. A reorg snaps that chain in multiple places at once.

Your manager changes

This is the most obvious hit. Your old manager watched you operate for months or years. They saw the hard problems you solved, the fires you put out, the way you mentored junior engineers. They had context.

Your new manager has none of that. They're learning what you do at the same time they're learning the new org structure, absorbing new priorities, and figuring out their own standing. Even if they're excellent, they need time to form a credible opinion of your work. That takes a minimum of six months. More often, it takes a full review cycle.

The practical impact: your new manager cannot write a strong promotion case for you. They don't have the stories. They don't have the firsthand evidence. And they know it. Most good managers won't advocate for a promotion they can't personally vouch for. Not because they doubt you. Because they'd lose credibility in calibration if they can't back it up.

Your calibration group changes

You're no longer being compared to the same peers. Your old calibration group knew your name. Some of them had worked with you directly. Your manager could reference shared context when arguing for you: "You all saw what happened when the auth service went down. That was her."

In a new calibration group, you're a stranger. The other managers in the room have their own people to fight for, and they have no reason to support yours. Your new manager is essentially introducing you from scratch. That's a structurally weaker position.

As explained in how promotion panels work at big tech, the people in the room matter as much as the evidence in the packet. A reorg replaces the people in the room.

Your priorities shift

The project you were leading, the one that was going to be your strongest promotion evidence, might get deprioritized, absorbed into another team, or canceled outright. This happens constantly during reorgs. Leadership reshuffles resources to match new strategic bets.

You don't lose the work you already did. But you lose the narrative arc. Promotion cases are stories. They have a beginning (identified the problem), a middle (drove the solution), and an end (delivered measurable impact). A reorg can cut your story off before the ending.

Your skip-level changes

This one gets overlooked. Your skip-level is often the person who has the most influence in the calibration room. They're the tiebreaker. They're the one who says "I know this person's work and I support promotion." When your skip-level changes, you lose that air cover entirely.

Your new skip-level doesn't know you. They might not even know your name for weeks. Building that relationship from scratch while also adjusting to a new team, a new manager, and new priorities is a lot to ask. But it's necessary, and understanding why your manager can't promote you alone helps clarify why.

The "reset clock" problem

The most painful part of a reorg isn't the disruption itself. It's the invisible clock that starts ticking afterward.

Most companies don't have a formal rule that says "new managers must wait X months before nominating someone for promotion." But the unspoken norm is real. Managers who advocate for someone they barely know look foolish. Calibration committees are skeptical of promotion cases from managers who've only been in the role for one cycle.

This creates a de facto waiting period of six to twelve months. For engineers who were already questioning why they've been at the same level for too long, the reorg just extended the wait. If the reorg happens two months before your review cycle, you effectively lose that cycle. Not officially. Nobody will tell you it's off the table. But the structural conditions for a strong case are gone.

On Blind, engineers describe this as the most frustrating part:

"Nobody told me it was postponed. They just said 'let's revisit next half.' Which is a polite way of saying 'we reset your clock and there's nothing you can do about it.'"

What you can do before the transition is complete

The window between "reorg announced" and "reorg fully landed" is critical. Most engineers spend this time processing emotions and speculating about what the new org will look like. The ones who protect their promotion case spend it differently.

Get written support from your old manager

Before your old manager moves on, ask them for two things:

1. A written summary of your contributions and trajectory. Not a formal letter. An email or doc that says: "Here's what this person did on my team, here's the impact, and here's where I believed they were headed."
2. A willingness to be contacted by your new manager. Your old manager's endorsement carries weight, but only if your new manager knows it exists and can verify it.

Do this the week the reorg is announced, not after the transition. Once your old manager is absorbed into their new role, writing a retroactive assessment for someone who's no longer on their team drops to the bottom of the list.

Document your work before context disappears

Dashboards get deleted. Slack channels get archived. Projects get renamed. The evidence of what you did can evaporate faster than you expect.

Before the transition, create a personal record of your key contributions:

• Metrics snapshots with dates (before/after comparisons for projects you drove)
• Links to design docs, post-mortems, and launch announcements you authored
• Peer feedback you've received, especially written feedback from cross-functional partners
• Impact statements that connect your work to business outcomes

This isn't just for your promotion case. It's for the conversation you'll have with your new manager about what you've accomplished. They need to see evidence, not hear a summary.

Have the explicit conversation early

Within the first two weeks of reporting to your new manager, schedule a dedicated career conversation. Not a status update. Not a "getting to know you" chat. A conversation specifically about your promotion timeline.

Say something like: "I want to share where I was in terms of my promotion case before the reorg. I've documented my key contributions and would love to walk you through them. I'd also like to understand your approach to promotions and what you'll need to see from me."

This does three things:

• Signals seriousness without being pushy
• Gives your new manager the information they'd otherwise take months to gather
• Establishes shared expectations so there's no ambiguity about timelines

Most new managers appreciate this. They inherited a team they don't fully understand. Someone showing up with organized documentation and clear goals is a relief, not a burden.

How to build your case in a new org

Once the reorg has landed and the dust has settled, your job is to rebuild the conditions that make promotion possible. That means treating three things as priorities.

Rebuild the relationship layer

Your promotion case doesn't exist in isolation. It needs champions. In a new org, you have to build those from scratch.

• Invest heavily in 1:1s with your new manager. Share wins weekly. Give them the material they'll need for calibration.
• Get on your new skip-level's radar. Volunteer for a visible project. Present at a team-wide meeting. Make sure they know your name and associate it with impact.
• Identify the new calibration peers. Figure out who else is being evaluated alongside you. Understand the bar in this new group.

Reframe your existing work for new priorities

The project you led on your old team might not map cleanly to your new team's goals. But the skills you demonstrated, the leadership behaviors, the technical judgment, those transfer.

Rewrite your win log to emphasize the transferable elements. Instead of "Led the migration of the payments service to the new API," frame it as "Led a cross-team technical migration that reduced latency by 40% and eliminated a class of production incidents." The second version doesn't depend on the reader knowing your old team's context.

Create new evidence fast

You need recent wins that your new manager witnessed firsthand. Inherited evidence from your old team is supporting material. It strengthens the case. But it can't carry it alone.

Look for high-visibility, short-cycle opportunities in the first 90 days:

• Fix something that's clearly broken. Every new org has low-hanging fruit that nobody has gotten around to.
• Ship something end-to-end. Even a small project that you own from problem to solution demonstrates the full arc.
• Help someone publicly. Cross-team collaboration that's visible to your new skip-level is disproportionately valuable right now.

The goal isn't to do more work. It's to create evidence your new manager can personally vouch for.

The part nobody talks about: reorgs can accelerate promotions too

This isn't always bad news. Reorgs create structural openings that don't exist in stable orgs.

Leadership vacuums. When a senior engineer or tech lead leaves during a reorg, someone needs to fill that role. If you step into it, you're demonstrating next-level behavior in real time. That's stronger evidence than any written case.

New teams need senior people. A newly formed team often has an explicit need for someone at the level above yours. If you're the most experienced person on a new team, the case for your promotion becomes obvious.

Fresh eyes. Your old manager might have anchored on an outdated impression of your work. A new manager who sees your recent output with no baggage can sometimes form a more accurate, more favorable assessment.

Broader scope. Reorgs sometimes expand your surface area. You might pick up ownership of systems or projects that didn't exist in your old role. More scope means more opportunity to demonstrate next-level impact.

The engineers who benefit from reorgs aren't luckier. They're faster at reading the new landscape and positioning themselves accordingly.

Company-specific patterns worth knowing

Different companies handle promotions during reorgs differently. A few patterns are worth knowing.

Google uses promotion committees that review packets independently of the manager relationship. This theoretically makes reorgs less disruptive, since the committee evaluates the written evidence rather than relying on a manager's in-room advocacy. In practice, your manager still writes a critical portion of the packet. A new manager writing that section with limited context weakens it.

Amazon ties promotion heavily to the manager relationship and calibration discussions. A reorg that changes your manager resets both. Amazon's Leadership Principles-based evaluation means you also need to recalibrate your evidence to align with how your new org interprets principles like Ownership and Deliver Results.

Meta runs a calibration process where your manager's advocacy directly determines whether your name even comes up. A manager who's known you for two months is structurally less likely to push for your promotion than one who's seen a full year of your work. Meta's fast-paced reorg culture means many engineers experience this more than once.

Microsoft uses the Connects system for ongoing feedback, which theoretically preserves continuity across manager changes. But the promotion decision still depends heavily on your manager's narrative in the calibration room. A reorg that happens mid-cycle can leave you with a Connects history that your new manager hasn't contributed to and may not fully trust.

What to remember

Reorgs are disruptive. They can delay your promotion by six to twelve months. But they don't erase your work. Your wins are still your wins. Your evidence is still your evidence.

The engineers who lose the most time are the ones who assume the system will carry their case forward automatically. It won't. The transition requires active management: documenting your work before context disappears, getting written support from your old manager, having explicit conversations with your new manager, and creating fresh evidence quickly.

The ones who recover fastest treat the reorg as a signal to double down on documentation, not a reason to wait.