How to Interview for the Level Above: What Changes from L7 to L8, L8 to L9, and Into VP

A recruiter reaches out about a role a rung above your current title, or a mentor makes an introduction, or someone in your network opens a door to a job at the next level. However it starts, you are probably already doing the work of that level, if not all of it then most of it. Your scope has outgrown your title, even though the title has not caught up.

So the interview is not really testing whether you can operate at the level you are targeting, because you already do, or you have strong conviction that you can. It is testing whether the people you meet come away feeling that the level fits you. That feeling is what earns you the offer at the level you want, and it is a different skill from doing the job. It also shifts depending on which jump you are making. Interviewing from L7 to L8 is not the same as interviewing from L8 to L9, and neither is the same as leaving a company like Google or Meta L8 to run product as a VP or head of product at a smaller company. This post covers what changes at each jump, and then the techniques that make you vibe as the level you are targeting rather than the one you hold currently.

What changes when you interview a level up, from L7 to L8, L8 to L9, or into VP/Head of Product?

By the time you are in a loop for L7 to L9 (which is Meta and Google's leveling for what most companies call Director to VP), everyone already knows you are capable. The competence rounds, the technical screen and the basic execution questions, are the floor, and every serious candidate clears the floor. Your level gets decided on the ceiling, which is the thinking only you can bring. So what the interviewers are really feeling is your seniority, and a feeling is more than a checklist. When that feeling is not quite there, a committee finds it easier to stand behind a clear yes at the lower level than a maybe at the higher one, so your task is to leave so little doubt that no one has a maybe to resolve. What creates that doubt, and the stories that resolve it, differ at each level jump.

Going from L7 to L8 feels hard for a lot of leaders, because it is where the work stops being mostly yours. An L7 interview rewards the impact and the revenue you drove, while an L8 interview probes how you have built a team and an org rather than a product. The stories that land are the ones where you changed the composition of a team to add a capability it was missing, restructured how the managers under you operate, or set the norm for how product management is done across your whole area.

Going from L8 to L9 raises the altitude again. An L8 builds and runs a strong org, while an L9 shapes direction across many orgs that do not report to them, and does it with far less information than feels comfortable. At this level you are often deciding on 10-20-30% of the data, so what the interview looks for is whether you can make the call without the full picture, trust your intuition when the data runs out, and set the conditions that let your org succeed when you are not in every review. The stories that land are about building the org and the system around it, not about a single outcome you drove yourself.

Leaving a big company at L8 to become a VP or head of product at a smaller one is a different frame again. A head of product is usually there to be the extension of the founder, taking the product off the founder's plate so they can work on the business itself, so the signals are different. They want to see that you can take a vision you did not create and bring it to life across all the unglamorous parts of the work, that your storytelling and influence are strong enough to help the company raise its next round, and that you can jumpstart execution while respecting what already exists.

The real worry with senior big-company leaders is not talent. It is that they have been shielded from the tactical day to day for so long that they cannot function without a large team and a lot of infrastructure around them. So the 2 failure modes to avoid are walking in as a pure visionary who wants to rewrite the roadmap, and walking in as a process-heavy operator who needs a big team to move. You want to come across as different enough to bring a fresh perspective, but not so different that the organization rejects you.

If you want the full picture of how companies like Google and Meta actually score each level, with the altitude mapping and the exact areas each loop digs into, I laid it out in the L7, L8, and L9 product leadership interview playbook.

How do you show you're operating at the level above?

Whatever the jump, the shift that changes everything is to walk in as an advisor rather than a candidate. Someone who already operates at the level does not audition. They treat the conversation the way they would treat advising a leader they respect, getting the real context, forming a view, and saying what they would actually do.

We have coached leaders through this shift across multiple companies and levels, into more than 26 offers at L7 and above, across Director, Senior Director, and VP/Head of Product roles with total comp as high as $2.9M:

1. Google L7 to Meta L8

2. Google L7 to Coinbase Sr Director (L9)

3. Google L7 to Calendly VP (L10)

4. MAI L67 to Google L8

5. MAI L67 to Startup Head of Product

6. Meta L6 to Google L7

7. Google L6 to MAI L67

Advising well in an interview comes down to 4 techniques that build on each other:

1. You start with a clear point of view.

2. You make that view your one superpower aimed at what the company needs most.

3. You help it land through contrast.

4. You frame all of it a level up.

The 1st technique is to have a point of view and state it, even when you are not 100% certain. A leader is expected to take a position and stand behind it, so a well-reasoned view you can defend reads as far more senior than a careful tour of every option. You do not have to be right about everything; what matters is showing the interviewer how you think and where you would place your bet.

The 2nd technique is to make that point of view your one superpower, aimed squarely at what the company needs most right now. The trap here is being merely average across everything, because a senior leadership loop rewards the leader who has the one strength this company needs more than it rewards the safe generalist. You can be well-rounded, and you still have to identify the thing you are unmistakably great at, confirm it is what they need most, and lead with it. In the interview that can sound as direct as this: “I noticed the VP of Engineering goes deep on the architecture, but what the company most needs over the next 2 years is someone who can turn this early product into a platform the whole business can grow on and build the team to run it, and that is the work I am strongest at.”

The 3rd technique is contrast, which makes your judgment visible, because our minds are poor at judging anything in isolation. Dark blue looks black until you set it beside true black. When you describe a decision you made, put it next to the simpler choice you could have made instead, so the interviewer feels the complexity you were working in. Rather than saying you built an approval flow, you might say that a single agent with full access would have been far easier to ship, but you scoped it tightly because one wrong action in that system could not be undone, which is a trade-off that only exists at real scale. Without that contrast, even your hardest calls sound ordinary.

The 4th technique is to frame everything a level up. A strong candidate at the current level talks about fixing the problems in front of them, while someone at the next level talks about building the system those problems live in, and where the org and the product need to be over the next few years. In practice, you answer an execution question by first laying out the bigger picture you are working toward, and only then walking down into the specific decision, so the interviewer watches you set direction before you get into the detail. Framing a level up also means talking about how you grow the people under you, how you raise the bar of a whole org, and how you get results through teams you do not control, since influence without authority is most of the job above L7. An answer that only ever describes a product you shipped, however good it was, tells the interviewer you are still operating at the level you are trying to leave.

What if you have never formally held the title?

Beneath the 4 techniques sits a single mindset, and it matters most when you have never formally held the title. The shift you need is from proving to advising, because the urge to prove is usually the thing that gives you away. Most capable people carry a version of this doubt, the sense that they have done the work but not held the title, so maybe they are not that level yet.

What settles it is rarely more evidence. It comes from one of 2 places: the fact that you have already been doing the work, or a strong conviction that you could do the job, held steadily enough that you stop trying to prove it. When you walk in determined to prove you belong, part of you spends the interview reassuring yourself, and it shows up as over-explaining, hedging, and apologizing for a gap that no one asked about. Someone who already operates at the level does none of that, because they are there to advise, the way an L8 or a VP would sit with a CEO and talk through what to do next.

So the most useful preparation has less to do with building a case for yourself and more to do with walking in as the person you already are on your best days at work, and advising from there. Interviewing for a level above your current title is not asking anyone to take a chance on you, because you already operate there. The real task is making that land with a few people in a few hours, under the kind of pressure that makes deep thinking hard to show. That is a learnable skill, and it is most of what I do with L7 to L9 candidates going for the next level.

If you want help closing the gap between the work you already do and the level they see, you can reach out to our team here:

• Ace your L7-L9 PM interviews: https://nancychu.hbportal.co/public/acing_interviews

• Ace leadership interviews across all roles: https://nancychu.hbportal.co/public/67c378d9a7c8e4001fea1a9b/1-acing_interviews

Every week I write about the thinking and communication techniques for in L7-L9 interviews. If that is useful to you, you can get them in your inbox each week.

Frequently asked questions

Can you interview for a role 1 or 2 levels above your current title?

Yes, and it happens often at this stage of a career, especially when the introduction comes through your network rather than a job posting. Companies will hire an external candidate into a level they would take much longer to promote someone into internally. What decides it is whether the loop feels you already operate at that level, not how long you have held your current title.

Why do strong candidates get downleveled after the interview?

Most downlevels come from stories that sat at the wrong altitude rather than from a weak performance. When every example centers on work you did yourself, the committee can only calibrate to the level that work represents, however impressive it was. The fix is choosing stories where you built the team, the org, or the direction, and where the outcome came through people who did not report to you.

Is L7 to L8 the hardest jump?

Many product leaders find it the hardest, because it is where the work stops being mostly yours and becomes something you produce through an org. An L8 loop wants evidence that you have shaped teams, managers, and the standard for how product gets done in your area. That is a different kind of story than the impact and revenue stories that carry an L7 loop.

How is a head of product role at a startup different from a director role at a large company?

The startup role asks for range and ownership rather than depth inside a defined lane. A head of product usually acts as the extension of the founder, covering strategy, hiring, fundraising support, and the unglamorous execution work, with very little infrastructure around them. Big-company leaders who struggle in these roles are usually the ones who need a large team and established process before they can move.

How long does it take to prepare for an interview a level up?

Most of the leaders I work with need a few weeks, and the time goes into selecting and reframing material rather than rehearsing. Practicing the same stories 40 more times makes you faster at a pattern that may not be landing at the level you want. What changes the outcome is choosing stories at the right altitude and getting your actual thinking into words.

---

About the author

Nancy Chu is an L7-L9 Product Leadership coach. She works with senior product leaders interviewing at companies like the top tech companies.

Her clients have landed more than 26 offers at L7 and above, at companies including Meta, Google, Microsoft, Stripe, Coinbase, and Calendly, with total compensation reaching $2.9M. You can see the full list at nancychu.co/wins.

The people she coaches are already exceptional at the work. What she helps with is the thinking underneath their answers, and how much of it the interviewers get to see.