# The 30-60-90 Day Plan Round, From Source Log to a Defended Page

*Decide whether to bring a plan, build one page where every line cites a source or a labeled assumption, and answer the probes hiring managers use to test it.*

- Canonical URL: https://www.refolk.ai/candidates/guides/30-60-90-day-plan-interview-round
- Pillar: Interviewing
- Format: Playbook
- Published: 2026-11-07
- Last reviewed: 2026-11-07
- Reading time: 22 min
- Keywords: 30 60 90 day plan for interview, how to present a 30 60 90 day plan in an interview, what would you do in your first 90 days interview answer, 30 60 90 day plan hiring manager round, should I bring a 30 60 90 day plan to an interview

## Key takeaways

- In Refolk's index, only 9 of 25 sampled US "Sales Manager" profiles held that exact title, against 22 of 25 for US Product Manager, so confirm span of control before you plan around a sales title.
- For a live hiring manager round, one page with two to four items per phase, spoken in 3 to 5 minutes, is the format that holds attention; 3 to 4 page plans suit a leave-behind the manager may never read.
- Every line in a 30-60-90 day plan should cite a logged source (posting, screen note, interviewer statement, or public filing) or an entry in a three-column assumptions register: assumption, evidence to seek, consequence if wrong.
- A 10-K's Item 1A risk factors describe the risks themselves, not how the company handles them, so a plan line sourced only to Item 1A belongs in the assumptions list.
- Write day-60 and day-90 targets against a day-30 baseline, because at least one hiring-side method turns the interview plan into committed onboarding goals and asks new hires to explain misses.
- The probe that decides the round is "What changes in your plan?", so rehearse revising the plan out loud more than you polish its design.

This playbook is for a candidate going into a final round where the hiring manager has asked for a 30-60-90 day plan, or might. A 30-60-90 day plan is a short document that sets out what you would learn, deliver, and own in your first 30, 60, and 90 days in the role. The guide runs the round in order: whether to bring one, a source log built from your own interview notes, a milestone test for each phase, a length gate, and a timed rehearsal of the challenge questions. When you finish, every line on the page traces to something you were told or sits in a labeled assumptions list.

## Should I bring a 30-60-90 day plan to an interview?

Bring one if it was requested, or if the role is management, senior, sales, or customer-facing, where requests are common. For most entry-level and mid-level roles, a clear verbal answer to "what would you do in your first 90 days" is enough, and a document nobody asked for can cost you.

The published advice disagrees, and you should know how much:

- **Bring it every time.** Career Confidential tells candidates to bring a plan to the first interview.
- **Bring it only when asked, or for senior or sales roles.** A candidate guide on careertestprep says to bring one only if the employer asks or the role is management, senior, or sales, and that a verbal answer is enough for most entry-level and mid-level interviews.
- **Unsolicited plans tend to hurt.** The Ask a Manager author wrote that unsolicited 30/60/90 plans usually weakened the candidates who brought them, because they were poorly done.

The weight of the evidence supports the middle position. One caution: the Ask a Manager finding is about poorly made plans. It doesn't say plans are bad in general. A well-sourced plan is a different object from the template-filled ones that drew that criticism.

> **Note:** The evidence here is thin
>
> No public data establishes how often plans are requested by role or seniority, and no published case covers junior or support roles specifically. If you are unsure, ask the recruiter directly whether the hiring manager expects a written plan in the final round.

Use this decision rule and write the result down with a one-line reason:

| Situation | Call |
|---|---|
| Plan requested | Build it; confirm delivery terms |
| Not requested; senior, sales, management, or customer-facing | Build it; offer it as a proposal |
| Not requested; entry or mid-level individual contributor | Skip the document; prepare the verbal answer from the same log |

Even if you skip the document, run the source log and the rehearsal sections below. The verbal answer needs the same inputs.

## What is the hiring manager actually grading in the plan round?

They are grading how you reason and revise when you only have partial information. They aren't grading whether you already know their systems. The polish of the slides tells them very little, and good interviewer guidance says so outright.

Interviewer Signal's guide for assessors, which scores plans on a four-level rubric, calls the plan "weak evidence for domain expertise, because the candidate does not know your systems." It also tells interviewers not to score the slides, because "design quality mostly measures how much time the candidate had." Its central probe is "What changes in your plan?" That is a question about revision. It isn't a question about content.

