How to Protect Your Career During a Reorganization

A reorg isn't just an org chart change. It's a power reset. The engineers who treat it as background noise lose ground. The ones who act strategically come out ahead.

"After the reorg, three people on my old team got promoted within a year. The rest of us were still trying to figure out who our manager was."

That's a real pattern. Reorgs don't just shuffle boxes on a chart. They reset who has context on your work, who advocates for you, and whose opinion matters when promotion decisions happen. If you don't act fast, the evidence you've spent months building can disappear overnight.

This article is about career protection: the specific defensive and offensive moves you should make when a reorg is announced or in progress. If you're looking for broader guidance on what reorgs mean and how to respond generally, start with What to Do When Your Company Reorgs.

Why reorgs are dangerous for your career

Most engineers underestimate how much of their promotion case depends on other people's memory and goodwill. Your manager knows what you shipped this quarter. Your skip-level saw the design doc you wrote. Your peer on the platform team can vouch for your cross-team collaboration.

A reorg can erase all of that in a week.

• Your manager moves to a different org. The person who was going to advocate for your promotion no longer has a seat at your calibration table.
• Your skip-level changes. The person who approved your project scope has no idea who you are.
• Your team splits. The project you led is now owned by someone else, and the context of your contribution is already fading.
• Your scope shrinks quietly. Responsibilities get reassigned during the transition, and you don't push back because you're told it's temporary.

None of these are personal. All of them are damaging if you don't respond.

Each one of these shifts can delay your promotion timeline by months, and the effects compound when multiple happen at once.

The 72-hour window: what to do immediately

The first few days after a reorg announcement are when the most important moves happen. Most people spend this time reading Slack threads and speculating. You should be documenting and reaching out.

Document everything before context evaporates

Your current manager still remembers your work right now. In three weeks, they'll be buried in their own transition. Get the following captured before that happens:

• A written summary of your contributions this cycle. Not for your self-review. For yourself. Dates, projects, outcomes, metrics. If you don't have a win log, build one now from memory, calendar invites, and PR history.
• Feedback from your current manager. Ask for a brief written summary of how they'd describe your performance and readiness for promotion. A two-line Slack message works. You want their assessment in writing before the relationship becomes former-manager.
• Peer feedback snapshots. If you've worked closely with people who are also being moved, ask them to write a quick note about the collaboration. Three sentences is enough. Once people scatter, this gets harder.

Get endorsements in writing

This is the move most engineers skip, and it's the most valuable one. Before your current manager moves on, ask them directly:

"Since we might not be working together after the reorg, would you mind writing a brief note about my work this cycle? I want to make sure the context carries over to whoever manages me next."

Most managers will say yes. Some will offer to talk to your new manager directly. Both outcomes are good. What you're doing is making your case portable. Your promotion evidence should not depend on one person's memory.

If you have a relationship with your skip-level, make the same request. A two-sentence endorsement from a director carries weight even if they're no longer in your reporting chain.

Map the new power structure

After the dust settles, the org chart will look different. But the real power structure takes longer to become visible. You need to figure out three things:

• Who makes promotion decisions for you now? This is your new manager and their manager. Understand what they care about and how they evaluate people.
• Who has influence in the new structure? Sometimes a senior engineer or a staff-level IC has more pull in calibration than your direct manager. Identify who those people are.
• What are the new team's priorities? Your old team's roadmap might be irrelevant now. The projects that mattered last quarter might not matter at all in the new structure.

Don't wait for an all-hands to answer these questions. Set up 1:1s with your new manager, your new skip-level, and adjacent leads. Ask directly: what does success look like on this team? What are the highest-priority problems? Where do you need help?

The engineers who do this in the first two weeks position themselves on the work that matters. The ones who wait get assigned whatever is left.

Protect your scope

Scope erosion is the quietest career risk during a reorg. It happens like this: a project you owned gets "temporarily" assigned to someone on the new team structure. A responsibility you held gets absorbed into a different group. Your title stays the same, but your actual influence shrinks.

This matters because scope is one of the primary things promotion committees evaluate. If you were leading a cross-team initiative and now you're writing features on a single service, your promotion case just got weaker, even if you're doing the same quality of work.

How to prevent scope erosion:

• State your ownership explicitly in the first meeting with your new manager. Don't assume they know what you own. They don't. Say it: "I've been leading the observability migration across three services. I want to make sure that stays with me through the transition."
• Get it in writing. Follow up the conversation with a message summarizing what you discussed. "Per our chat, I'll continue leading X and Y." This creates a record.
• Push back on "temporary" reassignments. If something is taken from you, ask when it's coming back. If there's no clear answer, treat it as permanent and escalate.
• Volunteer for new high-priority work. The best way to protect scope is to expand it. If the new structure has urgent problems, be the person who steps up. That's how you go from "inherited engineer" to "critical contributor" in the new org.

