What Is a Skip Level Meeting (And How to Use It to Get Promoted)

You get a calendar invite from your boss's boss. No agenda. Just a 30-minute block labeled "Skip Level." Your stomach drops. What did I do? Am I getting managed out? Is there a reorg?

Relax. A skip level meeting is one of the most common practices in tech organizations. And it's also one of the most commonly wasted.

Most engineers show up, answer whatever questions their skip-level asks, say something safe like "things are going well," and leave. They treat it as a performance check-up. Something to survive. That's a missed opportunity. Because a skip level meeting is one of the few times you get direct, one-on-one access to the person who often has the final say on whether your promotion goes through.

What is a skip level meeting?

A skip level meeting is a one-on-one conversation between you and your manager's manager. You "skip" a level in the reporting chain. Your direct manager is not in the room.

If you're a software engineer reporting to an engineering manager who reports to a director, your skip level meeting is with that director. If your manager reports to a VP, your skip is the VP.

These meetings happen on different cadences depending on the company and the leader's preference. Some directors run them monthly. Others do them quarterly or twice a year. At some companies, they only happen during specific seasons like performance review prep or org planning. The format is almost always the same: a private 1:1, usually 30 minutes, without your manager present.

Why do companies run skip level meetings?

Skip levels exist because information gets filtered as it moves up the chain. Your manager tells their boss a version of what's happening on the team. That version is shaped by what your manager thinks is important, what makes them look good, and what they remember. It's not malicious. It's human.

Senior leaders know this. They run skip levels to get a less filtered view of three things:

• How the team is actually doing. Not the version that gets reported up, but the ground-level reality. Are people blocked? Is morale low? Are there process problems the manager isn't surfacing?
• Whether the manager is effective. Your skip-level is evaluating your manager, too. They want to know if you feel supported, if your 1:1s are useful, if you're getting clear direction.
• Who on the team shows leadership potential. This is the part most engineers miss entirely. Your skip-level is forming an impression of you. Every skip level meeting is, quietly, an evaluation of whether you think and communicate at a level above your current role.

That third point matters more than the other two combined when it comes to your career.

What your skip-level is actually evaluating

Your skip-level is not checking whether you shipped your tickets on time. They already know that from status reports and sprint reviews. What they're paying attention to is harder to quantify.

Can you zoom out? Engineers who only talk about their current tasks signal that they're operating at their current level. Engineers who connect their work to the team's goals, the org's priorities, or a business outcome signal something different. When you say "I'm working on the migration" versus "the migration unblocks the team from hitting the Q3 reliability target, and I've been coordinating with the infra team to make sure we don't regress latency," those are two different people in your skip-level's mind.

Do you understand what matters to them? Your skip-level has their own pressures. They're thinking about headcount decisions, org strategy, cross-team dependencies, and what their boss is asking them to deliver. If you show that you understand even a fraction of that context, you stand out from the engineers who only know their own sprint board.

Are you someone they'd go to bat for? This is the sponsorship question. Sylvia Ann Hewlett's research on 12,000 white-collar professionals found that people with sponsors were significantly more likely to advance: 23% more for men, 19% more for women. A sponsor isn't a mentor who gives advice. A sponsor is someone with power who uses it on your behalf. They say your name in rooms you'll never enter. They vouch for you when someone on the promotion committee hesitates. Your skip-level is one of the few people positioned to become that sponsor. But they won't sponsor someone they barely know.

The connection between skip levels and promotions

Here's where this gets concrete. At most tech companies, your direct manager proposes your promotion. But your direct manager doesn't approve it alone. The proposal goes to a calibration meeting where your manager argues your case in front of peer managers and their own boss (your skip-level).

Joan C. Williams' research in Harvard Business Review (2024) found that calibration meetings introduce bias through unequal airtime. Some employees get extensive discussion. Others get skimmed over in seconds. The ones who get more airtime are typically the ones whose names are already recognized by multiple people in the room.

Your skip-level is in that room. If they've had real conversations with you, if they know what you're working on and why it matters, if they've formed their own positive impression of your judgment, they don't just passively listen to your manager's pitch. They nod. They add context. They become a second advocate.

If your skip-level has never had a meaningful conversation with you, your manager is pitching a stranger. And good work alone isn't enough to make that pitch land when the room has limited promotion slots and every other manager is pitching just as hard.

The mistake most engineers make

Most engineers approach skip level meetings in defense mode. They answer questions. They keep things positive. They don't bring up their own career because it feels presumptuous. They certainly don't talk about promotion because that feels like going over their manager's head.

This is backwards.