There is a second reason to take the content seriously anyway: the plan can outlive the interview. One hiring-side method, from the author of *Finding a Job Fast Using a 30/60/90 Day Plan*, treats the plan as "specific, measurable and actionable outcomes that this candidate will commit to achieving." During onboarding, the manager will "reconfirm the thirty, sixty and ninety day outcomes to which they have committed." If goals are missed, the scripted conversation opens: "Help me understand what led to your being unable to achieve the goal and plan you set for yourself." A new-hire check-in guide from Windmill asks at day 90: "Looking at your 30-60-90 plan, where did you land against it?"

So the round is graded on how you revise, and anything you write down can come back as a performance standard. Every rule in this guide follows from those two facts.

> Rehearse the revision, not the slides. The interviewer is grading how your plan changes when you learn something new.

## Which sources can a 30-60-90 plan line cite?

A plan line can cite four kinds of source: what interviewers said in this loop, your screen and recruiter notes, the job posting, and public company material. Anything else is an assumption and goes in a separate, labeled register.

#### Source strength for plan lines, strongest first

1. **Interviewer statements** - What the hiring manager and panel said in this loop, logged with name and date
2. **Screen and recruiter notes** - Answers to your questions about success and scope
3. **The job posting** - Phrases you can map directly into phase goals
4. **Public company material** - 10-K items and earnings-call quarters, public companies only
5. **Assumptions register** - Everything else, labeled, with evidence to seek and consequence if wrong

*A plan line is only as strong as the layer it cites, and anything below the public-material layer is an assumption, not a fact.*

### Ask what success looks like before you build

The strongest source is a direct answer to a question you asked. Fortune's advice: "During your initial phone screen, feel free to ask the hiring manager the critical ways they define success in that role." A Manager Tools forum thread suggests the hiring manager's assistant as another route when the manager is hard to reach. Log every answer with who said it and when.

Ask about scope as well as success, because a job title tells you less than you'd think. This matters most in sales.

**36% - Share of sampled US "Sales Manager" profiles that held that exact title**

In Refolk's index, 9 of 25 sampled US matches held the exact title, against 22 of 25 for US Product Manager.

In Refolk's index of professional profiles, a search for "Sales Manager" in the United States matches 276,564 profiles. Matching is inclusive, so it pulls in VP Sales titles. In a 25-profile sample, only 9 held the exact title. There were 4 CEOs and 10 VP-of-Sales variants.

| Title (US) | Matching profiles | Exact title in sample | VP or CXO in sample |
|---|---|---|---|
| Sales Manager | 276,564 | 9/25 | 14/25 |
| Product Manager | 67,414 | 22/25 | 0/25 |
| Ratio | 4.10x | | |

The same title also behaves differently across countries:

| Title | Country | Matching profiles | Exact title in sample of 25 |
|---|---|---|---|
| Sales Manager | United States | 276,564 | 9 (36%) |
| Sales Manager | United Kingdom | 54,862 | 16 (64%) |
| US/UK ratio | | 5.04x | |

What this proves is that "Sales Manager" covers everything from a single seller to a VP who runs a sales organization. It doesn't tell you this company's version. Before you write a single line, ask in the screen how many people would report to you and what number you would own. A day-60 milestone that assumes a team of eight looks naive if the role is a quota-carrying individual seat.

### Run the public-material pass

For a public company, two documents are worth the time. A 10-K is the annual report a public company files with the SEC, searchable through EDGAR at sec.gov.

- **Item 1A, risk factors.** This section is governed by Regulation S-K Item 105. The SEC's investor bulletin notes that companies generally list risk factors in order of importance, and that the section "focuses on the risks themselves, not how the company addresses those risks." A risk factor section longer than 15 pages must open with a bulleted summary, so start there.
- **MD&A.** MD&A stands for Management's Discussion and Analysis and is governed by S-K Item 303. It must cover liquidity and capital resources, results of operations, and critical accounting estimates.
- **The latest earnings call.** An earnings call is the quarterly call where executives present results and take analyst questions. It usually happens within a day or two of the 10-Q filing, and companies generally publish a transcript. One careers source notes that "analysts push executives harder than press releases do", so the Q&A section is the best public record of what leadership is being pressed on.