Build relationships with new stakeholders

Your old network still matters. But the people who will influence your next promotion are likely different now.

In the first month after a reorg, schedule 1:1s with:

• Your new manager (obvious, but go beyond status updates; share your career goals and your documented wins)
• Your new skip-level (introduce yourself, share what you're working on, ask what they care about)
• Senior ICs or tech leads on your new team (they'll have opinions about you in calibration discussions)
• People from your old team who landed in influential positions (they're your bridge between old context and new structure)

You're not networking for the sake of it. You're making sure the people who will evaluate you actually know what you've done and what you're capable of. This is the same principle behind making sure your work is visible, but the stakes are higher because you're starting from zero with a new audience.

When a new manager arrives and starts changing everything, the stakes for your career evidence become even higher.

What to do if your role is "TBD"

Sometimes a reorg leaves you in limbo. You don't have a clear team. Your manager hasn't been named. Your projects are frozen. This can last days or weeks.

This is uncomfortable, but it's also a window of opportunity. While everyone else is waiting for instructions, you can:

• Keep shipping. If your current work is still relevant, keep doing it. Don't stop producing results because the org chart is in flux.
• Write weekly updates and send them to whoever is acting as your interim manager. If no one is, send them to your old manager or your skip-level. The point is to create a paper trail that proves you kept working during the gap.
• Talk to multiple teams. If your placement isn't decided yet, you may have more influence over where you land than you think. Reach out to team leads whose work interests you. Express interest. Ask what they need. This is the one time you can shop for your next role without it looking like you're trying to leave.
• Don't panic publicly. Venting on Slack or in large meetings about the uncertainty signals that you're reactive. Process your frustration privately. In public, be the person who's focused and productive despite the chaos.

The engineers who get placed well during reorgs are usually the ones who made it easy for leadership to see where they fit.

Financial considerations most people ignore

Reorgs don't just affect your title trajectory. They can hit your compensation.

• Vesting schedules. If you're on a four-year vest with a cliff, a reorg that leads to role elimination could cost you unvested equity. Know your vesting dates. If you're close to a cliff, that changes your risk calculus.
• Equity refresh grants. Refresh grants are often tied to performance reviews. A reorg that disrupts your review cycle could delay a refresh. Ask HR directly if the timeline is affected.
• Level mapping. Some reorgs remap levels. If the new org uses a different leveling system, confirm where you land. "We'll figure it out later" is not an acceptable answer when it affects your comp band.
• Severance triggers. If the reorg involves layoffs or role elimination, understand your company's severance policy. Some companies offer voluntary separation packages during reorgs. Knowing your options doesn't mean you're leaving. It means you're informed.

The networking play: reorgs are the best time to meet people

This sounds counterintuitive, but reorgs are one of the best networking opportunities you'll get without changing jobs. Teams are mixing. Reporting lines are shifting. Everyone is meeting new people.

Use this. The social norms around reaching out are relaxed during a reorg. "Hey, I'm new to this part of the org and wanted to introduce myself" is a completely natural message. In a stable org, cold-pinging a director feels awkward. During a reorg, it's expected.

Set a goal: meet five new people in the first two weeks after the reorg lands. Prioritize people who are:

• In positions of influence in the new structure
• Working on the highest-priority projects
• Known for developing their reports (if they could become your manager)

These relationships compound. Even if they don't affect your next review cycle, they create visibility that pays off later.

The career protection checklist

Here's the full list of moves, in rough priority order. Not all will apply to every reorg, but review the list and act on the ones that do.

Within the first 72 hours:

1. Write down every win, project, and contribution from this cycle
2. Ask your current manager for a written performance summary
3. Collect brief written feedback from key collaborators
4. Confirm your vesting schedule and any upcoming equity events

Within the first two weeks:

1. Meet your new manager; share your goals and documented wins
2. Meet your new skip-level
3. Map the new power structure and identify high-priority projects
4. Explicitly state your scope ownership in writing
5. Volunteer for visible work in the new structure

Within the first month:

1. Build 1:1 relationships with five new stakeholders
2. Confirm your level mapping and comp band haven't changed
3. Start writing weekly updates for your new manager
4. Reassess your promotion timeline against the new structure

The bottom line

Reorgs reward people who move fast and think clearly about what just changed. The org chart shifted, which means the people, the priorities, and the politics shifted too. Your job is to make sure your career evidence is portable, your scope is protected, and the new decision-makers know who you are and what you've done.

Don't wait for the reorg to settle before you act. By the time it settles, the opportunities have already been claimed.

---

CareerClimb helps you stay focused during chaos. Your wins are documented, your promotion case is portable, and your plan adapts with you. Download the app and keep building, no matter what the org chart looks like.