How to Write a 30/60/90 Day Plan for a Job Interview
What a 30/60/90 Day Plan Actually Is
A 30/60/90 day plan is a one-page document that lays out what you will do in your first three months on the job. Hiring managers ask for it in final-round interviews for two reasons. First, it shows whether you understand the role beyond the job description. Second, it shifts the interview from "are you a fit" to "let us discuss how you would actually work."
Most candidates write something generic. Learn the team. Build relationships. Identify quick wins. That is the version that loses to the candidate who shows up with a plan tied to the actual problems the team is trying to solve.
This guide gives you the structure, the content, and a real example you can adapt.
When You Will Be Asked
30/60/90 day plans are most common in:
Final-round interviews for manager and director roles.
Sales roles where ramp time is part of the evaluation.
Product manager roles where strategy is the job.
Operations or program manager roles where the first quarter sets the pattern.
Executive roles where the board wants to see a 100-day plan.
If you are interviewing for one of these roles and have not been asked for a plan, offer one. "I have been thinking about how I would approach the first 90 days. Would it be useful if I shared a plan in the next round?" Most hiring managers will say yes, and you control the framing of the conversation.
The Structure That Wins
A 30/60/90 day plan should be one page, three sections, with clear headers. Hiring managers do not have time to read a five-page document. They want to see the shape of your thinking quickly.
Days 1 to 30: Listen and Learn. What you will do to build context.
Days 31 to 60: Diagnose and Plan. What you will start to test, propose, or pilot.
Days 61 to 90: Execute and Show Impact. What you will deliver or set in motion.
Under each section, include three to five specific actions. Vague aspirations like "build relationships across the org" are bullets every other candidate uses. Specific actions like "meet with the top 10 accounts to understand renewal risk" tell the hiring manager you know what the role actually requires.
What to Include in Each Section
Days 1 to 30. Listen and Learn.
The first 30 days are about context, not action. Hiring managers do not expect you to ship anything. They expect you to ask the right questions and not break anything.
Include: A list of stakeholders you will meet with in week one. The specific dashboards, tools, or data sources you will dig into. The customers, accounts, or projects you will review. One or two open questions you will be researching.
Avoid: Generic onboarding language. "Complete HR onboarding" does not need to be on the plan.
Days 31 to 60. Diagnose and Plan.
By day 60, you should have a point of view. This section is where you signal that you can move from listening to thinking.
Include: A working hypothesis on what is going well and what needs to change. A draft proposal you will share with your manager. One or two pilots or tests you will start. Specific metrics you will begin tracking.
Avoid: Big declarations like "Restructure the team." You do not know enough yet, and hiring managers do not want to hire someone who will reorg in month two.
Days 61 to 90. Execute and Show Impact.
By day 90, you should be able to point to something concrete that moved.
Include: A specific deliverable. A pilot result. A relationship that turned a corner. A process you put in place. A measurable change in the metric that matters to your manager.
Avoid: Vague claims like "I will be fully ramped." Hiring managers know everyone says that. Show what fully ramped looks like.
The Research You Need to Do First
You cannot write a useful 30/60/90 day plan without doing real homework on the team and the company. The candidates who win these interviews spend three to six hours preparing the plan.
Research checklist:
Read the last 4 earnings calls or shareholder letters if the company is public.
Read the company's blog and press releases from the past 6 months.
Search LinkedIn for the team you would lead or work with. Look at their backgrounds, tenure, and recent posts.
Look up the hiring manager's posts, podcasts, or articles. Note their language. Note what they care about.
Read 3 to 5 customer reviews on G2, Capterra, or Trustpilot.
Look at the company's job postings to understand where they are investing.
For more on company research before interviews, see how to research a company before an interview. For the actual interview structure that gets you to the 30/60/90 stage, see our second round and panel interview prep guide.
Real Example: Director of Customer Success
Here is a working version of a 30/60/90 day plan for a Director of Customer Success role at a Series C SaaS company with a known retention problem.
Days 1 to 30. Listen and Learn.
Meet 1:1 with every CSM and CS Manager in week one. Goal: understand current playbooks and where time goes.
Review the last 24 months of NRR data. Segment by ICP, ARR band, and tenure to find the leak.
Sit on 10 customer calls (renewal, escalation, onboarding) across segments.
Meet with CRO, VP Product, and Head of Support to align on what good retention looks like.
Audit the current health score model. Test it against 20 known churn cases from the past 6 months.
Days 31 to 60. Diagnose and Plan.
Draft a working hypothesis on the top 3 drivers of churn and present to the CRO and Product leadership.
Propose a revised CS coverage model based on customer segment and risk, not headcount.
Pilot a 30-minute weekly account standup with the 20 at-risk accounts.
Build a leading-indicator health score based on the patterns I find in the audit.
Start a customer advisory program with 6 strategic accounts.
Days 61 to 90. Execute and Show Impact.
Deliver a written retention plan with specific NRR target by quarter.
Roll out the new coverage model with onboarding for the team.
Save or stabilize at least 3 of the 20 at-risk accounts.
Hire or shift 1 senior CSM to the strategic account segment.
Establish a monthly business review cadence with the top 25 accounts.
This plan works because it is specific to the role and references real signals from the research. It also makes promises the candidate can deliver in 90 days, not aspirations they cannot.
How to Present the Plan in the Interview
Send the plan as a one-page PDF or shared doc 24 hours before the final-round meeting. Do not surprise the hiring manager with it on screen. Give them time to read.
In the meeting, walk through the plan in 8 to 10 minutes. Then ask: "What feels right? What feels off? What would you push me to do differently?" That question converts the interview into a working session, which is exactly what you want.
When the hiring manager pushes back, do not defend. Take the feedback. Say something like, "That is a good point. If I had two more weeks of context, I would probably revise this section to focus on X." That answer shows you are coachable and adaptive, which are two qualities every manager hires for.
The Common Mistakes That Sink Candidates
Mistake 1: Promising too much in the first 30 days. Candidates who promise to "rebuild the team" or "launch new pricing" in month one show they do not understand how organizations actually change.
Mistake 2: Generic bullets. "Meet stakeholders" or "Learn the product" tells the hiring manager nothing.
Mistake 3: No metrics. A plan without numbers reads like a wish list. Even a directional metric ("improve qualified pipeline conversion by 10 points") is better than none.
Mistake 4: Ignoring stakeholders. Most roles fail not because the work is wrong but because the person did not align with the right partners. Build stakeholder alignment into the plan explicitly.
Mistake 5: Treating it as a one-time deliverable. The best version of this plan becomes the working document you and your new manager review in week two of the actual job. Write it like a working document, not a sales deck.
How to Tailor the Plan to Different Role Types
Sales roles. Day 1 to 30 should include time with the existing book, the top 10 accounts, and the sales playbook. Day 31 to 60 should include a clear pipeline target by month 3, with named accounts. Day 61 to 90 should show first closed business or a meaningful pipeline build with specific dollar values.
Product manager roles. Day 1 to 30 should include time with engineering, design, customers, and the existing roadmap. Day 31 to 60 should include a written point of view on roadmap priorities and a proposed sequencing change. Day 61 to 90 should include a shipped or scoped initiative tied to a business metric.
People manager roles. Day 1 to 30 should include 1:1s with every direct report and skip-level meetings with their reports. Day 31 to 60 should include a written team assessment, a draft of the next quarter's goals, and one or two coaching investments with specific reports. Day 61 to 90 should include a shipped team outcome and one talent decision (hire, move, promote, or coach).
Executive roles. The 30/60/90 plan extends to 100 days and often includes board-level deliverables. Stakeholder mapping is more important than for any other role. The first 30 days should include time with the CEO, the board chair, peers, and the top 20 customers or partners.
Where Avery Comes In
The reason most strong candidates do not even get to the 30/60/90 day stage is that recruiters and hiring managers screen them out at the LinkedIn level before the conversation starts. The candidates who consistently reach final rounds have a profile that reads like someone who already thinks in 90-day plans.
Run an Avery audit and we will tell you exactly what your LinkedIn signals to a hiring manager, where it falls short of the bar for the roles you are targeting, and what to fix before your next final-round interview.