Your skip-level expects you to talk about your career. That's part of why the meeting exists. They want to know what you're working toward, what problems you're solving, and whether you're thinking beyond your current scope. When you play it safe and say nothing of substance, you confirm exactly one thing: that you're fine where you are. The formal 1:1 is just one channel — there are several ways to build skip-level visibility that don't require a standing meeting at all.

On Team Blind, where engineers are verified by company email, a common piece of advice surfaces repeatedly: break your skip level conversation into three areas: people, product, and process. Don't just report status. Share what you're observing about the team, the product direction, and the processes that are working or broken. That's what leaders at that level care about. And it demonstrates that you're already thinking at their altitude.

How to use skip levels strategically (without being political)

You don't need to be manipulative. You just need to stop wasting the meeting.

Share your work in terms of impact, not tasks

Don't say "I'm working on the payments refactor." Say "I'm leading the payments refactor because the current system is blocking the team from shipping the new checkout flow. We should have it done by end of month, and it'll cut integration bugs by roughly half based on what we've seen in staging."

The difference: one is a status update. The other shows ownership and business awareness. Your skip-level remembers the second version. When your skip-level asks "what are you working on?" — which they will — there's a three-sentence structure that turns that question into a visibility moment rather than a forgettable status update.

Ask questions that show you're thinking beyond your team

Questions like "What's keeping you up at night?" or "Where do you see the org headed over the next year?" aren't just polite conversation starters. They signal that you're interested in the bigger picture. And the answers give you real information about what leadership prioritizes. When you know what your skip-level cares about, you can frame your own work in those terms.

Name your career goals directly

You don't need to demand a promotion. But you should be clear about what you're working toward. Something like: "I'm focused on operating at a senior level this half. I've been looking for opportunities to lead cross-team work and I'd value your perspective on what you've seen differentiate people at that level."

That's not presumptuous. It's the kind of clarity that makes your skip-level remember your name when promotion season arrives.

Follow up after the meeting

Most engineers never follow up. They treat each skip level as a standalone event. The ones who build real relationships send a short note after: "Thanks for the conversation. You mentioned the reliability initiative is a priority this quarter. I've been thinking about how the work my team is doing on the migration connects to that. Happy to share more details if helpful."

This takes two minutes. It keeps you top of mind. And it builds continuity between meetings so each conversation doesn't start from zero.

What NOT to do in a skip level meeting

Don't complain about your manager. Even if your manager is terrible, the skip level meeting is not the place to escalate that. If there's a serious issue (harassment, ethical violations), use HR. If it's friction or frustration, handle it through your 1:1 with your manager first. Complaining to your skip-level about your manager makes you look like you can't manage conflict, and it puts your skip-level in an awkward position.

Don't treat it as a performance review. Your skip-level doesn't want to hear a list of everything you shipped last quarter. They get that data from other channels. They want a conversation. Show up with perspective, not a brag sheet.

Don't wing it. The engineers who get the most from skip levels prepare. They know what they want to say about their work, what questions they want to ask, and what impression they want to leave. If you want a detailed game plan for your next skip level, we have a companion piece on how to prepare for a skip level meeting that covers the tactical prep step by step.

When skip levels don't happen (and what to do about it)

Not every company or leader runs skip level meetings. If yours doesn't, you're not stuck. The access just requires more initiative.

• Ask your manager. "Would it make sense for me to set up a skip level with [director name]? I'd like to get their perspective on the org direction." Most managers will say yes because it reflects well on them.
• Present your work where your skip-level can see it. Cross-team demos, architecture reviews, postmortems. Any context where senior leaders attend and you can show your work directly.
• Volunteer for cross-team projects. The project itself may be secondary. The exposure to leaders outside your immediate team is the real value.

The goal isn't to bypass your manager. It's to make sure the people who influence your promotion have enough context about you to support it when the time comes.

Skip levels are a tool. Use them like one.

A skip level meeting is not a trap, not a performance review, and not something to just survive. It's 30 minutes of direct access to someone who has real influence over your career trajectory.

Most engineers waste that access by playing it safe. The ones who use it well walk in with context about the org's priorities, share their work in terms of impact, name their career goals out loud, and follow up afterward. Over time, they build a relationship with leadership that pays off when calibration arrives and the room is debating who gets one of the limited promotion slots.

You can't control whether you get promoted. But you can control whether the people making that decision know who you are and what you've done. That starts with taking your skip level meetings seriously.

---

CareerClimb's AI coach Summit helps you prepare for exactly this. It tracks your wins, maps them to your promotion criteria, and helps you rehearse the conversations that build visibility with leadership. Download CareerClimb and start building your case.