A focused review of a 10-K's key sections takes 30 to 45 minutes. One banker routine for an earnings call is a 45-minute read. Tag every resulting log entry with its Item number or quarter.

A private company has none of these documents. In that case the posting and your interview notes carry the whole plan, and the assumptions register will be longer. That's expected. Engineering blogs and published OKRs may help, but their usefulness isn't established. Log them as the weakest public source and confirm anything from them in the interview.

For the posting, map phrases into phases. One guide's example: "If the listing mentions 'improving client retention,' build that into your 90-day goal." If you applied through [Refolk](/candidates), the fit score against this posting already shows which requirements you match least. Those requirements are where days 1 to 30 should spend their learning time, and they're also where interviewers will probe.

## The 30-60-90 day plan procedure, step by step

Run these steps in order. Experis warns candidates not to start preparing the plan the night before the interview. Sourced time estimates exist only for the public-material reading, and they are given in that step.

#### From bring-or-skip to a defended page

1. **Make the bring-or-skip call** - Check whether the plan was requested and whether the role is management, senior, sales, or customer-facing. Write down a yes or no with a one-line reason.
2. **Ask what success looks like before building** - Use the screen, the recruiter, or the hiring manager's assistant to ask how success is defined and what scope the role carries. Log each answer with who said it and when.
3. **Build the source log** - Give every fact from the posting, screen notes, interviewer statements, and public material an ID, a source, and a date. You're done when no fact lacks either.
4. **Run the public-material pass** - For a public company, read the 10-K's key sections in 30 to 45 minutes and the latest earnings call transcript in about 45. Tag entries with Item number or quarter; for a private company, note that this layer does not exist.
5. **Draft two to four items per phase** - Write each phase with two to four lines, and tag every line with a log ID or an assumption ID. No line on the page goes untagged.
6. **Write the register and test each milestone** - Move unknowns into a three-column register: assumption, evidence to seek, consequence if wrong. Each phase must end in an outcome the manager could verify on that day without asking you, with a decision gate after day 30.
7. **Pass the length and format gate** - Cut to one page or 3 to 6 slides, spoken in 3 to 5 minutes, and confirm any delivery terms. A timed run-through must finish inside five minutes.
8. **Rehearse the challenge probes on a timer** - Answer the four standard probes out loud. Each answer names a trigger, a stop condition, or a revision, without notes.
9. **Deliver, take corrections, and keep it in the room** - Frame it as a proposal, walk it, then ask what you have wrong and log the corrections. Walk the whole page in the meeting; never leave it behind as a substitute.

The source log needs only five fields per row: ID (S1, S2, and so on), date, source type, who said it or where it appeared, and the fact in one line. Assumptions get their own IDs (A1, A2) in the register, which keeps the two kinds of claim apart on the page.

## How do I write milestones and assumptions that survive questioning?

End every phase in an outcome the manager could check on that day without asking you, and put every unknown in a three-column register. An activity like "meet stakeholders" isn't a milestone. "Shared a written diagnostic of the top three issues with my manager" is.

### The milestone test

A candidate guide on SlideUpLift flags "no measurable outcome by day 90" as a common failure and says to "end on a result, not an activity." Apply one test to each phase's last line: **could the manager verify it on day 30, 60, or 90 without asking you?** If the answer is no, rewrite it.

Handle numbers carefully. Interviewer guidance calls a claim like "increase revenue by 25% in 90 days" a red flag, and the hiring-side method above shows why: the number may come back as a commitment. One role template measures day-90 improvement "against the day-30 baseline." Use that structure. Day 30 establishes the baseline, and days 60 and 90 report movement against it.

After day 30, add a decision gate. A decision gate is a named review where you confirm priorities before committing to changes. PracHub's model wording: "After 30-day diagnostic, review findings with manager and senior stakeholders to validate priorities before proceeding to solution design in Days 31-60."

### The assumptions register

Manager Tools advises candidates to "state all of your assumptions AND point out areas which would require additional information." PracHub models the register with three columns: assumption at interview time, evidence to seek, and consequence if wrong. No source recommends a specific number of assumptions, so don't aim for a count. Every unsourced belief the plan depends on goes in the register.

