What would you do in your first 90 days? How to answer it
Give a three-stage plan: in the first 30 days, learn the people, tools and priorities; by day 60, take on real work and deliver a first small win; by day 90, own your area and propose one improvement. Tailor each stage to this role using what you've learned from the job post and the interview, and say what you'd want to have achieved by day 90.
What the interviewer is checking
This is a situational question, and it shows up more often for experienced hires and managers, and in later rounds. The interviewer wants to see:
- That you'll learn before you change things. New hires who rearrange everything in week two cause damage, even with good ideas.
- That you'll still deliver early. Learning for three months with nothing to show is the opposite problem.
- That you understood this job. A plan that could apply to any company shows you weren't listening.
So your plan needs a clear shape (learn, then contribute, then improve) and specific details from this role.
The 30/60/90 shape
| Stage | Main goal | What you'd do | What "done" looks like |
|---|---|---|---|
| Days 1–30: learn | Understand people, tools and priorities | Meet your team and key partners one-to-one, learn the systems, read past reports, shadow the work | You can explain the top three priorities and who owns what |
| Days 31–60: contribute | Take on real work and deliver a first win | Own a set of tasks or accounts, fix one small known problem, ask for feedback | One visible result, and your manager trusts you with routine work |
| Days 61–90: own and improve | Run your area and suggest one change | Take full ownership, propose one improvement backed by what you've learned | A short written plan for the next quarter, agreed with your manager |
Say it in that order, but don't recite the table. Pick one or two specific actions per stage.
How to tailor it
Generic plans sound like this: "First I'd learn, then I'd contribute, then I'd add value." Tailored plans use details you collected:
- From the job post: the main responsibilities and tools. "The post mentions moving reporting to a new system, so in month two I'd want to…"
- From the interview so far: problems they mentioned. "You said onboarding new clients takes too long. In the first month I'd sit in on three onboardings to see where time goes."
- From your research: the company's recent news, product or customers. See what do you know about our company for how to research.
Always add a check: "Of course, I'd confirm priorities with you in the first week." It shows you won't go off on your own.
Example answers
These examples use invented details to show the shape.
Team lead (customer support)
"In the first 30 days I'd mainly listen. I'd have one-to-ones with each of the eight people on the team, sit in on calls, and read the last quarter's satisfaction scores and complaints. I'd also ask you what success looks like at six months. By day 60, I'd want to take on the weekly rota and fix one thing the team raises most. You mentioned weekend coverage, so that could be it. By day 90, I'd present a short plan for the next quarter: probably targets for response time and one change to how we handle escalations, based on what I've seen."
Individual contributor (data analyst)
"Month one, I'd learn the data: where it lives, how it's cleaned, which reports people actually use. I'd meet the three teams I'd support and ask each what question they wish they could answer. Month two, I'd take over the weekly sales report and answer one of those questions with a small analysis. Month three, I'd own the reporting fully and suggest one improvement, maybe automating the parts that are still copied by hand, since you mentioned that takes a day each week."
Sales role
"In the first 30 days I'd learn the product deeply, shadow your top reps on calls, and study the last six months of won and lost deals. By day 60 I'd be running my own calls with support, and aim to have my first pipeline built. By day 90 I'd want to be carrying my full target and to share one thing I'd noticed about why deals stall, from the calls I'd listened to."
Graduate or first job
"As my first role, the first month would be about learning how things are done here: the tools, the standards, and who to ask. I'd keep a list of questions and save them for one daily check-in so I don't interrupt people all day. By month two I'd want to be doing routine tasks on my own and checking my work against the standard. By month three, I'd want my manager to be able to hand me a task without detailed instructions, and I'd like to have taken on one small project of my own."
When they ask for it as a presentation
Some interviews, especially for managers, ask you to bring a 30/60/90 plan as a short presentation or document. Use the same table as your skeleton, one slide or section per stage, plus a slide on what you'd measure. Keep it under ten minutes and leave time for questions. The guide to job interview presentations covers timing and structure.
Mistakes to avoid
| Mistake | Why it hurts | Instead |
|---|---|---|
| "I'd change X straight away" | Sounds like you'll act before you understand | Change things in the third stage, after learning |
| A plan with no specifics | Shows you didn't listen | Use one detail from the post and one from the interview |
| Only learning, no delivery | Worries them about slow ramp-up | Include a first small win by day 60 |
| Criticising how things are done now | You don't know the reasons yet | Frame changes as "I'd look at…" |
| Ignoring the manager's priorities | Sounds like you'll go your own way | Say you'd agree priorities in week one |
Questions people ask
How long should my answer be?
About 60 to 90 seconds when asked in conversation. If they want detail, they'll ask about a stage.
Is this question only for managers?
No, but it's more common for senior roles. For junior roles, the same shape works with smaller goals: learning the tools, then doing routine work alone, then taking on something of your own.
What if I don't know enough about the role to make a plan?
Say what you'd find out first and why. "I'd want to understand how the team measures success before setting targets" is a good answer if you follow it with what you'd do once you knew.
Should I give numbers or targets?
Only if you understand their numbers. Otherwise, describe the kind of result you'd aim for and say you'd agree targets with your manager.
Can I ask them what they'd expect in 90 days?
Yes, and it's a strong question for the end of the interview. It shows you're already thinking about doing the job well.