What You Gain From Knowing Your Skip-Level Manager
Promotion decisions don't usually happen in your one-on-one. They happen in calibration meetings, headcount planning, and quick conversations between your manager and their manager. If you're not in the room, you can't control the narrative.
Skip-level manager: your manager's manager. Some companies run formal skip-level one-on-ones. Many leave it up to you.
Your manager carries it for you. That works fine when they're a strong advocate with plenty of time. It works less well when they're making the case for eight people in a 45-minute meeting.
A direct relationship with your skip-level gives leadership a firsthand read on your work. It keeps your reputation intact when the org chart changes. It also shows you what next-level work looks like before you're expected to do it.
Your manager can only carry so much of your story
When your name comes up in a calibration meeting, your manager makes a real case for you. They just don't get long to make it. A room reviewing a whole department moves through people quickly, and your manager is making the same case for everyone else on the team.
So the case gets compressed. The migration you untangled becomes a line about a solid quarter. The junior engineer you've been coaching may not come up at all. That isn't a failure on their part. It's what fits in the time they have.
When your skip-level has already seen how you think through a problem, your manager's case lands differently. The reaction shifts from "okay" to "that tracks, I've talked with them." Your manager's case and your skip-level's own impression back each other up.
Relationships above your manager survive reorgs
Managers change more often than you'd expect. They get promoted, change teams, leave the company, or get reshuffled in a reorg. When that happens, everything they knew about your work leaves with them.
A new manager starts with your title, your last review, and whatever made it into the handoff notes. You'll need to start strong with that new manager anyway. It goes much better when someone one level up already knows your work and can vouch for it. That person often has a say in who you report to next and which project you land on.
You can't work at the next level if you can't see it
Promotions are a lagging indicator. You usually have to show impact at the next level before you get the title for it, and what counts as impact shifts as you grow, often without anyone telling you. That's hard to do when the priorities defining that level get set two rungs above you.
By the time those priorities reach you, they've been filtered into a roadmap item or a ticket. The problem behind them, and the tradeoffs leadership weighed, got lost along the way. That's how projects get scoped in conversations you weren't in.
Skip-level conversations let you hear the problem while it's still a problem. Say your skip-level mentions that support costs keep climbing. You know the error path behind a big share of those tickets. That's a connection your manager might never have had the context to make, and it's exactly the kind of work that gets noticed at the next level.
|
|
Where can AI save you time?
My friends at Big Creek Growth put together a quick survey to spot the repetitive work you can hand off to automation.
|
|
Tell your manager before you book the time
This is where skip-level relationships go wrong. If your manager finds out about the meeting from their boss, it looks like you went around them. Even with good intentions, that costs trust you'll spend months rebuilding.
Tell your manager first. Keep it simple: you'd like to understand the broader priorities better, and you're planning to ask their manager for a quarterly conversation. Ask if they have any preferences on how you approach it. Most managers will be glad you asked. If yours reacts badly to a transparent request, that tells you something too.
A few rules keep the relationship healthy:
- Don't bring complaints about your manager or team that you haven't raised with your manager first. The skip-level meeting isn't an escalation channel.
- Don't use it to reopen decisions your manager already made. If you disagree, have that conversation with your manager.
- Share relevant context afterward. If your skip-level mentions a priority that affects the team, tell your manager. It keeps them informed and shows the relationship helps them too.
Some situations require taking a problem to your manager's manager. That's a different conversation with different stakes. Keep it separate from this one.
Come with questions about their problems
Thirty minutes a quarter is enough. If your company already runs formal skip-levels, the same approach applies. You're just using the time you already have better.
Bring questions about what they're dealing with, like:
- What are you most focused on this quarter, and what's getting in the way?
- What would you want more of from our team?
- Where do you see gaps between what engineering is building and what the business needs?
Then share one thing you're working on, framed in terms of what they just told you. Skip the status report. Show them how your work connects to what they care about.
The follow-up matters more than the first meeting. Next quarter, reference something they said last time and what you did with it. That's how an occasional meeting turns into a working relationship.
The people deciding your next role are working from a compressed version of you. You can't sit in that meeting, but you can make sure the person running it has already met you and seen how you work.
That costs one conversation with your manager and thirty minutes a quarter with theirs. Ask what they're focused on, connect your work to it, then follow up next time on what they told you.
Do that for a year and your manager's case lands on someone who already recognizes your name, instead of hearing it for the first time.