> **Rule:** Every line cites something
>
> Each line on the page carries a source log ID or an assumption ID. A line with neither gets cut, or rewritten until it has one.

Use the matrix below to decide where each candidate line belongs. Base the decision on how big a change it proposes and how much evidence from your own loop backs it.

#### Where a proposed change belongs in the plan

Horizontal axis runs from Thin evidence from your loop to Strong evidence from your loop. Vertical axis runs from Small change to Large change.

| Quadrant | What it means |
| --- | --- |
| Large change, thin evidence | Move to the register and propose a day-30 decision gate instead |
| Large change, strong evidence | Keep, place after day 30, name a trigger and a stop condition |
| Small change, thin evidence | Turn it into a first-week question to ask |
| Small change, strong evidence | Keep as a plan line with its log ID |

*Large changes on thin evidence belong in the assumptions register behind a day-30 gate, not in the plan's first phase.*

Frame the whole document as a hypothesis. Phrasings documented in the sources include opening with "I put together a short draft of how I'd approach the first 90 days, based on what I've heard so far," starting lines with "I would expect to" or "I'd plan to," and titling the page a "30-60-90 Plan Proposal."

**One-page 30-60-90 plan proposal with assumptions register**

```
30-60-90 PLAN PROPOSAL: [Role], [Company]
Based on what I have heard so far. [S#] = source log entry. [A#] = assumption.

DAYS 1-30: Learn and set the baseline
- I'd plan to [action tied to what the hiring manager said] [S#]
- I'd plan to [action tied to a posting phrase] [S#]
- I would expect to [action resting on an unknown] [A#]
Day-30 milestone: [written outcome my manager can check without asking me, including the baseline figure]
Decision gate: review findings with [manager] and [named stakeholders] to confirm priorities before days 31-60.

DAYS 31-60: Contribute against confirmed priorities
- [action] [S#]
- [action] [S# or A#]
Day-60 milestone: [change measured against the day-30 baseline]

DAYS 61-90: Own a result
- [action] [S#]
- [action] [S# or A#]
Day-90 milestone: [result, stated relative to the day-30 baseline]

ASSUMPTIONS
ID | Assumption at interview time | Evidence to seek | Consequence if wrong
A1 | [belief] | [who or what would confirm it] | [which plan line changes]
A2 | [belief] | [who or what would confirm it] | [which plan line changes]
```

*Replace every bracket; keep the source and assumption IDs visible on the page you present.*

## How long should a 30-60-90 day plan be for an interview?

For a live hiring manager round, aim for one page with two to four items per phase, or 3 to 6 slides, spoken in 3 to 5 minutes. Longer formats exist, but they are built for a document the manager reads alone, and the evidence suggests that reading often doesn't happen.

| Source | Written limit | Slides | Spoken time |
|---|---|---|---|
| copilotinterview | 1 page | - | 3 to 5 min |
| Career Confidential / CFI | 1 page per phase | - | - |
| Fortune | 3 to 4 pages | - | - |
| SlideUpLift | 1 page | 3 to 6 live | - |
| jobs.ac.uk (via noxi) | - | 3 to 4 / 6 to 7 | 5 / 10 min |
| SlideEgg | - | 8 to 15 | 10 to 20 min |

The written limits run from one page to four, roughly a fourfold spread. The spread comes from different delivery modes, not real disagreement. Fortune's "A typical 90 day plan is 3-4 pages" describes a leave-behind document. The one-page and few-slide limits describe a live walk-through. AiPPT's "five to ten core slides" and Career Confidential's "one to three-page" range sit in between. Pick the format by how you'll deliver the plan, not by which template you found first.

For a live round, the copilotinterview limit is the one to obey: "More than one page, or more than five minutes spoken, and the manager stops listening." No source sets a split between presenting time and Q&A, so don't assume one. Ask the recruiter how long the slot is.

If the plan was requested, confirm the delivery terms: format, length, whether to send it ahead, and the deadline. In one Manager Tools forum case, the manager asked for the plan "1 day before our face to face interview." With that little notice, you can only meet the deadline if your source log already exists.

## How do I present the plan and answer the challenge questions?

Present it as a proposal in under five minutes, invite corrections, then answer the probes with a trigger, a stop condition, or a revision. The probes are predictable, so you can rehearse them on a timer before the round.

