90 Day Plan for a Job Interview: What to Present and How to Structure It

8 min read ยท 2026-10-17

A 90 day plan for a job interview is a short document, one or two pages long, that shows what you would do in your first three months if you got the job. Split it into three blocks: days 1 to 30 to learn, days 31 to 60 to contribute, days 61 to 90 to deliver. Each block needs two or three goals the hiring manager can actually check.

The plan doesn't need to be right. It shows how you think. You can't know everything about the company from the outside, so the interviewer is watching three things: how well you understood the role, which questions you would ask first, and what result you would aim for by day 90. Below is a six-day roadmap to build and rehearse the plan. After it, you'll find what to write in each block and how to present it without reading it out loud.

The roadmap at a glance

Goal: Walk into the interview with a one or two page 90-day plan built around this specific role, and be able to present it in about five minutes. Duration: 6 days before the interview

  1. Research the Role and the Team (Days 1 to 2)

    Find out what the job is really for, so the plan answers the employer's needs and not general ones.

    • Reread the job posting and underline every verb that describes a result (launch, grow, reduce, build, fix).
    • Read the company's recent news, product pages, blog and leadership posts from the last few months.
    • Look up the hiring manager and future teammates on LinkedIn to see what they work on.
    • Write down the three problems you think this role was opened to solve.
    • List what you don't know yet. Those gaps become your first 30 days.

    Milestone: One page of notes with three likely priorities and five open questions.

  2. Draft Days 1 to 30: Learn (Day 3)

    Show that you'll listen and get up to speed fast without breaking anything.

    • Name the people you would meet in the first two weeks, by role (manager, peers, key internal clients).
    • List the tools, processes and data you would need to learn.
    • Add one small early win you could deliver by day 30, such as documenting a process or fixing one recurring issue.
    • Write one learning goal you could measure, like "can run the weekly report without help."

    Milestone: Three to four goals for the first month, each with a visible proof.

  3. Draft Days 31 to 60: Contribute (Days 3 to 4)

    Move from observing to doing real work with feedback.

    • Pick one of the three priorities from your research and turn it into a first project.
    • Plan a check-in with your manager to share what you've learned and adjust your goals.
    • Add a habit you would set up, such as a weekly update or a shared tracker.
    • Name one improvement you would suggest, and say it depends on what you learn in month one.

    Milestone: One owned project and one scheduled feedback point.

  4. Draft Days 61 to 90: Deliver (Day 4)

    Show the result the company gets for hiring you.

    • State the main result you'd aim for by day 90, in words the hiring manager uses.
    • Plan how you would measure it, using the measures the team already tracks.
    • Add a longer-term proposal for the next quarter.
    • Plan a 90-day review with your manager.

    Milestone: A clear day-90 outcome and the way it would be measured.

  5. Format It on One or Two Pages (Day 5)

    Make the plan easy to scan in under a minute.

    • Use three columns or three blocks with the same headings: focus, goals, how success is checked.
    • Keep each goal to one line. Cut every sentence that could fit any job.
    • Add a short header with the role title, your name and one line on your overall approach.
    • Print three copies and save a PDF you can send afterwards.

    Milestone: A clean document a stranger can understand in 60 seconds.

  6. Rehearse the Walkthrough (Day 6)

    Be ready to present it out loud, briefly, and to change it on the spot.

    • Practice a five-minute version and a one-minute version.
    • Prepare an answer for "what if your assumptions are wrong?"
    • Rehearse moving from the plan to a question for the interviewer.
    • Do one mock run with a friend who has never seen the plan.

    Milestone: You can explain the plan without looking at the paper.

What to Include in a 30-60-90 Day Plan for an Interview

The strongest plans use the same structure in every block, so the reader can compare months at a glance. For each 30-day block, write four short items.

Proof is the line that makes a goal checkable. "Meet the sales team" is an activity. "Shadow three sales calls and write down the top objections" is a goal with proof. Rewrite every goal until someone else could check whether it happened.

