30-60-90 Day Plan for Job Interviews

You are in the final round. The hiring manager asks, "Can you walk us through your 30-60-90 day plan?"

Some candidates freeze. Some give generic answers. The candidates who get the offer present a specific, thoughtful plan that shows they have already mentally started the job.

A 30-60-90 day plan is one of the highest-leverage things you can prepare for senior interviews. Here is exactly how to build one that lands you the role.

What a 30-60-90 Day Plan Is#

A 30-60-90 day plan is your proposed roadmap for your first three months in the role. It outlines:

• Days 1-30: Learn and observe
• Days 31-60: Contribute and build relationships
• Days 61-90: Drive initiatives and show impact

When done well, it demonstrates:

• You understand the role's responsibilities
• You have thought about how to ramp up
• You will hit the ground running
• You think strategically, not just tactically
• You can structure complex thinking

When done badly, it shows:

• You did not research the company or role
• You will need a lot of hand-holding
• You think in vague generalities

When You Will Be Asked for One#

30-60-90 day plans come up in:

• Senior IC interviews (Staff, Principal, Director): often expected at the final round
• Manager and executive interviews: almost always required
• Sales roles: very common, especially for AE+ positions
• Customer Success leadership: standard
• Product Manager final rounds: increasingly common
• Marketing leadership: standard

Even if not directly asked, presenting one can differentiate you from other candidates.

The Framework#

Days 1-30: Learn and Listen

Goal: Build deep understanding of the company, team, customers, and current state.

What to include:

• Stakeholder meetings: 1:1s with manager, direct reports (if applicable), peers, key cross-functional partners
• Customer learning: review customer feedback, sit in on calls, read NPS results
• Documentation review: read internal docs, architecture documents, OKRs, post-mortems
• Process observation: shadow ongoing projects, attend team rituals
• Quick wins identification: find 1 to 2 small things to fix early

What NOT to include:

• Major changes or strategic pivots
• Aggressive deliverables
• Strong opinions about how things should change

Days 31-60: Contribute and Build

Goal: Start contributing meaningfully while continuing to learn.

What to include:

• First deliverables: ship something concrete (a feature, a process improvement, a hire)
• Relationship deepening: deeper conversations with key stakeholders, build trust
• Strategy formation: based on first 30 days of learning, propose initial directions
• Process improvements: identify 1 to 2 inefficiencies and propose fixes
• Team feedback: gather feedback from team on what to improve

What to be careful about:

• Pushing too hard before you understand the context
• Making sweeping changes
• Stepping on existing team members' toes

Days 61-90: Drive and Demonstrate

Goal: Show measurable impact and own meaningful work.

What to include:

• Strategic initiative: launch a project that moves a key metric
• Stakeholder alignment: present your 6-month vision to leadership
• Team development: invest in growing your team (if applicable)
• Cross-functional impact: influence beyond your immediate team
• Measurable results: specific metrics you want to move

By day 90, you should be fully operational. No more "still learning" excuses.

How to Prepare a Plan for a Specific Interview#

Step 1: Research the Company Deeply

Before drafting your plan:

• Read the company's last 4 quarterly earnings (if public)
• Review their blog, especially engineering and product posts
• Read their Glassdoor reviews (filter to senior employees)
• Check Crunchbase for recent funding and growth
• Find recent press coverage
• Look up the leadership team on LinkedIn

Spend at least 4 hours on company research.

Step 2: Understand the Role's Real Goals

The job description is a starting point, but real goals are deeper. Ask in earlier rounds:

• "What does success look like in this role at 6 months? 1 year?"
• "What are the team's top priorities for the next quarter?"
• "Who are the key stakeholders this role needs to work with?"
• "What is the biggest challenge facing the team right now?"

These questions give you the material for your plan.

Step 3: Identify Likely Quick Wins

Even from the outside, you can identify likely improvement areas. For example, for an Engineering Manager role:

• Is the deployment pipeline slow? (you can improve developer productivity)
• Is there frequent on-call burnout? (you can improve reliability)
• Are there unclear OKRs? (you can introduce structure)

For a Product Manager role:

• Is product discovery weak? (you can introduce customer interview programs)
• Are launches inconsistent? (you can build launch processes)
• Is data infrastructure weak? (you can champion better analytics)

Identify 3 to 5 specific quick wins. These signal you have real ideas.

Step 4: Draft the Plan

Use this template:

My 30-60-90 Day Plan for [Role] at [Company]

Days 1-30: Learn and Listen

Goals: Build deep understanding of [team/customers/product]. Establish relationships with key stakeholders. Identify quick win opportunities.

Key Activities:

• 1:1s with: [list specific people - manager, peers, cross-functional partners]
• Customer learning: [how you will learn about customers]
• Internal learning: [docs you will read, meetings you will attend]
• Observations: [what you want to understand]

Output: Synthesis of learnings, list of 3 to 5 quick win opportunities, proposed 60-90 day priorities.

Days 31-60: Contribute and Build