#### The plan walk-through in the room

1. **Frame** - Call it a proposal based on what you have heard so far
2. **Walk** - Two to four items per phase, 3 to 5 minutes total
3. **Invite corrections** - Ask what you have wrong before they tell you
4. **Take the probes** - Answer with the trigger, the stop condition, or the revision
5. **Close** - Log the corrections and confirm what you would change

*The walk-through takes under five minutes; the corrections and probes that follow are where the round is decided.*

The four probes from Interviewer Signal's evaluation guide:

1. "What would make you decide not to make that change?" Interviewers use this one against any major change announced for the first 30 days.
2. "What changes in your plan?" This asks you to revise in real time after hearing new information.
3. "What would tell you at day 30 that you were behind?" This tests whether your day-30 milestone is checkable.
4. "Who would you meet in the first week, and what would you ask them?" This tests whether your learning phase has names and questions in it, or only intentions.

Rehearse out loud. A written answer that reads well can still fall apart when spoken.

**Timed rehearsal script for the four plan probes**

```
PROBE 1: "What would make you decide not to make that change?"
The change: [plan line, ID]
What would trigger it: [evidence I would need to see, and where I would see it]
What would stop it: [the specific finding that would make me drop or delay it]

PROBE 2: "What changes in your plan?" (after they give new information)
What I heard: [their point]
Which line moves: [ID] from [phase] to [phase], or into the register as [A#]
What stays: [the line that still holds, and why]

PROBE 3: "What would tell you at day 30 that you were behind?"
My day-30 milestone: [outcome]
Behind looks like: [the observable miss]
What I would do: [the first correction, and who I would tell]

PROBE 4: "Who would you meet in the first week, and what would you ask them?"
1. [role or name] :: [question tied to A#]
2. [role or name] :: [question tied to A#]
3. [role or name] :: [question tied to A#]
```

*Fill one block per probe from your own plan; aim to answer each in about a minute, out loud, without notes.*

Probe 2 deserves the most practice. Have someone read your plan, then give you one fact that contradicts a line. Your answer should name the line by its ID and say where it moves. A candidate who can do that cleanly has shown the skill the round is testing.

Make sure the plan agrees with the resume you sent. If a plan line leans on experience the resume doesn't show, the interviewer will ask about it. Refolk keeps the tailored resume for each posting, so you can check the plan against the version this hiring manager actually read before you rehearse.

## How does a 30-60-90 plan go wrong?

Most failed plans fail in one of eight ways. Several of them look like strengths when you check them casually. For each one, below is what it looks like, why it misleads you, and the check that catches it.

1. **Bringing a plan nobody asked for.** Bringing a plan feels like a sign of enthusiasm, and that's the false positive: enthusiasm isn't the same as fit. The Ask a Manager author reported that unsolicited plans weakened candidates when they were poorly done. *Check:* was it requested, and is the role senior, sales, or management?
2. **Announcing changes in the first 30 days.** A bold first-month change reads as decisiveness. Interviewer Signal treats it as a red flag and answers it with "What would make you decide not to make that change?" *Check:* every change in days 1 to 30 has a named trigger and a stop condition, or it moves behind the day-30 gate.
3. **Activity milestones.** "Meet 10 stakeholders" looks concrete and passes a polish check, but it is an activity, not an outcome. *Check:* could the manager verify it on day 30 without asking you?
4. **Absolute numeric targets.** A hard number looks ambitious. Under the hiring-side method above, it becomes a commitment at onboarding, and you may have to explain why you missed it. *Check:* every target is expressed against a day-30 baseline.
5. **Over-reading risk factors.** A plan line citing the 10-K feels well researched. But Item 1A states risks, not how the company handles them. *Check:* does any line claim a company practice that is sourced only to Item 1A? If so, move it to the assumptions register.
6. **Being liked for similarity.** The interviewer may warm to your plan because it mirrors their own thinking. Interviewer Signal warns assessors that this isn't evidence of quality, and you shouldn't take it as evidence either. *Check:* does the plan contain at least one line the interviewer is likely to disagree with, and are you ready to defend it?
7. **Generic content.** A plan can be well structured and still say nothing specific. One candidate guide's test is whether the plan "could be copy-pasted into any other company's interview unchanged." *Check:* every line carries an ID from this loop's log.
8. **Leaving it behind.** Handing over a polished document feels thorough. One hiring-side author said plainly that the manager won't look at it after you've gone. *Check:* the agenda includes time to walk through it in the meeting.

