How to answer "What are you looking for in your next role?" — real criteria, not a wish list

The easy version of this answer is a wish list — growth, a great culture, interesting problems, room to learn. It's not wrong, exactly, it's just interchangeable: almost any candidate could say the same thing about almost any job. What actually answers the question is naming the specific conditions you do your best work under, backed by real evidence, and showing they line up with what's actually in front of you.

Why interviewers ask it

This is a two-way fit check disguised as a simple question. Interviewers are listening for self-knowledge (do you actually know what makes you thrive, or are you guessing?), honesty (are your criteria real, or picked to sound good?), and alignment (does what you're describing match what this role can genuinely offer?). A mismatch here, caught early, saves both sides a bad hire — which is exactly why a specific, honest answer serves you better than a flattering, vague one.

The framework: Criteria → Evidence → Fit

1. Criteria. Name two or three concrete things you're looking for — a level of ownership, a specific problem domain, a working style, direct mentorship. Specific enough that not every job would qualify.
2. Evidence. A brief reason each criterion is real for you — something you've noticed from past roles about what made you thrive or what made a role a poor fit.
3. Fit. A direct, honest tie from your criteria to this specific role — not a forced connection, a genuine one.

The Evidence step is what separates a real answer from a rehearsed one. "I want more ownership" is a preference; "on my last team I was at my best once I owned a project end to end instead of executing someone else's spec, and I want more of that" is a preference with a reason behind it — which is what actually makes it believable.

A worked example

"Two things matter most to me right now. First, real ownership over a defined problem area rather than a rotating set of tickets — I noticed on my last team that my best work happened on the one project where I owned the outcome end to end, not just the execution. Second, being close enough to the people using what I build to actually hear how it lands, since the projects I've cared most about were ones where I got that feedback directly instead of through three layers of summary. From what I've read about this role, both of those seem genuinely built in — a defined problem area and a small team close to the actual users — which is a big part of why it stood out to me."

Criteria (specific, not generic) → Evidence (a real pattern noticed from past work) → Fit (an honest, specific tie to this role). Nothing here could be copy-pasted into an answer for a different job.

What if you're not sure what you're looking for yet?

That's worth figuring out before the interview, not during it. Look back at the roles or projects you've genuinely enjoyed and the ones you didn't, and ask what was actually different about them — scope, autonomy, the kind of problems, who you worked with. The pattern that emerges is a far more honest answer than picking a criterion because it sounds impressive. Working through your own history out loud — the same self-audit that helps with explaining a resume gap honestly — tends to surface real criteria faster than trying to invent them cold.

Common mistakes to avoid

• A generic wish list. "Growth, great culture, interesting challenges" could describe any job at any company and signals no real thought.
• Leading with compensation. It may matter, but naming money as the primary criterion here undersells the rest of what you're looking for — and it belongs more naturally in a different conversation.
• No evidence behind the criteria. A stated preference with nothing backing it is a guess dressed up as self-knowledge.
• Criteria that contradict the role. Describing a need for structure when interviewing for a fast, ambiguous startup role (or the reverse) is worth addressing honestly, not glossing over.
• Badmouthing why past roles fell short. Framing your criteria entirely around what a former job lacked reads as grievance, not direction.

The bottom line

"What are you looking for in your next role?" rewards specific, evidence-backed criteria over a flattering wish list. Name what actually matters to you, show real evidence it's true, and connect it honestly to the role in front of you. That combination reads as someone who knows themselves — which is a far stronger signal than any list of nice-sounding qualities.

Related: Why is there a gap in your resume? · A time you met a tight deadline · Why should we hire you?