Why the skip-level exists
A skip-level meeting is a 25-to-45 minute conversation with your manager's manager, usually your director, VP, or SVP. The stated purpose is "connection." The real purpose is calibration: they are calibrating how you think, whether your judgment can be trusted with more scope, and whether the story your manager tells about you matches the person in the room.
Most senior engineers, engineering managers, and directors treat it as a friendly check-in and leave nothing behind. That is the mistake. A skip-level is one of the two or three highest-leverage meetings you get in a calendar year. Every question you bring is a signal.
The four questions that always work
1. "What is the org's biggest risk over the next two quarters that isn't showing up in the roadmap?"
This does three things at once. It signals you think past your team, it invites the skip to say something honest, and it hands you information you can act on. A weak skip will answer with the roadmap. A strong one will name the thing they lose sleep over. Either way, you learn something.
2. "What would you need to see from me to trust me with [next scope up]?"
This is the promotion question, asked without asking for the promotion. Name the scope specifically: "the platform team," "the AI initiative," "the EU rollout." Not "more senior." The specificity forces a specific answer. Write down what they say. That is your packet.
3. "Where do you think my team is over-invested or under-invested right now?"
This is the trust question. You are inviting a critical read on work that is technically yours. It signals that you separate ego from craft - the single most-cited attribute in every staff-plus and director-level promo committee I have sat next to.
4. "Is there anything you have heard about me or my team that I should be aware of?"
This is the sponsor question. Skip-levels hear things. Peers vent, HR forwards feedback, the last promo cycle left residue. Asking directly turns a rumor into an addressable data point. Ask it near the end. Do not flinch at the answer.
Questions to avoid
- "How is the company doing?" You should already know. Reading a public 10-K, an all-hands recording, or your CEO's last board update takes an hour. Not doing it reads as unserious.
- "What are your priorities?" They said them at the last all-hands. Asking again tells them you were not listening.
- Roadmap status. That is what your one-on-one with your manager is for. Bringing it to the skip signals you cannot separate levels.
- Anything you would not want repeated to your manager. Assume every skip gets played back. Sometimes with kindness, sometimes not.
- "How is my manager doing?" Never. Not once. Even if invited.
How to prep in 20 minutes
- Write down one thing your team shipped in the last 60 days that they probably haven't heard about. One sentence. Have it ready if they ask "how's the team."
- Write down one specific scope you want next. Name it out loud in your prep. Rehearsal matters.
- Pick two of the four questions above. Not all four - you don't have the time and it reads as a script. Rotate on the next skip.
- Put a hard 25-minute finish in your calendar block. Nothing kills a skip-level like running long because you were "just getting to the good part."
Template agenda
For a 30-minute skip-level, this is what the flow actually looks like when it lands:
- 0–2 min: Warm open, one line on how you are. No filler.
- 2–7 min: One-sentence read on the team. Not a status update - a judgment call. "The team is on plan; the risk I'm watching is X."
- 7–20 min: The two questions you prepped. Let them talk. Take notes.
- 20–27 min: The scope question. Ask, listen, write it down, name a specific follow-up.
- 27–30 min: "Anything you've heard I should know?" Wrap with thanks. Do not ask for another meeting.
What a good skip-level actually changes
Two or three well-run skip-levels in a row are usually the difference between a promo packet that gets "not yet" and one that clears committee. Not because the meeting itself promoted you, skips almost never promote directly, but because your director walks into the calibration meeting with a specific memory of you making a call, and specific language for the scope you're carrying. That is what your manager cannot manufacture on your behalf.
If your skip-levels keep going "fine" but nothing moves, scope, comp, decision rights, the pattern is almost never the meeting. It's how you're holding the room, and how your scope reads upward before you ever get on the calendar. That's the specific work of the Leadership Identity Recode™. Rehearsed in real skip-levels, not role-play.