How to answer "What would you do in your first 90 days?" — a plan, not a promise

This question rewards a specific kind of humility: enough confidence to say what you'd actually do, and enough self-awareness to admit you don't know everything yet. Candidates fail it in two opposite ways — either a vague "I'd learn the ropes and see where I can help" that says nothing, or a bulldozer plan that promises to fix everything by week two, before they've met the team or seen the real constraints. The answer that works sits between: a real plan that's still built around finding out what's actually true first.

What they're actually checking

Three things. Judgment — do you know that new hires need to learn before they act? Initiative — will you actually build something, or wait to be told? And realism — does your plan reflect how this specific job and team actually work, or is it a generic template you'd give to anyone? A strong answer proves all three by being concrete about the early listening and equally concrete about what you'd ship once you understand the terrain.

The framework: Listen → Build → Deliver

1. Listen (roughly the first 30 days). Name what you'd actually do to learn the job — the people you'd meet, the systems or accounts you'd study, the questions you'd ask to find out what's really working and what isn't. This is not filler; it's the part that makes the later phases credible.
2. Build (the next 30 days). With that context, what would you start putting in place — a process, a relationship, a first version of something — that sets up real contribution without needing full authority yet?
3. Deliver (the last 30 days). What's a believable first result by day 90? Not a moonshot — something scoped enough that a new hire could plausibly land it, that also matters to the team.

The structure signals maturity on its own: you're not promising to arrive with the answers, you're promising a disciplined way of getting to them fast.

A worked example

"In the first month, I'd focus on understanding how the team currently handles the problem this role exists to fix — sitting in on calls, reading past retros, and talking to the two or three people closest to it, so I'm not guessing at what's broken. By day 60, I'd expect to have identified one or two concrete gaps and started addressing the smaller one directly, while socializing a proposal for the bigger one with whoever owns it. By day 90, I'd want to have shipped that smaller fix and have a clear, agreed-on plan for the larger piece — something the team helped shape, not something I showed up and declared."

Notice what's absent: no invented numbers, no promise to "transform" anything. Just a believable sequence a reasonable new hire could actually follow.

How to tailor it to the role

Generic 90-day plans are the tell that a candidate hasn't thought about this job. Pull from the job description for what the team is actually short on, and shape your Listen phase around learning exactly that gap rather than the job in general. If you're switching into a new role at a company you already know — say, moving into your next role — say so; that context changes what "day one" even means and interviewers will notice if you skip past it.

Common mistakes to avoid

• The vague version. "I'd learn the systems and get to know the team" is true of every job everywhere and proves nothing.
• Overpromising. Claiming you'd overhaul a process or hit a big number by day 30 signals you don't understand how little context a new hire actually has.
• Skipping the listening phase entirely. Jumping straight to what you'd "fix" reads as presumptuous — you don't know what's actually broken yet.
• A plan with no specifics. If your 90-day plan could be copy-pasted into any job posting, it wasn't built for this one.
• Ignoring people. A plan built entirely around tasks and none around relationships misses that most early failures in a new role are relational, not technical.

The bottom line

"What would you do in your first 90 days?" isn't asking for a to-do list — it's asking whether you understand the shape of starting a new job well. Structure your answer around learning first, building second, and a believable result third, and make each phase specific to the actual role in front of you. That's the difference between a plan and a promise.

Related: What are you looking for in your next role? · What is your management style? · Tell me about a difficult customer or client