How to Rebuild Your Relationship With a New Skip-Level

You spent months getting your skip-level to understand your work. They knew your projects, your strengths, where you were headed. When your name came up in calibration, they had context. They could back up your manager's case.

Then they left. Or got moved. Or the org reshuffled and now someone new sits in that seat.

Suddenly, the person two levels above you doesn't know who you are. They don't know what you've shipped, what you're working toward, or why you matter. And the uncomfortable truth is: in most promotion processes, your skip-level's opinion carries more weight than your manager's.

You're starting from zero. Here's how to rebuild.

Why the Skip-Level Relationship Matters More Than You Think

Your manager can advocate for you. But in calibration rooms, your manager is one voice among many, and they often need backup from their own boss to make your case stick.

Leader-Member Exchange (LMX) theory, one of the most studied frameworks in organizational psychology, shows that the quality of your relationship with leadership directly influences your job performance ratings, career opportunities, and even how much ambiguity you experience in your role. High-quality exchanges, built on trust and mutual respect, lead to better outcomes across the board. If the skip-level change came alongside a broader reorg, how to rebuild your promotion case with a new manager covers the direct-manager side of the same reset.

The catch: LMX research also shows that leaders tend to categorize their reports into "in-groups" and "out-groups" early in the relationship. Those first few interactions set the pattern. If your new skip-level forms their impression of you before you've had a chance to shape it, you may get sorted into the wrong category and not realize it for months.

The First Move: Don't Wait to Be Introduced

Most engineers assume their manager will introduce them to the new skip-level, provide context, share their track record. Sometimes that happens. Often it doesn't, or it happens in a way that's too vague to be useful.

Take the initiative. Within the first two weeks of the change, request a 1:1 with your new skip-level. If they have regular office hours or open skip-level meeting slots, use those. If not, send a direct message: "I'd love to grab 15 minutes to introduce myself and share what my team is focused on."

This is not overstepping. Senior leaders consistently say they want ICs to be proactive about these conversations. A survey from IEEE Spectrum found that skip-level meetings are one of the most underused career growth tools available to engineers, precisely because most people feel too intimidated to initiate them.

You're not asking for a favor. You're making their job easier by giving them context they need.

What to Cover in the First Meeting

You have 15 to 30 minutes. Don't waste it on small talk or on reciting your resume. Cover three things:

What you're working on and why it matters. One to two sentences about your current projects, framed in terms of business impact. Not "I'm building the new notification service" but "I'm leading the notification overhaul, which should reduce our user churn signal from delayed alerts by about 30%."

Where you're headed. A brief mention of your career goals. "I'm working toward a senior promotion and focusing on building cross-team technical leadership this half." This gives your skip-level a frame for interpreting your work in the future.

One ground-level insight they probably don't have. Skip-levels are often disconnected from day-to-day engineering reality. Sharing something specific from the ground, a bottleneck, a risk, an opportunity nobody else is flagging, positions you as someone with valuable perspective. This is the kind of input that LeadDev describes as uniquely valuable from ICs, because no one else in the org has that vantage point.

End with: "I'd love to stay in touch. Would it make sense to grab time occasionally, maybe quarterly?"

Building the Relationship Over Time

One meeting doesn't build a relationship. It opens the door. Here's how to keep it open without being pushy.

Make your work visible in their channels

Pay attention to where your skip-level gets information. Do they read weekly team updates? Attend certain standups? Skim a particular Slack channel? Whatever their intake channel is, make sure your work shows up there. Not as self-promotion, but as clear, concise updates that demonstrate impact.

If your manager sends a weekly summary to their boss, ask your manager to include a line about your project's progress. You're not going around your manager. You're making sure the signal about your work reaches the right altitude.

Be useful, not just visible

The difference between "trying to get on my skip-level's radar" and "being someone my skip-level values" is the difference between visibility and usefulness.

Useful looks like: volunteering for a cross-team initiative that your skip-level cares about, surfacing a risk before it becomes a problem, or offering perspective in a meeting where senior leadership is present.

Visibility alone, without substance behind it, gets noticed for the wrong reasons. Skip-levels can tell the difference between someone contributing and someone performing.

Don't undermine your direct manager

This is where engineers sometimes stumble. Building a skip-level relationship does not mean bypassing your manager or airing grievances upward. Your manager and your skip-level talk regularly. If you complain about your manager to their boss, it nearly always gets back to your manager and damages both relationships.

Keep skip-level conversations positive and forward-looking. If you have issues with your manager, address them directly with your manager first.

When Your Skip-Level Seems Uninterested

Some skip-levels simply don't do 1:1s with ICs. They're busy, they see it as their managers' job, or they don't prioritize relationship-building down the chain.

This is frustrating, but it's not a dead end. You can still build the relationship through indirect channels:

• Deliver results that your manager can champion upward. If your skip-level won't meet with you directly, your manager becomes the translator for your work. Make sure they have plenty of material.
• Be excellent in meetings where your skip-level is present. One strong contribution in a team-wide meeting can establish more credibility than three private 1:1s.
• Write clearly and concisely in shared documents, design docs, and project summaries. Your skip-level may never schedule a meeting, but they might read your work.

Not every skip-level relationship will be close. Some will be distant but functional. The goal isn't friendship. It's making sure the person who influences your career trajectory has an accurate picture of your contributions. For a deeper guide on building that connection even when access is limited, how to get on your skip-level's radar covers both direct and indirect approaches.

The Promotion Angle

Here's why all of this matters concretely: when promotion decisions are made, your skip-level often has veto power. They may not write your review, but they sign off on whether your manager's recommendation moves forward.

If your skip-level doesn't know you, doesn't know your work, or has a vague, neutral impression of you, your promotion packet is weaker than it needs to be. Not because your work wasn't good enough, but because the person who needs to approve it can't speak to it.

The engineers who get promoted consistently aren't just good at their jobs. They're known by the people in the room where decisions happen. When your skip-level changes, rebuilding that recognition is not optional. It's part of the work.

Your First 30 Days Playbook

Here's the sequence, compressed:

1. In the first week, request a 1:1 with your new skip-level. Prepare a 2-minute summary of your work and goals.
2. Have the meeting in week two. Share context, share one insight, express interest in staying connected.
3. Over weeks three and four, find one way to make your work visible in a channel your skip-level monitors. Ask your manager to include your project updates in their upward reporting.
4. From month two onward, follow up quarterly. Keep the relationship warm with occasional touchpoints, not constant contact.

The relationship won't be what it was with your previous skip-level overnight. But the engineers who rebuild it fastest are the ones whose careers stay on track through the transition.

---

CareerClimb's AI coach, Summit, helps you prepare for skip-level conversations with specific talking points tailored to your situation, your goals, and the impression you want to make. Download CareerClimb to build your case with the people who matter.