"Where do you see yourself growing" is a values question disguised as a planning question. The interviewer wants to know what you want to get better at, whether your trajectory fits the role, and whether you've thought about it deliberately.

Three vectors of growth

Frame the answer around at most two of these:

1. Depth

Going deeper in your current domain.

• "I want to get really good at frontend performance — Core Web Vitals, INP work, profiling-driven optimization."
• "I want to deepen my React internals knowledge — fiber, server components, concurrent mode."
• "I want to become the person who can pick up any frontend system and reason about its constraints."

2. Breadth

Expanding adjacent areas.

• "I want to get better at product thinking — not just implementing specs but pushing back on them constructively."
• "I want to learn enough backend to design API contracts collaboratively."
• "I want to grow into accessibility expertise — it's adjacent to my current work and underinvested in most teams."

3. Impact / scope

Larger scope of influence.

• "I want to move from individual features to owning a system end-to-end."
• "I want to mentor more — bringing junior engineers up to mid level."
• "I want to influence technical direction across teams via RFCs and ADRs."
• "I want to grow into a tech lead role."

Be concrete, not aspirational

Vague: "I want to keep learning and growing." Concrete: "I've been driving the LCP work on our checkout page; over the next year I want to go deeper into perf — I'm reading Ilya Grigorik's HTTP book and have started running RUM analyses for our team."

The concrete version shows you've already started.

Anchor to what you've already done

The strongest answers reference work-in-progress: "I'm already doing X; over the next two years I want to grow into Y."

This shows:

• Trajectory, not just dreams.
• Self-awareness about where you are.
• Initiative.

Avoid the traps

"I want to be a manager"

Only say this if (a) it's true, (b) the role you're applying for has a path to it, and (c) you're applying somewhere that values it. Otherwise you signal you're not going to commit to the IC role you're interviewing for.

"I'll do whatever the company needs"

Sounds humble; reads as no preference. Companies want people with direction.

Listing every possible direction

"I want to grow in frontend AND backend AND product AND management AND..." sounds unfocused. Pick at most two.

Misaligned to the role

Applying for a senior IC role and saying "I want to spend my time on people management" is a red flag.

Tying to the role

Even better: tie the growth to what the role offers.

"From the role description, it sounds like there's a strong performance practice and complex SSR work — I'd want to deepen there. I'm also curious about the design-system side; I haven't worked closely with a system at this scale and I'd want to learn from how your team operates it."

This makes the answer specific to this interview, not a generic answer.

When you don't know

"I'm not sure exactly. What I know is I want to keep getting better at the technical depth — perf, architecture — and I want to be in a place where I'm working with engineers who are stronger than me on at least one axis. I'm open to where that leads, including potentially a tech-lead path if the work calls for it." That's honest and shows reflection.

Interview framing

"I'd frame growth in two of three vectors — depth, breadth, impact — and pick one or two specific to me. Concretely for me: I'm already driving the LCP work on our checkout; over the next two years I want to deepen in frontend performance and architecture — be the person who can pick up any FE system and reason through its constraints. Alongside that, I'm growing my product judgment — pushing back on specs constructively, not just implementing. I'd avoid vague aspirations or listing every direction; the strongest answers reference what you've already started, tie to what the role offers, and align to whether the role is IC or management."