Interview questions

The hard ones

How to answer "What are you looking for in your next role?"

This question sounds like small talk and isn't — it's the screener deciding whether to spend their credibility on you. Here's what they're actually listening for, the four answers that cost people the round, and a way to build yours in about a minute.

Why they ask it

The person on the phone has to hand you off. They'll walk into a room, physical or virtual, and say "this one's worth your time." To do that they need one clear sentence about what you want. If your answer gives them nothing to repeat, they can't advocate for you, and they move on to the next resume.

They're also checking fit in the cheapest possible way. If you want to manage people and this job has no reports, better to find out now. If you want deep technical work and this role is 60 percent meetings, same. They're not trying to catch you. They're trying to avoid wasting four rounds on a mismatch.

And there's a third thing, quieter. They want to know you've thought about it. Someone who can say what they want has a direction. Someone who says "I'm open to whatever" has given up on direction, and that's easy to read as desperation — even when it's really just politeness or exhaustion.

What not to say

"I'm pretty flexible. I'm open to anything."

You meant it as easygoing. It lands as directionless. The screener now has nothing to say about you in the handoff meeting, so they say nothing. If you're genuinely open because you need work, that's real — but say it as a range, not a blank: "I'm focused on [type of work], and I'd consider [adjacent type] if the team's right."

A list of what you're escaping — the bad manager, the reorg, the politics.

The rest of the call becomes about your last job instead of this one. Every complaint, even a fair one, makes the interviewer wonder how you'll describe them in a year. You don't have to pretend the last place was great. Convert it: "I'm looking for a team where priorities hold for more than a quarter" says the same thing and points forward.

Leading with money, title, or remote days.

Those matter and you should absolutely ask — just not in the first ninety seconds. Opening with them tells the screener you're shopping, not interested, and they'll deprioritize you against someone who seems engaged. Answer the work question first. Then ask about comp in the same call, before you hang up.

"Growth. A challenge. Somewhere I can make an impact."

Three words that describe every job ever posted. The interviewer hears nothing and writes nothing down. Replace each one with the actual thing: growth into what, challenge of what kind, impact on which problem.

How to build a strong answer

  1. Start with the work, not the conditions.
    Name the kind of problem you want handed to you. Not the title — the work. "I want to own a product line end to end, including the messy parts like pricing." "I want to be the person who untangles data that three teams disagree about." One sentence. This is the part they repeat to the hiring manager, so make it repeatable.
  2. Add two conditions, not seven.
    Conditions are things like team size, how much autonomy, how close to the customer, how much structure, industry, pace. Pick the two that would actually change your yes to a no. Listing seven makes you sound impossible to place. Two makes you sound like you know yourself. If one of yours is stability after a layoff, say it plainly: "After [company] went through layoffs, I'm looking for a team with a clear runway." That's an honest requirement, not a weakness.
  3. Connect it to this job with one specific detail.
    One detail from the posting or the company — a specific responsibility, a product, something the recruiter said in the first two minutes. "That's part of why the [specific responsibility] line in the posting caught me." One is enough. Reciting the whole job description back sounds like flattery and tells them nothing about you.
  4. Stop at about a minute, then ask one question.
    Forty-five to sixty seconds is the target. When you've said your three things, stop. Then hand it back: "Does that line up with how you'd describe the role?" That question does real work — it gets them talking about the job, and their answer tells you whether to adjust everything else you say on the call. Practice out loud once. Not to memorize it, just so the shape is in your mouth.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, laid off, fifteen years in one industry, hasn't interviewed since 2016.

Two things, really. The work I want is the operations side — taking a process that's held together with spreadsheets and people's memories and turning it into something that runs. That's what I spent most of my time on at [company], and it's the part I'd pick if I could pick. The other thing is honest: after the layoff, I'm paying attention to whether a team is funded and where the work sits in the company's priorities. I'm not chasing a title. I want to be somewhere the work matters for more than one quarter. That's part of why the [specific responsibility from the posting] piece of this role stood out. Does that match how you'd describe it day to day?

It names the work in concrete terms, and it says the stability thing out loud instead of dancing around it. Nobody penalizes a laid-off candidate for wanting a stable team. They penalize vagueness. Adapt the specifics — the strength here is the shape, not the words.

Twenty-four, one internship, applying for a first real job.

I'm looking for a place where I'll get real feedback. My internship at [company] was good, but I was mostly handed finished work to check. I want to be on a team where someone will look at what I made and tell me what's wrong with it, because that's how I get better faster. Work-wise, I want to stay close to [the specific type of work — writing, analysis, code, customers], and I'd rather be a small part of a strong team than the only person doing this job somewhere. This role looked like it sits on a team of [number, if you know it], which is why I applied. What does the first six months usually look like for someone new here?

It doesn't fake experience. Wanting feedback and wanting to be around better people is a completely legitimate answer at this stage, and it signals coachability without using the word. The question at the end is one a new grad can genuinely ask.

Employed, quietly looking, doesn't want to trash the current job.

I've been at [company] for [number] years and I've learned a lot there. What I'm looking for next is more ownership of the outcome, not just the deliverable. Right now I build the thing and hand it off; I'd rather be accountable for whether it actually worked and be able to change it when it doesn't. The other piece is scope — I want to work on problems that touch more than one team, because that's where I've done my best work. This role reads like both of those are part of it, especially [specific detail]. Is that fair, or is it narrower than it sounds?

It explains the move without a single complaint. "More ownership of the outcome" is true, forward-facing, and doesn't require you to say anything bad about people you still work with. The closing question protects you from overselling a role that's smaller than advertised.

What comes next

Answer this one well and the interviewer usually goes here:

  • What would make you turn this job down?
  • What didn't you get in your last role?
  • Where do you want to be in three years?
  • What are your salary expectations?
  • What other roles are you interviewing for right now?
  • What's the part of this job you're least sure about?
  • How soon could you start?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You already know what you want out of your next job — this is just the work of saying it in three sentences instead of thirty, and that's a thing you can practice tonight.