A ninth failure applies to your research, not the page. Inclusive title matches inflate role counts. As the tables above show, the US "Sales Manager" pool includes CEOs and VPs. If you cite a market or pool size anywhere in your preparation, check the exact-title share first.

> **Watch out:** A polished plan can still fail
>
> Design quality mostly measures how much time you had. A plan with no sourced lines and no assumptions register fails the probes no matter how it looks.

## What to do after the round

Keep the source log, the register, and the corrections you collected. If you're hired, the plan becomes the starting point for your real onboarding plan, and you'll be measured against it.

Interviewer Signal's softer version of the hand-off asks the new hire to "compare their plan with what they have now learned, and turn it into the real 30-60-90 day plan." The stricter version reconfirms your committed outcomes. Either way, the corrections you logged in the room are the first edits. If you aren't hired, the log still has value. The success definitions and scope answers belong in your notes on that employer, and the format and rehearsal carry over to the next final round.

#### Before you walk into the round

- [ ] The bring-or-skip decision is written down with a one-line reason.
- [ ] Every fact in the source log has an ID, a source, and a date.
- [ ] You asked how success and scope are defined, and the answers are logged with who gave them.
- [ ] Every line on the page carries a source ID or an assumption ID.
- [ ] The assumptions register has all three columns filled for every entry.
- [ ] No plan line claims a company practice sourced only to 10-K Item 1A.
- [ ] Each phase ends in an outcome the manager could verify on that day without asking you.
- [ ] Day-60 and day-90 targets are stated against a day-30 baseline, not as absolute numbers.
- [ ] Any change in days 1 to 30 has a named trigger and a stop condition.
- [ ] The plan is one page or 3 to 6 slides, and a timed run-through finishes inside five minutes.
- [ ] You have answered all four probes out loud, including a live revision under probe 2.
- [ ] The meeting agenda includes time to walk through the plan in person.

## Frequently asked questions

### Should I bring a 30-60-90 day plan if the interviewer didn't ask for one?

Only if the role is management, senior, sales, or customer-facing, where requests are common; for most entry-level and mid-level roles a clear verbal answer is enough. Sources disagree: one career site says bring one to the first interview, while the Ask a Manager author found unsolicited plans usually weakened candidates because they were poorly done. If you bring one unasked, call it a proposal and offer it rather than pushing it onto the agenda.

### How long should a 30-60-90 day plan be for an interview?

For a live round, one page with two to four items per phase, spoken in 3 to 5 minutes, or 3 to 6 slides with one phase per slide. Published advice ranges up to 3 to 4 pages, but those longer formats are built for a document the manager reads alone. One guide warns that more than one page or more than five minutes spoken and the manager stops listening.

### What if I know almost nothing about the team's internal situation?

Put what you do not know in a labeled assumptions register and make your first 30 days a diagnostic with a decision gate. Interviewer guidance treats the plan as weak evidence of domain expertise because candidates cannot know internal systems, so missing inside knowledge is expected. What gets graded is whether you state assumptions plainly and say what evidence would change them.

### Should I put revenue or percentage targets in my plan?

Only relative to a baseline you will measure in the first 30 days, never as an absolute promise. A claim like increasing revenue by 25% in 90 days is flagged as a red flag in interviewer guidance. At least one hiring-side method reuses the interview plan as committed onboarding outcomes, so any number you write can come back as a performance standard.

### Should I leave a copy of the plan with the hiring manager?

Leaving a copy is fine as long as it isn't the main event. Walk the whole plan in the meeting. One hiring-side author put it bluntly: don't leave the plan to be looked at after you leave, because the manager won't read it. Book time in the agenda for the walk-through and the questions. If you send a copy afterward, keep it to the same one page you presented.

### How do I answer what would you do in your first 90 days without a written plan?

Use the same source log and give a spoken version: two or three moves per phase, each tied to something you heard in the process, ending in a day-90 outcome. Open by saying it is based on what you have heard so far, name one assumption you would test first, and say what you would do if it turned out wrong.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/30-60-90-day-plan-interview-round*
