When an interviewer asks "what are you looking for in your next role?", they are not making small talk. They are checking one thing: do your goals match the job in front of you, and will you stick around once you have it.
The strongest answer does three things at once. It names a specific, role-relevant thing you want (not "a good opportunity"), it ties that want to something the company actually offers, and it signals you plan to grow there rather than treat the job as a layover. According to Indeed's career advice team, hiring managers use this question to read your motivation, your culture fit, and your likelihood of staying.
Here is the short version before the detail:
- Lead with a concrete skill or type of work you want to do more of
- Connect it to the company by name and by something specific about them
- Avoid salary, perks, and complaints as your opening note
- Don't signal you'll leave ("a stepping stone toward my own startup")
This guide gives you a repeatable structure, multiple example answers you can adapt, and the mistakes that quietly sink otherwise-strong candidates.
Why interviewers ask this question
This question is a fit test wearing a casual disguise. The interviewer wants to know whether the role you describe in your head is the role they are actually hiring for.
There are three things they are listening for:
- Alignment. Does what you want line up with what the job delivers day to day? If you say you want deep technical ownership and the role is 70% stakeholder meetings, that mismatch shows up fast.
- Longevity. Replacing a hire is expensive. They want to hear that this looks like a place you would stay and grow, not a six-month bridge to something else.
- Self-awareness. Candidates who know what they want sound like professionals. Candidates who say "I'm open to anything" sound directionless, even when they mean to sound flexible. University career centers make the same point: James Madison University's career guide lists "describe what is most important to you in a job" as a core question precisely because the answer reveals priorities.
The Muse frames a four-step approach that maps cleanly to these goals: start with your skills, explain your motivation, connect to your long-term goals, and close with company-specific detail. The structure works because it answers the unspoken questions in the order the interviewer cares about them.
One thing worth knowing: this question is a close cousin of "what are your career goals?", "why do you want this job?", and "what motivates you?" If you have prepped those, you already have most of the raw material here.
A simple framework that works in any interview
You do not need a script. You need a structure you can fill with your own specifics. Four moves, in order:
- Name what you want to do more of. Pick one or two skills or types of work that genuinely energize you and that the role requires. "I'm looking for a role where I can own data pipelines end to end" beats "I want growth opportunities."
- Say why it matters to you. A sentence on motivation makes the answer human. Seeing your work reach real users, mentoring juniors, solving messy ambiguous problems — pick what's true.
- Point at the future. Show you are thinking past the first six months. "I'd like to grow into leading a small team over the next few years" signals commitment without overreaching.
- Land on the company. Close with one specific, researched detail about *this* employer that connects to everything above. This is the line that proves you are not reciting a generic answer.
The table below shows how the same framework adapts across very different roles.
| Step | Software engineer | Marketing manager | Career switcher (finance → data) |
|---|---|---|---|
| What you want | Own backend systems end to end | Run full-funnel campaigns, not just one channel | Apply analytical skills to data problems |
| Why it matters | Enjoys solving scaling problems | Motivated by measurable revenue impact | Wants work that uses statistics daily |
| Future | Grow into a tech lead | Build and mentor a small team | Move toward an analytics specialty |
| Company hook | Your move to event-driven architecture | Your push into product-led growth | Your data team's mentorship culture |
Notice that the company hook in each row is something you could only know after doing real homework. That is the part most candidates skip, and it is the part interviewers notice most.
Example answers you can adapt
These are written as *hypothetical* examples to show the framework in motion. Do not memorize them word for word — swap in your real skills, motivations, and the actual company detail.
Example 1 — Mid-level software engineer
> "In my current job I've spent most of my time on the backend, and that's the work I want more of — owning services end to end rather than picking up scattered tickets. I really enjoy the scaling problems, the part where a system that worked at 10,000 users starts breaking at a million. Longer term I'd like to grow into a tech lead role. That's a big part of why this team stood out to me: I read about your move to event-driven architecture last year, and that's exactly the kind of work I want to be in the room for."
Example 2 — Marketing manager
> "I'm looking for a role where I can run campaigns across the full funnel instead of being boxed into a single channel. What motivates me is seeing the line move — being able to point at revenue and say my work did that. Down the road I'd like to build and lead a small team. Your shift toward product-led growth is what got me excited here, because that's a strategy I want to help execute, not just observe."
Example 3 — Career switcher (finance to data analytics)
> "I'm making a deliberate move from finance into data analytics, so what I'm looking for is a role where I can use my analytical background on data problems every day. I've always been the person on my team who wanted to dig into the *why* behind the numbers. I know I'm earlier in this specific path, so I'm looking for a place with a strong mentorship culture — which is exactly what your data team described in the job posting. That's the kind of environment I want to grow in for the long haul."
Each answer follows the same four beats. Each one ends on a real, researched company detail. That ending is what separates a forgettable answer from a memorable one.
Mistakes that sink the answer
Most weak answers fail in predictable ways. Avoid these:
- Leading with money or perks. Compensation matters, and you should negotiate it — but not here. Opening with salary or remote days makes you sound transactional. Save it for the salary-negotiation conversation later in the process.
- Being vague. "I just want a good opportunity" or "I'm keeping an open mind" reads as no opinion at all. Specific criteria make you sound like someone who knows their own value.
- Signaling you'll leave. If your answer is "I want to learn X so I can launch my own thing next year," the interviewer hears a resignation letter. Frame your growth as growth *with them*.
- Trashing your current job. Venting about a bad manager makes you look like a flight risk and a complainer. As Career.io's guidance notes, keep the answer forward-looking and tied to your goals rather than your grievances.
- Forgetting the company. A perfect answer about your goals that never mentions *this* employer is just a monologue. The company hook is mandatory.
If you want to pressure-test your delivery, pair this with broader interview prep like how to ace an interview and a strong tell me about yourself answer — these questions reinforce each other, and a consistent story across all three is what builds interviewer confidence.
The prep that makes the company hook real
The hardest part of this answer is the last line: the specific, true detail about the employer. You cannot fake it, and generic praise ("I love your culture") is worse than nothing.
That detail usually comes from knowing who you are talking to. The fastest path into a role is rarely the apply button — it is a real conversation with the person doing the hiring, who can tell you what the team actually cares about. Articuler helps jobseekers find the actual hiring manager behind a posting using semantic search across 980M+ profiles, then builds a Playbook on what that person works on and values — so your "company hook" comes from genuine intel, not a guess. It also drafts personalized outreach that gets far higher reply rates than a generic LinkedIn note, which is how you get that conversation in the first place.
FAQ
How long should my answer be?
Aim for 30 to 60 seconds — roughly three to five sentences. Long enough to hit all four beats (skill, motivation, future, company), short enough that you are not rambling. If the interviewer wants more, they will ask a follow-up.
Should I mention salary when asked what I'm looking for?
No. This question is about fit and direction, not compensation. Bringing up pay here makes you sound transactional. Handle salary in a dedicated negotiation conversation later in the process, where it belongs.
What if I genuinely don't know what I want next?
Pick the part of your past work you'd most like to do more of and build from there — even a partial direction beats "I'm open to anything." Doing real research on the role often clarifies what you want, so prep the specific job before the interview rather than improvising in the room.
How is this different from "why do you want this job?"
"Why do you want this job" is about the specific role and employer. "What are you looking for in your next role" is broader — it asks about your criteria and direction generally. The trick is to answer the broad question in a way that still lands on this specific company at the end.
Can I use the same answer for every interview?
Use the same four-step *structure*, but never the same closing line. The final company-specific detail must change for each employer. Reusing a generic ending is the single fastest way to sound rehearsed and uninvested.