A 30-60-90 day plan for an interview is a one-page outline of what you would do in your first three months in the role: learn in the first 30 days, start contributing by day 60 and own or lead something by day 90. Bring one when the company asks for it, or when you're interviewing for a senior, management, product or sales role where the hiring manager is likely to ask how you would approach your first months.
A good plan is short, specific to the job description and honest about what you don't know yet. It isn't a promise. It shows the hiring manager how you think about ramping up, who you would talk to and what "good" looks like in your first quarter. This guide covers when to bring one, the learn-contribute-lead structure, a one-page template we wrote, example plans for three roles and how to present it in a hiring manager interview.
This is different from a job-search plan. If you're looking for a 30-60-90 plan to organise your search after losing a job, see our job search plan after a layoff.
When should you bring a 30-60-90 day plan to an interview?
You don't need one for every interview. It helps most when the role has room for judgment about priorities, and when the hiring manager round is about how you would do the job rather than whether you can solve a set problem.
| Situation | Bring a plan? | How to use it |
|---|---|---|
| The recruiter or job post asks for one | Yes, always | Follow any format they give; keep it to one page unless told otherwise |
| Manager, director or team lead role | Yes | Have it ready for "How would you approach your first 90 days?" |
| Senior individual contributor (staff engineer, senior PM, senior analyst) | Usually | Use it as a talking point in the hiring manager round |
| Sales or customer success role | Usually | Focus on territory or account learning, pipeline and first wins |
| Entry-level or new graduate role | Optional | A short learning-focused version can help in a final round |
| Early technical screens or coding rounds | No | Save it for the manager or final round |
Build the plan after the first conversations, not before. Earlier rounds tell you the team's real priorities, and a plan that uses them is far more convincing than one written from the job post alone. If you're preparing for the manager round in general, start with how to prepare for a hiring manager interview.
The structure: learn, contribute, lead
Most 30-60-90 plans follow the same arc. Each phase has a different goal, and the plan is clearer when each phase has two to four concrete items rather than a long list.
Days 1–30: learn
- Meet the people you'll work with most: your manager, teammates, key partners and, where relevant, customers.
- Learn the systems, product, data or accounts you'll own. Name them if you know them from the job description.
- Understand how success is measured: the team's goals, metrics and the decisions coming up.
- Deliver one small, useful thing, such as a bug fix, a documentation update or a customer call summary, so you learn the workflow end to end.
Days 31–60: contribute
- Take ownership of a defined piece of work and ship it.
- Share one observation or proposal based on what you learned, framed as a question for your manager to react to.
- Build working routines: how you report progress, how you plan with partners.
Days 61–90: lead
- Own a larger outcome, such as a project, a metric, a process or a team initiative.
- Agree with your manager on goals for the next quarter.
- For managers: have a view on team strengths, gaps and hiring needs.
For each phase, include how you'll know it worked. "Ship the first feature" is a task; "first feature shipped and used by at least one customer team" is a measurable result. Use the numbers you heard in the interviews, and mark any guesses as assumptions.
One-page 30-60-90 template we wrote
This is a template we wrote. Copy the structure into a document or slide and fill it in with what you know about the role.
| Days 1–30: Learn | Days 31–60: Contribute | Days 61–90: Lead | |
|---|---|---|---|
| Goal | Understand the team, users and systems | Own and ship a defined piece of work | Own an outcome and set next-quarter goals |
| Priorities | 2–3 things to learn, named | 1–2 deliverables | 1 larger project or metric |
| People | Manager, team, key partners | Partners you'll ship with | Stakeholders for the next plan |
| Deliverables | One small, real contribution | A shipped piece of work, a proposal | Project results, a quarterly plan |
| How I'll measure it | Agreed onboarding goals met | Delivered on time, used by someone | Metric moved, plan approved |
| Assumptions to check | List what you guessed from the job description and want to confirm with the manager | ||
The last row matters. It tells the manager you know the plan is a draft and invites them to correct it, which turns your presentation into a conversation.
Example 30-60-90 plans for engineer, PM and manager roles
These are examples we wrote for fictional roles. Replace every detail with what you learned about your target job.
Software engineer (backend, payments team)
- 30 days: Set up the local environment and ship two small fixes. Read the payment flow end to end and the last three incident reviews. Meet the on-call lead and the product manager.
- 60 days: Own the retry-logic improvement the manager mentioned and ship it behind a flag. Join the on-call rotation as a secondary.
- 90 days: Lead the design review for moving refunds to the new service. Propose two reliability metrics for the team dashboard.
Product manager (B2B onboarding)
- 30 days: Interview eight customers and the support lead. Review the activation funnel and current roadmap. Learn how engineering plans and estimates.
- 60 days: Write a problem brief on the biggest onboarding drop-off and agree on one experiment with design and engineering.
- 90 days: Launch the experiment, share results and present a prioritized onboarding roadmap for next quarter.
Engineering manager (team of six)
- 30 days: Hold one-on-ones with every team member and key partners. Learn the delivery process, on-call load and current commitments. Make no structural changes yet.
- 60 days: Fix one process pain the team raised, such as review delays. Set up a regular planning rhythm with product.
- 90 days: Share a team health summary with your manager, agree on hiring needs and set goals for next quarter.
Notice what the manager plan leaves out: big changes in the first month. Hiring managers for leadership roles often want to see that you'll listen before you act. If you're preparing for a leadership loop, our guide to the engineering manager onsite interview covers the other rounds, and how to describe your leadership style pairs well with the plan.
How do you present a 30-60-90 day plan in a hiring manager interview?
Wait for a natural opening. The cleanest one is a direct question such as "How would you approach your first few months?" Other openings include "What would you focus on first?" or the time for your questions at the end. If the plan was requested, ask at the start of the round when they'd like to see it.
- Frame it. "I put together a short draft of how I'd approach the first 90 days, based on what I've heard so far. Can I walk you through it?"
- Keep it to three to five minutes. One or two sentences per phase, with the measurable outcome for each.
- Name your assumptions. "I assumed the retry work is the top priority. Is that right?"
- Ask for a reaction. "What would you change?" Then listen. Their answer tells you what they care about most.
- Offer to leave a copy. In person, bring printed copies. On video, have it ready to send after the call.
The plan also makes a strong reference in your close: "As I mentioned in my plan, the first thing I'd do is…" Our guide on how to end an interview strong shows how to fit it into a closing statement. If the plan becomes a formal presentation, follow how to prepare a presentation for a job interview instead.
Mistakes to avoid
- Too long. More than one page, or more than five minutes spoken, and the manager stops listening.
- Too generic. "Learn the culture, build relationships, add value" fits every job. Name the systems, metrics and people.
- Overpromising. Claiming you'll rebuild the platform in 90 days suggests you don't understand the role. Pick realistic outcomes.
- Criticizing the current team. Phrase improvements as questions and observations, not fixes for problems you assume exist.
- Not listening to feedback. If the manager pushes back, adjust out loud. That reaction is part of what they're assessing.
Expect follow-up questions on any item in the plan. Our list of hiring manager interview questions includes several that build on it, such as how you'd handle a priority change in month two.
Practice it
Present your plan out loud three times before the interview, timing each run, and practice answering "What would you change if your first priority turned out to be wrong?" The goal is a calm, conversational walk-through, not a recital.
For realistic follow-ups, rehearse the manager round with a free AI mock interview. In CoPilot Interview's desktop app, Mock Interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10 with what to fix. You can use it free for 15 minutes a day with no account. Follow each employer's rules on AI tools, and use AI to prepare beforehand.
Rehearse the manager round
Practice answering first-90-days and leadership questions out loud and get each answer scored with what to fix.
Try a free AI mock interviewFAQ
What is a 30-60-90 day plan in an interview?
It is a one-page outline of what you would do in your first three months in the role: learn in the first 30 days, contribute by day 60 and own or lead something by day 90. It shows the hiring manager how you think about ramping up.
Should I bring a 30-60-90 day plan to every interview?
No. Bring one when it is requested, or for manager, senior, product and sales roles where the hiring manager is likely to ask about your first months. Skip it for early screens and coding rounds.
How long should a 30-60-90 day plan be?
One page, with two to four items per phase. You should be able to walk through it in three to five minutes.
What do you put in the first 30 days of a 30-60-90 plan?
Focus on learning: meeting your manager, team and key partners, understanding the systems or accounts you will own, learning how success is measured and delivering one small, useful contribution.
How do you present a 30-60-90 day plan in an interview?
Wait for an opening such as a question about your first months, frame it as a draft based on what you have heard, walk through each phase in a sentence or two, name your assumptions and ask what the manager would change.
Is a 30-60-90 day plan the same as a job search plan?
No. In an interview it describes your first three months in a new role. A 30-60-90 job search plan organises your search after a layoff, which is a separate topic.