30-60-90 day plan template.

Add your role, pick three to five goals for each phase or write your own, and copy your plan.

First 30 days: Learn3 goals
Days 31 to 60: Contribute3 goals
Days 61 to 90: Lead3 goals
Your planAdd your job title and company
30-60-90 day plan: [Job title] at [Company] First 30 days: Learn - Meet my manager and agree what success looks like at 90 days - Have a one-on-one call with each person on the team - Set up my tools, accounts and access Days 31 to 60: Contribute - Take ownership of a first project and agree its deadline - Share a written summary of what I've learned and my first ideas - Meet the people in other teams I'll work with most Days 61 to 90: Lead - Deliver my first project and share the results - Propose goals for my next quarter, agreed with my manager - Work independently on my core responsibilities

Built in your browser from the goals you pick and write. Nothing is sent or saved.

How to write a 30-60-90 day plan

  1. Start from the job description. The responsibilities listed there are what your manager will judge you on.
  2. Learn first. The first 30 days are for people, tools and context. Big changes can wait.
  3. Contribute next.By day 60, own a first project and share what you've learned.
  4. Lead by day 90. Deliver, work independently, and propose goals for the next quarter.
  5. Agree it with your manager. Share the plan in your first week and review it at each stage.

Starting remotely? Pick the starter goals about overlap hours, written decisions and onboarding notes: they cover what an office would teach you without asking.

30-60-90 day plan examples by role

Example plans for common kinds of roles. Copy the goals that fit into the builder above.

When to use it: Software, data and other technical roles, where the first weeks go into the codebase and the deploy process.

First 30 days: Learn

  • Set up the development environment and ship a first small change
  • Read the architecture docs and the last few incident reviews
  • Pair with a teammate on a code review each week

Days 31 to 60: Contribute

  • Own a feature or bug-fix area end to end
  • Join the on-call or support rotation, if the team has one
  • Write down one gap in the documentation and fix it

Days 61 to 90: Lead

  • Deliver a project from design to release
  • Propose one technical improvement with a short written plan
  • Help onboard the next engineer who joins

What each phase is for

First 30 days: Learn

Meet people, set up tools, and agree what success looks like.

Days 31 to 60: Contribute

Own a first project, share early ideas, ask for feedback.

Days 61 to 90: Lead

Deliver results, work on your own, and set next quarter's goals.

Before your first day

Still interviewing? Prepare with the questions to ask the interviewer, and accept the offer in writing with the job offer response emails. At your first review, the self-evaluation phrases help you look back on the plan.

Frequently asked questions

What is a 30-60-90 day plan?

A short plan for your first three months in a new job: what you will learn in the first 30 days, where you will start contributing by day 60, and what you will own by day 90. It sets expectations with your manager.

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

It can help in a final round, especially for sales, management and senior roles. Keep it to one page, base it on what you learned in earlier interviews, and present it as a draft you'd refine with your manager.

How many goals should each phase have?

Three to five. Fewer can look thin, and more than five is hard to finish while you are still learning the job.

What goes in the first 30 days?

Learning: meeting the team, setting up tools and access, understanding the product, customers and metrics, and agreeing what success looks like with your manager.

How is a plan different for a remote job?

Add goals for things an office would give you for free: agreeing overlap hours across time zones, finding where decisions are written down, and setting a rhythm of written updates so your manager can see your progress.

Is the plan written by AI?

No. The starter goals are a fixed list written by our team, and the builder only arranges the goals you pick or type. Nothing is sent or saved.

Rather spend your time on interviews than on applications?

Auto-apply fills in the forms for remote jobs that match you. Let it send them, or check each one first.

Browse remote jobsLet auto-apply handle applications

Rotate your phone

RemoteSnipe works best in portrait. Please turn your device upright to continue.