How to Prepare for a Skip Level Meeting (Questions, Template, and What to Actually Say)

The calendar invite just appeared. A 30-minute meeting with your manager's manager. No agenda. No context. Just a title that says "Skip Level" or "Quick Chat" or, worst case, just their name.

Your first thought is probably: am I getting fired?

You're not. Skip level meetings are normal. They happen at most mid-to-large tech companies, and your skip-level manager (the person your direct manager reports to) probably has them scheduled with every engineer on the team. But normal doesn't mean unimportant. Most engineers show up, answer a few questions, say "everything's going well," and walk out having wasted one of the few direct touchpoints they'll ever get with a decision-maker who shapes their career.

The engineers who get promoted treat these meetings differently. They prepare. They bring questions. They leave with something specific: a relationship that pays off when their name comes up in calibration.

Here's how to do that.

What a skip level meeting actually is

A skip level meeting is a one-on-one between you and the person your manager reports to, usually a director or senior manager. Your direct manager is not in the room.

The format is almost always informal. Thirty minutes. Open-ended questions. Your skip-level will probably start with some version of "How's everything going?" or "What's on your mind?"

From your skip-level's perspective, this meeting serves three purposes. The first is an organizational health check: they want to know if their managers are managing well, if priorities are clear, and if the team is functioning. The second is talent identification. They're building a mental map of who's on the team, who's growing, and who might be ready for more. This directly feeds into calibration conversations. The third is an early warning system. Systemic problems like bad processes, broken team dynamics, and misaligned priorities rarely surface through standard reporting. Skip levels are how senior leaders hear about them before they escalate.

This is not a performance review. Nobody is grading you. But if your skip-level doesn't know your name, this meeting is your chance to change that. The impression you leave shapes how they think about you when your name comes up in rooms you're not in.

What your skip-level is evaluating, even if they say it's casual

They'll tell you it's just a check-in. And that's mostly true. But senior leaders are always pattern-matching, whether they intend to or not.

How you frame problems reveals your level. An engineer who says "the deploy pipeline is slow" is reporting a complaint. An engineer who says "our deploy pipeline adds two days to every release, which is blocking the team from shipping ahead of the Q3 deadline, and I've been thinking about what a fix could look like" is demonstrating the scope and ownership that calibration committees look for in senior-level work.

Whether you think beyond your own work matters, too. Questions about the org's direction, cross-team blockers, or where leadership sees the team heading in six months signal strategic awareness. Status updates about your current project signal that you're thinking about your sprint, not the business.

Your communication quality is data. How you explain your work, how you ask questions, how you handle ambiguity. Your skip-level is absorbing all of it, even in a casual conversation.

How to prepare in the 48 hours before

Good preparation takes 20 minutes, not two hours.

Start by reviewing your recent wins. Know two or three specific things you've shipped or contributed to. Frame each one in terms of the outcome it created, not the work it required. "Reduced oncall pages by 35%" lands differently than "refactored the alerting service."

Next, prepare three to five questions. See the template below. Have them written down. Bringing questions signals that you're intentional about the meeting, not just showing up because the calendar told you to.

Skim any recent all-hands notes, team objectives, or leadership announcements. You want to speak to what your skip-level cares about (the team and the org), not just your individual tasks.

If this is your first skip level, give your direct manager a heads-up that you're planning to discuss team priorities and career growth. This prevents political weirdness. No one likes being surprised when their boss mentions something their report said.

The three categories of questions to bring

Bring three to five questions organized across these categories. You won't use all of them. Pick the ones that feel natural once the conversation starts.

Career growth questions

These position your skip-level as a mentor, which is a role most senior leaders are comfortable with and genuinely enjoy.

• "What separates engineers who grow into [next level] from those who stay at [current level]?"
• "What skills or behaviors do you see in the strongest engineers on this team?"
• "Is there anything I should be thinking about for my development that I might not see from where I sit?"

Visibility questions

These surface opportunities without directly asking for them.

• "Are there any cross-team initiatives coming up that could use support?"
• "What's one thing you wish more engineers on the team understood about how decisions get made at your level?"
• "How does our team's work connect to the org's top priorities right now?"

Alignment questions

These show you're thinking at a broader scope than your immediate tasks.

• "What's the biggest challenge facing the org right now?"
• "Are there any upcoming changes in direction that would be useful for me to know about?"
• "What does success look like for our team from your perspective over the next six months?"

