How to evaluate a 30-60-90 day plan in an interview
On this page
- What the exercise can and cannot tell you
- Set a brief that makes plans comparable
- What a strong plan contains
- Red flags
- Follow-up questions that separate rehearsal from thinking
- The scoring rubric
- Capturing what the candidate actually said
- Adjust the bar for seniority
- Mistakes interviewers make
- After the hire
- Questions people ask
Asking a candidate to present a 30-60-90 day plan is common for manager, sales, customer-facing and senior roles. It is also one of the easiest exercises to score badly. Interviewers tend to reward the most polished slides, the most confident delivery, or the plan that most resembles what they would have written themselves. None of those predicts how the person will actually spend their first three months.
This guide covers how to evaluate a 30-60-90 day plan in an interview: how to set a brief that is fair, what a strong plan contains, the red flags, the follow-up questions that separate a rehearsed plan from real thinking, and a four-level scoring rubric. For what a good plan looks like once someone is hired, see the 30-60-90 day plan template for new hires.
What the exercise can and cannot tell you
A candidate's 30-60-90 day plan is a work sample for a narrow set of skills: how they approach learning a new environment, how they prioritize, how they turn goals into checkable milestones, and how they respond when their assumptions are challenged. It is weak evidence for domain expertise, because the candidate does not know your systems, and weak evidence for execution, because nothing in the plan has been done yet.
Decide before the interview which competencies on your scorecard the plan is meant to test, and score only those. If the interview scorecard for the role lists "prioritization" and "stakeholder management," the plan feeds those two lines. It should not also become the de facto score for communication, executive presence and culture.
Set a brief that makes plans comparable
Plans can only be compared if every candidate answered the same question with the same information. Before asking for one, write a short brief and give it to every candidate at the same stage:
- The role's real situation in a paragraph: team size, what the team owns, one or two known challenges you are comfortable sharing.
- The format and limit: for example, no more than five slides or two pages, and a 15-minute presentation followed by 20 minutes of questions.
- The expected effort: say plainly that a few hours is enough and that you are looking at thinking, not design.
- What they can ask: offer a short call or email thread for questions, and give every candidate the same offer.
- What you are not asking for: a solution to a live business problem. The take-home assignment guide covers the free-work question in more detail, and the same principles apply here.
What a strong plan contains
A strong 30-60-90 day plan usually shows most of these, whatever the role:
- Learning before changing. The first phase is about understanding the people, the work and the numbers, with a named way of doing it: which conversations, which data, which processes observed firsthand.
- Assumptions stated as assumptions. "I would expect renewal risk to sit in the mid-market accounts, and I would check that in the first two weeks" beats "the problem is mid-market churn."
- Checkable milestones. Each phase ends with something the hiring manager could verify on the day: a memo delivered, a process run solo, a metric baselined, a first result measured.
- Sequencing with reasons. The candidate explains why one thing comes before another, and what they would deliberately not do in the first 90 days.
- Named stakeholders. The plan identifies the people whose trust the role depends on, not just "build relationships."
- Role-specific substance. A finance manager's plan mentions the close; an engineering manager's mentions on-call and delivery; a sales plan mentions pipeline and ramp. Generic plans could be for any job.
- A view of their own risk. Strong candidates name what could go wrong in their own ramp and how they would notice.
Red flags
| Red flag | What it can suggest | How to test it in the Q&A |
|---|---|---|
| Major changes announced for the first 30 days | Acts before understanding; may break things that work for reasons they cannot see | "What would make you decide not to make that change?" |
| Every milestone is an activity ("meet the team," "learn the product") | Thinks in effort rather than outcomes | "How would I know on day 30 that this went well?" |
| Diagnosis of your business stated as fact from outside | Overconfidence, or not listening to the brief | Correct one assumption and watch how they adjust |
| The plan could be for any company | A template reused across applications, possibly generated without much thought | "Which part of this plan is specific to us, and why?" |
| A copy of what worked at their last company | May not adapt to a different context | "What is different here that would change this?" |
| No mention of the team or stakeholders | Sees the role as individual output even where it is not | "Whose support do you need most by day 60?" |
One red flag on its own is rarely decisive. A candidate who proposes an early change but explains a sensible condition for it in the discussion has answered the concern. Score the plan together with the conversation, not the slides alone.
Follow-up questions that separate rehearsal from thinking
The presentation is the prepared part. The questions afterwards are where you learn how the candidate thinks. Plan four or five of these in advance and ask them of every candidate:
- "If you could only achieve one thing in the first 90 days, which would it be, and why that one?"
- "Here is something about our situation you could not have known." Share one real fact. "What changes in your plan?"
- "What would tell you at day 30 that you were behind?"
- "Which part of this plan are you least sure about?"
- "Who would you meet in the first week, and what would you ask them?"
- "What have you left out on purpose?"
The second question matters most. A candidate who revises their plan thoughtfully in response to new information is showing the exact skill the first 90 days demand. One who defends the original plan against the new fact is showing you how they will handle the gap between their expectations and the real job.
The scoring rubric
Score each dimension from 1 to 4, using the anchors below. The format follows the approach in behavioral anchors for interview scores: each level describes what the interviewer saw or heard, so two interviewers watching the same presentation land on the same number.
| Dimension | 1 — Weak | 2 — Mixed | 3 — Strong | 4 — Exceptional |
|---|---|---|---|---|
| Learning approach | No learning phase, or changes proposed immediately | Learning phase exists but is generic ("get up to speed") | Names specific people, data and processes to learn from, before changing anything significant | As 3, and explains how the learning will shape later phases, with conditions that would change the plan |
| Specificity to the role | Could apply to any job | Mentions the role's main tasks but not its real challenges | Built around the role's actual systems, deliverables and metrics from the brief | As 3, and identifies a challenge in the role that the brief only hinted at |
| Checkable milestones | Activities only | Some milestones are checkable, most are not | Each phase ends with outcomes a manager could verify on the day | As 3, with leading indicators that would show early whether the plan is off track |
| Prioritization | Everything at once, no order | An order without reasons | Clear sequence with reasons, and an explicit list of what waits | As 3, and the candidate defends the tradeoff convincingly when pushed |
| Stakeholders | None named | "Build relationships" in general | Names the key relationships and what each needs from the role | As 3, and anticipates where stakeholder interests will conflict |
| Response to challenge | Defends the plan unchanged or abandons it entirely | Accepts the new fact but struggles to adjust | Adjusts the plan sensibly and explains why | Adjusts, and asks the question that reveals what else might be wrong |
Write a line of evidence next to every score: what the candidate said or showed that justifies it. "Said she would not change the pipeline stages until she had watched two full quarters of deals move through them" is evidence. "Seemed thoughtful" is not.
Capturing what the candidate actually said
The most useful evidence in a plan presentation usually comes in the questions afterwards, which is also when interviewers are busiest listening and least able to write. Agree before the interview who takes notes during the Q&A, and write the scores within an hour, while the answers are fresh. Tools that transcribe the conversation help here; Interview Signal, for example, drafts a scorecard where each score quotes the candidate's own words from the transcript, which keeps the debrief about what was said rather than how the presentation felt.
Adjust the bar for seniority
| Level | What a strong plan emphasizes |
|---|---|
| Individual contributor | Learning the tools and the work, first output reviewed, a first owned piece of work by day 90 |
| First-time manager | One-on-ones, team diagnosis, a first decision made with the manager's support |
| Experienced manager | Diagnosis across the team and its partners, a first improvement measured, a next-quarter plan |
| Executive | A structured listening tour, decision rights clarified, a forward plan, and restraint about early reorganization |
For role-specific examples of what the finished plan should contain, the role pages linked from the 30-60-90 day plan hub show concrete milestones for sales, engineering, product, finance, HR and other roles. They are a useful reference when writing the brief and calibrating the rubric.
Mistakes interviewers make
- Scoring the slides. Design quality mostly measures how much time the candidate had. Unless visual communication is part of the job, leave it off the score.
- Penalizing missing inside knowledge. The candidate cannot know your systems. Score how they plan to learn them.
- Rewarding similarity. A plan that matches what the interviewer would have done feels right but is not evidence of quality. The anchors help here.
- Letting the plan override the rest of the loop. A great presentation can create a halo over weaker interviews. Score each interview separately and discuss them together in the debrief, as covered in how to run a final round interview.
- Changing the brief between candidates. Once one candidate gets extra context or more time, the plans stop being comparable.
After the hire
The candidate you hire has already written a draft of their own onboarding plan. Use it. In the first week, sit down together, compare their plan with what they have now learned, and turn it into the real 30-60-90 day plan with milestones you both agree on. It saves time, and it tells the new hire that the work they did in the interview mattered.
Questions people ask
Should I ask every candidate for a 30-60-90 day plan?
Only for roles where planning and prioritizing across the first months is a real part of the job, which usually means managers, senior individual contributors and client-facing roles with a book of business. For roles with a structured ramp, the exercise mostly measures presentation skill and costs candidates time without telling you much.
How long should a candidate spend preparing a 30-60-90 day plan?
Say how long you expect, and keep it short: a few hours at most for most roles. Set a page or slide limit so candidates who have less spare time, because of a current job or caring responsibilities, are not competing against people who spent a weekend on it.
Is it a red flag if the candidate's plan gets our business wrong?
Not by itself. Candidates are working from public information and a short brief, so some wrong assumptions are expected. What matters is whether they labeled their assumptions as assumptions and how they respond when you correct one during the discussion.
How much should the 30-60-90 day plan count in the hiring decision?
Treat it as one piece of evidence for a few specific competencies, such as structured thinking, prioritization and learning approach, not as a pass or fail gate. Weight it alongside the other interviews on the scorecard rather than letting a polished presentation outweigh everything else.
Can we use the candidate's plan after we hire them?
Yes, as a starting draft for their real onboarding plan, which is a good use of the work. Using ideas from rejected candidates' plans is a different matter; keep the brief general enough that you are not asking for free consulting, and do not implement a rejected candidate's specific proposals as if they were your own.