Goals: Ship first deliverables. Build trust with team. Refine strategic direction based on learnings.

Key Activities:

• Ship [specific quick win you identified]
• Lead [specific project or initiative]
• Build [specific relationship or process]
• Refine [strategy or roadmap]

Output: Initial deliverables shipped, proposed strategy reviewed with leadership.

Days 61-90: Drive and Demonstrate

Goals: Drive a strategic initiative end-to-end. Show measurable impact. Establish operating cadence.

Key Activities:

• Lead [strategic initiative tied to company priorities]
• Present [vision or strategy] to [leadership/team]
• Move [specific metric] by [target amount]
• Build [team capability or process]

Output: Measurable business impact, strategic alignment for the next quarter.

Sample 30-60-90 Plan: Engineering Manager Role#

Here is a real sample for an EM role at a Series C SaaS company:

Days 1-30: Learn and Listen

Goals: Build deep understanding of the team's technical landscape, customer needs, and operating model. Establish trust with 8 direct reports and key cross-functional partners.

Key Activities:

• 1:1s with all 8 engineers (45 min each)
• 1:1s with PM, design, and product partners
• Review last 6 months of post-mortems
• Sit in on 5 customer support calls
• Audit deployment process and on-call rotation
• Read engineering wiki and architecture decision records

Output: 5-page synthesis document covering team strengths, gaps, and recommendations. List of 3 quick wins.

Days 31-60: Contribute and Build

Goals: Ship one operational improvement. Begin coaching individual engineers. Help PM partners with technical scoping.

Key Activities:

• Implement new on-call schedule reducing weekend burden by 40%
• Pair with each engineer on coaching topics they identified
• Run technical design reviews for the team's 2 largest upcoming features
• Establish weekly tech debt review

Output: On-call satisfaction up. Two large features designed with input from team. Coaching plans for each engineer.

Days 61-90: Drive and Demonstrate

Goals: Drive a strategic technical initiative. Establish team metrics and rituals. Help recruit one new engineer.

Key Activities:

• Lead migration of legacy auth service to new identity platform (engineering OKR)
• Establish quarterly team OKRs and weekly metric review
• Conduct 6+ candidate interviews; hire 1 new engineer
• Present team vision to engineering leadership

Output: Auth migration in progress. Team operating with clear OKRs and rituals. 1 hire made.

How to Present Your Plan#

In an interview, you typically have 5 to 10 minutes to present. Format:

Option 1: Verbal Walkthrough (Most Common)

Walk through your plan section by section. Pause to invite questions. Be specific about activities and outcomes.

Option 2: Slide Deck (Some Senior Roles)

For executive interviews, prepare 5 to 7 slides:

• Slide 1: Title and your understanding of the role
• Slide 2: Days 1-30 plan
• Slide 3: Days 31-60 plan
• Slide 4: Days 61-90 plan
• Slide 5: Key metrics you would track
• Slide 6: Stakeholder map
• Slide 7: Open questions

Option 3: One-Pager (Some Interviews)

A printable PDF you bring to the interview. Useful for sales roles and customer success leadership.

Common Mistakes#

Mistake 1: Too Generic

A plan that could apply to any company at any role signals you did not do research.

Bad: "In month 1, I will learn the company and meet stakeholders."

Good: "In month 1, I will conduct 1:1s with [specific people], review your post-mortems from the last 2 quarters, and analyze your developer productivity metrics dashboard."

Mistake 2: Too Ambitious

Promising to launch 5 strategic initiatives in 90 days signals you do not understand how complex organizations work.

Be realistic. Ship 1 to 2 meaningful things, not 10.

Mistake 3: Too Cautious

Saying "I will only listen for 90 days before doing anything" signals lack of confidence and bias for action.

Senior roles expect you to start contributing by day 30 to 45.

Mistake 4: Ignoring Stakeholders

Plans focused only on individual contributor work miss the cross-functional nature of senior roles.

Include partners, customers, and leadership in your plan.

Mistake 5: No Metrics

Vague outcomes ("improve team productivity") are weaker than specific metrics ("reduce deployment time from 45 minutes to 10 minutes").

Use numbers wherever possible.

Mistake 6: Not Adapting Based on Interview Insights

If during the interview the hiring manager mentions a specific challenge, weave it into your plan answer.

Example: "Based on what you mentioned about the team's on-call burnout, in my first 30 days I would prioritize learning the current rotation and proposing improvements."

What to Do This Week#

If you have a senior interview coming up:

1. Research the company deeply (4+ hours)
2. Ask thoughtful questions in earlier rounds to gather info
3. Draft your 30-60-90 day plan (90 minutes)
4. Practice presenting it out loud (target 8 minutes)
5. Adapt based on what you learn through the interview process
6. Use our interview prep tools to rehearse

A great 30-60-90 day plan can be the deciding factor in a senior interview. Candidates who present specific, well-researched plans consistently outperform candidates who give generic answers.

Spend the time. Land the offer.