How to naturally mention your promotion goals

Don't ask for a promotion in a skip level meeting. That's not what the meeting is for, and it puts your skip-level in an awkward position relative to your direct manager. The explicit career conversation about goals and timelines should happen with your direct manager first. The skip level meeting is where you demonstrate readiness, not where you make the request.

Instead, frame it as a growth question:

"I've been focused on growing toward [next level]. From your perspective, what does it take to operate effectively at that level?"

You've signaled your ambition without making a request, positioned your skip-level as a coach rather than a gatekeeper, and gotten direct criteria from someone who participates in promotion decisions. Criteria your direct manager may not have given you.

Another approach that works:

"What's the most common gap you see in engineers trying to make the jump from [current level] to [next level]?"

Both of these questions are asking about promotion without saying the word. Your skip-level will understand exactly what you're asking, and they'll respect that you framed it as a learning question rather than a demand.

What to say if they ask "How can I support you?"

This is the most common question skip-level managers ask, and most engineers fumble it with "I'm good, nothing comes to mind."

That's a wasted opportunity. Have one specific, reasonable ask ready. You could say you'd love more exposure to cross-team work (signals ambition, easy for them to act on). Or that it would help to understand what your team's work looks like from their level (invites them to share context that makes your work more aligned). Or that you're working on growing toward the next level and any guidance on what to focus on would help.

Pick one. The goal is to leave them with a concrete impression that you're intentional about your career and easy to help.

What NOT to say

The biggest mistake is complaining about your manager. Even if your complaints are valid, your skip-level's first instinct is to question your judgment, not your manager's. If there is a genuine problem, raise it as a systemic observation: "I've noticed our team sometimes gets conflicting priorities from different stakeholders" is different from "my manager doesn't communicate priorities well."

Being vague is almost as bad. "Things are going well" tells your skip-level nothing and wastes both of your time. Be specific about what you're working on, what's going well, and what you're thinking about.

Don't claim ownership of outcomes you didn't drive, either. Senior leaders have good BS detectors. Understated confidence lands better than inflated claims.

Your skip-level also doesn't need a sprint readout. They have dashboards for that. Use the time for the conversation you can't have anywhere else: career growth, org context, and building a relationship with someone who influences your trajectory.

Finally, never share something with your skip-level that you haven't already raised with your direct manager. If it gets back to your manager (and it will), you've damaged the trust that the rest of your working relationship depends on.

After the meeting: what to do in the next 48 hours

The meeting is only half the work. The follow-up is what builds a lasting relationship.

Send a short thank-you within 24 hours. Two to three sentences. Reference something specific they said. This keeps you top of mind and shows you were actually listening.

If they mentioned a priority, a concern, or a piece of advice, do something with it within two weeks. Then let them know. Example: "You mentioned the onboarding experience for new engineers. I put together a starter guide for our service and shared it with the team." This is how you build a reputation as someone who listens and executes.

You don't need to schedule recurring skip levels, though you can ask. Low-touch alternatives work fine: share a brief update when you hit a milestone on something they asked about, respond thoughtfully when they send a team announcement, or volunteer for a cross-team initiative they're sponsoring. One short async message per quarter is enough to stay on their radar without being annoying.

After every skip level, give your direct manager a short summary of what you discussed. This prevents surprises and shows you're not going behind their back. It also gives your manager useful signal about what their boss cares about.

Skip level meeting question template

Copy this list. Adjust for your situation. Bring it to your next meeting.

Career growth:

1. What separates engineers who grow into [next level] from those who stay at [current level]?
2. What skills or behaviors do you see in the strongest engineers on this team?
3. What's the most common gap in engineers trying to move from [my level] to [next level]?

Visibility and opportunity:

4. Are there any cross-team initiatives coming up that could use support?
5. What's one thing you wish more engineers understood about how decisions are made at your level?
6. How does our team's work connect to the org's top priorities?

Alignment and org context:

7. What's the biggest challenge facing the org right now that I might not see from my level?
8. Are there any upcoming changes in direction that would be useful for me to know about?
9. What does success look like for our team from your perspective?

Relationship-building:

10. What's something that surprised you when you moved into your current role?

---

CareerClimb helps you prepare for the conversations that shape your career: skip levels, 1:1s, and promotion conversations. Your AI coach Summit helps you clarify what to say, what to ask, and how to position your work with the people who decide your trajectory. Download CareerClimb