Every external interview for a bigger job has one question sitting under all the others, whether anyone says it out loud or not: have you actually done this before? If your current title is one level below the role, the honest answer is usually "partly", and the interview is where you prove that "partly" is enough.
This guide is about that proof when you are moving to a new employer. If you are going for a promotion with your current employer, the dynamics are different, and the internal interview guide covers that case.
The doubt the panel is trying to settle
A panel interviewing someone for a step up is rarely worried about skill in the abstract. They are worried about the gap between what your title says and what the job needs. A team lead applying for a manager role makes them wonder whether you have owned a budget, made a hiring call, or dealt with a performance problem with nobody above you in the room. A senior analyst applying for a lead role makes them wonder whether you have set direction for others, or only executed it well.
That doubt is reasonable, and arguing with it gets you nowhere. You answer it with evidence. The mistake most step-up candidates make is to answer with potential ("I'm ready for more", "I learn fast") when the panel wants a record. Potential is something they can only take on trust. A record they can probe, and probing is what interviews are for.
Building the record from work you already did
Very few people land a role one level up without having done some of it already. The work is finding those pieces and naming them properly. Go through the last two or three years and look for:
- Stretch work: a project or responsibility that sat above your grade, handed to you because someone trusted you with it.
- Acting up or covering: weeks or months when your manager was on leave, between roles, or overloaded, and you ran the team's priorities, signed things off, or sat in their meetings.
- Projects owned end to end: something where you set the plan, made the calls, dealt with the problems and answered for the result, even if the team was two people.
- Influence without authority: a budget you shaped without holding it, a hire you interviewed for and recommended, a process the wider department adopted because you pushed for it.
Write each one down as a short story with a decision in the middle. "I covered for my manager for six weeks" is a fact. "While my manager was on leave I had to choose between holding a launch date for a client unhappy with the scope, or delaying and renegotiating, and I chose to delay" is evidence. The six weeks are illustrative; use your own numbers.
If you already structure answers with a framework such as STAR, keep using it. The point here is which stories you pick, not how you tell them.
Talking at the altitude of the next level
The difference between levels is mostly about what you decide and what you answer for. Your answers need to sound like they come from that altitude, which means shifting the weight of each story:
- From tasks to decisions. Less "I built the report", more "I moved the report to weekly, because the leadership team kept making calls on month-old numbers."
- From effort to trade-offs. A senior role is full of choices with no clean answer. Say what you gave up and why. "We dropped the second market to protect the launch date" tells the panel you can live with a cost.
- From your work to other people's work. Mention who you brought along, coached or unblocked. If you shaped how a team spent its time or money, say so plainly, and be precise that you influenced it rather than owned it.
- From the week to the quarter. Next-level roles are judged over longer horizons. Show that you think about what happens after the project ships.
A quick test: read an answer back and look at the verbs. If they are mostly "did, built, wrote, ran", you are speaking at your current level. If you find "chose, prioritised, negotiated, stopped", you are getting closer.
Without overclaiming
There is a line between presenting stretch work well and inflating it, and panels are good at finding it. Follow-up questions will push on any claim that sounds bigger than your title: "Who signed off the budget?", "Were they your direct reports?", "What did your manager decide?"
Get ahead of it. Use precise words: "I led the project" when you did, "I ran the team day to day while my manager was out" when that is the truth, "I recommended the hire" rather than "I hired". Then name the gap yourself: "I haven't held a full budget yet. Here is the nearest I've come, and here is how I'd get up to speed." A candidate who knows exactly where their experience stops reads as more senior than one who claims everything. Their story also survives the second round.
The questions that test it
Panels rarely ask "can you do the bigger job?" directly. They ask questions that reveal it. Expect some version of:
- "Tell me about a decision you made without your manager's input."
- "Describe a time you disagreed with someone more senior. What did you do?"
- "How have you handled someone on the team who was not delivering?"
- "What is the biggest budget or headcount you have had influence over?"
- "What would you do in your first three months here?"
- "Why now?"
The first-months question matters more than it looks. It is the only one where you get to show next-level thinking about their situation instead of your past, so prepare it like a short plan: what you would want to understand, who you would meet, and the first real decision you expect to face.
If they ask how you manage people, that question has its own guide. The short version is to describe what you actually do, not a style label.
Salary and your own questions
The end of the interview is still part of the test. Two things tend to go wrong here.
Salary at the new level
If you anchor your expectations on your current pay, you may price yourself at your current level, which quietly undercuts everything you said in the interview. In many cases it is more useful to research what the role itself tends to pay in that sector and location, and talk about the range for the job rather than a raise on your current salary. Where you are allowed to decline sharing your current pay, it is often reasonable to steer back to the role. Rules on salary history questions vary by country and region, so check what applies to you. Negotiation itself is a bigger subject with its own articles.
Questions to ask them
A candidate thinking at the next level asks how the role is set up to succeed, not just what it involves:
- "What decisions will this role own that the previous person didn't?"
- "How will you judge success at six and twelve months?"
- "What budget or headcount sits with this role, and what still goes up for approval?"
- "Is this a new position or a backfill? If it is a backfill, what would you like done differently?"
- "Who at the level above will I work with most closely?"
The answers also tell you whether the step up is real. A bigger title with no decision rights is a common trap, and it is better to spot it before you sign.
Before the interview
Pick four stories from your stretch work, acting-up periods and end-to-end projects. For each one, write down the decision at its centre, the trade-off, and the exact limit of your authority. Rehearse the first-months answer as a plan, and prepare one honest sentence about the gap you have not covered yet.
Then check that your CV tells the same story, with your scope described accurately. A tool like Postulit can turn your LinkedIn profile into a CV draft that you then tighten for the target level.
The panel is not asking whether you have held the title. It is asking whether you have already made the decisions that come with it. Bring the decisions.