Adjust the balance to your level. For an entry-level role, the first block can lean heavily on training and learning, and the last block can stop at "handles the core tasks alone." For a senior or management role, the interviewer expects decisions by day 60 and a clear direction by day 90. Don't promise a reorganization of the team in month one, though. That suggests you haven't listened yet.

  • Focus: one word or phrase, such as learn, contribute, deliver.
  • Goals: two to four actions you would take, written as verbs.
  • People: who you would work with or report to during that block.
  • Proof: how you and your manager would know the block went well.

How to Turn Job Posting Phrases Into Plan Goals

Most candidates write the plan from memory of what a "good employee" does. A better method is to translate the job posting line by line. Take each responsibility in the posting and ask what it would look like in month one, two and three.

Here is an example for a marketing coordinator posting that says "manage the email newsletter and grow engagement".

Do this for the three biggest responsibilities and you already have most of your plan. The interviewer will recognize their own words, which shows you read the posting carefully. Every goal will also be tied to something the company already cares about.

  • Days 1 to 30: review the last ten newsletters, learn the email tool, and note which topics got the most replies or clicks according to the team's own reports.
  • Days 31 to 60: send the newsletter on your own with one test on subject lines or send time.
  • Days 61 to 90: share a short report on what the tests showed and propose a content calendar for the next quarter.

How to Present a 90-Day Plan in an Interview

Don't open with the plan. Wait for a natural moment, usually when they ask "how would you approach this role?", "what would you do first?" or "do you have any questions?" Then say you've put your thinking on paper and ask if they'd like to see it. Hand over a printed copy, or share your screen in a video interview.

Walk through it in this order.

The last two steps matter most. When the interviewer corrects one of your assumptions, you learn something real about the job and you look open to feedback. Take a note on your copy while they talk. If you get a follow-up round, bring a revised version that includes what they told you.

  • One sentence on your approach, for example "I'd spend the first month learning how the team works before changing anything."
  • One highlight per block, not every bullet point. Let them read the rest.
  • Your assumptions out loud, such as "I assumed the onboarding flow is the main priority. Is that right?"
  • A question to close, which turns the plan into a conversation about what the role really needs.

When to Bring a Plan and When to Skip It

A plan helps most in interviews for roles with clear results: sales, marketing, product, operations, project management and any management position. It's also useful in a final round, when the employer is choosing between a few strong candidates and wants to picture you in the job.

It's less useful in a first phone screen, which is usually short and focused on your background. Some interviews also follow a fixed set of questions with little room for documents. In those cases, keep the plan in your bag or a tab, and use its content in your answers anyway. If the employer asks for a presentation or a case study, your plan can become the backbone of it.

Common mistakes to avoid

  • Writing a generic plan that could fit any company, so replace every vague line with a goal tied to this employer's product, team or posting.
  • Promising big changes in the first month, so keep days 1 to 30 for learning and save proposals for the second and third blocks.
  • Filling three pages with dense text, so cut to one or two pages with one line per goal.
  • Inventing numbers or targets you can't know from outside, so describe how you would measure success and say you'd set the target with your manager.
  • Reading the document out loud during the interview, so present one highlight per block and let the interviewer read the rest.
  • Treating the plan as final, so ask the interviewer to correct your assumptions and update it before any next round.

Frequently asked questions

Should I bring a 90-day plan to a job interview?

Yes, if the role has clear results to deliver or if you're in a later round. Bring printed copies and offer it when the conversation turns to how you would approach the job. If the moment doesn't come, use its ideas in your answers instead.

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

One page is ideal and two pages is the maximum. The interviewer should be able to scan it in about a minute. Keep the details in your notes so you can talk about them if asked.

What is the difference between a 90-day plan and a 30-60-90 day plan?

They are usually the same document. A 30-60-90 day plan just splits the 90 days into three blocks of 30 days, each with its own focus. That split is what makes the plan easy to read and easy to discuss in an interview.

What if I don't know enough about the company to write a plan?

Write what you can from public information and label your guesses as assumptions. List the questions you'd answer in the first 30 days. A plan that shows how you would find the answers is still convincing, as long as it's clearly about this role.

Generate this roadmap with AI