How to Request a Skip-Level 1:1 (And What to Cover)

You've read the advice about building relationships with your skip-level. You know it matters for calibration and sponsorship, for getting your name mentioned in rooms you're not in. But your company doesn't have a formal skip-level program. Your boss's boss hasn't sent you a calendar invite. And the idea of reaching out yourself feels somewhere between "proactive" and "political."

So you do nothing. And six months from now, when your manager pitches your promotion in calibration, your skip-level has no data about you. They've never heard you describe your work. They have no reason to back your case over anyone else's.

The meeting doesn't happen unless you make it happen. Here's how to do it without it being weird.

Tell your manager first

This is the step most people skip, and it's the one that prevents the most damage.

Before you send the request, tell your manager. Not ask permission. Tell them. Something like: "I'd like to set up a 1:1 with [skip-level name] to build the relationship and get a better sense of org priorities. Wanted to give you a heads up."

Why this matters: on Team Blind, verified engineers consistently warn that skip-level meetings can be misread if your direct manager doesn't know they're happening. Your skip-level might mention it to your manager. If your manager is hearing about it for the first time from their boss, it looks like you went around them. That's a hole you don't want to dig out of. It also helps to understand what your skip-level is actually evaluating in these meetings — knowing that changes how you frame the request and the conversation itself.

Telling your manager reframes it from "going around you" to "being proactive about org relationships." Most managers will appreciate it. Some will offer to introduce you, which makes the whole thing even easier.

The request itself

Keep it short. Don't over-explain why you want the meeting. A long justification makes it sound like something's wrong.

Here's a message that works:

Hi [name], I'd love to set up a 30-minute 1:1 sometime in the next couple weeks. I'm interested in learning more about where you see the org heading and how my work connects to the bigger picture. Would any time work for you?

Three sentences. Forward-looking framing. No hint of a complaint or escalation. Most skip-level managers will say yes. They want to know what's happening on their teams, and proactive engineers are exactly the kind of people they want to hear from.

If you don't get a response in a week, follow up once. If they don't respond to the follow-up, drop it for now and try again in a quarter. Some skip-level managers are genuinely too buried. Don't take it personally.

What to cover in the meeting

You have 30 minutes. Don't waste them on status updates. Your skip-level has other channels for project status. This meeting is about two things: giving them a reason to remember your name, and getting information that helps you do better work.

Start with their priorities

Open with a question about what they're focused on. "What's the biggest challenge facing the org right now?" or "Where do you see the team needing to grow over the next year?"

This does two things. It shows you think beyond your own sprint. And it gives you information you can use to connect your work to what matters at their level. If they say reliability is their top concern and you're working on reducing incident noise, you now know exactly how to frame your work in the next conversation.

Describe your work in terms of impact

When they ask what you're working on (and they will), don't give a task list. Describe the problem, your work, and why it matters. One sentence each.

There's a three-sentence structure that works reliably here: lead with what's broken, describe what you're building, and close with the outcome the org gets when it ships. The companion piece on this exact question walks through the framework with before-and-after examples if you want to practice before the meeting.

Ask one career-growth question

Near the end of the meeting, ask one question about what it takes to grow at your level. "What do you look for in engineers who are ready for the next level?" or "What separates the engineers who get promoted from the ones who don't on this team?"

This isn't asking for a promotion. It's asking for the criteria. And the answer often reveals priorities that your manager hasn't surfaced, because your skip-level sees a different slice of the picture.

Don't bring complaints

Not about your manager. Not about the process. Even if the complaint is legitimate, a skip-level 1:1 is the wrong venue. Your skip-level will wonder why you didn't raise it with your direct manager first, and the meeting becomes about a problem instead of about you.

If something genuinely needs to be escalated, do it separately with clear framing. Don't smuggle it into a relationship-building conversation.

After the meeting

Send a short follow-up. "Thanks for taking the time. I found the conversation about [specific topic they mentioned] really helpful. Looking forward to staying in touch."

Then do the thing most engineers forget: follow through on anything you discussed. If they mentioned a priority, connect your next piece of work to it. If they suggested you talk to someone, actually talk to them. The follow-through is what separates a one-time meeting from an ongoing relationship.

Try to get on their calendar again in 2-3 months. You don't need a recurring meeting. You need enough touchpoints that when your name comes up in calibration, they have a firsthand impression, not just your manager's summary. If you want to build visibility beyond the 1:1 itself — through demos, internal writing, and cross-team work — how to get on your skip-level's radar covers the full picture.

---

CareerClimb's AI coach Summit helps you prepare for conversations with your skip-level, your manager, and anyone else in your promotion path. It knows your specific role, your goals, and what you've been working on, so the advice is never generic. Download CareerClimb