Your first 90 days

Why it matters

Getting the job is the start, not the finish. The first three months shape how your team sees you and how fast you grow. Many new hires struggle not from lack of skill but from unclear expectations, hesitation to ask questions, or trying to prove themselves with big changes too early. A 30-60-90 day plan gives you structure, and some employers ask candidates to present one in the final interview.

The core idea: learn, contribute, own

A simple plan has three phases:

Each phase should include at least one measurable outcome so you and your manager can see progress.

Worked example: a junior software developer

Days 1–30

• Get the app running locally and ship one small bug fix (goal: first PR merged in week 2).
• Meet my manager, my onboarding buddy, the product manager, the designer and someone from support. Ask each: "What do you wish new people understood sooner?"
• Read the team's architecture notes and fix one thing that was out of date.

Days 31–60

• Own a small feature end to end with reviews (goal: shipped by day 60).
• Pair with a teammate on an incident or on-call shift to learn how production problems are handled.
• Write down three questions about the codebase and get them answered.

Days 61–90

• Lead a medium-size task, including the plan and the review with stakeholders.
• Review two teammates' pull requests per week.
• Present one small improvement (such as speeding up the test suite) with numbers.

Check-ins: a weekly one-to-one with my manager; review this plan at days 30, 60 and 90.

The same idea in other roles

• Data analyst: by day 30, know the main tables and definitions (what counts as an "active customer"?); by day 60, own a weekly report; by day 90, deliver an analysis that changes a decision.
• Cybersecurity or cloud engineer: shadow on-call and incident reviews, learn the runbooks, then own a hardening or automation task.
• UI/UX designer: learn the design system and research history, run a small usability test, then own a feature's design.
• IT project manager or systems analyst: map stakeholders, learn the delivery process, then run a small project or requirements effort.
• Technical trainer or CS teacher: observe sessions or classes, learn the curriculum and learners, then deliver and improve a module using feedback. New K-12 teachers usually also have induction or mentoring requirements set by their school or state.

Habits that help

• Ask good questions. Try first for a set time, then ask with what you tried. Keep a running list to batch questions for your one-to-one.
• Write things down. Notes on setup, decisions and terminology help you and the next new hire.
• Clarify expectations early. Ask your manager: "What would a great first 90 days look like for you?"
• Deliver small things reliably before proposing big changes. Trust comes from follow-through.
• Keep a brag document. Log what you did each week and its impact. You will need it for reviews.
• Look after yourself. Feeling overwhelmed in the first months is normal; it is not a sign you were the wrong hire.

Common mistakes

• Waiting to be told everything. Onboarding is often incomplete; take ownership of your learning.
• Suggesting a rewrite in week two before understanding why things are the way they are.
• Hiding mistakes. Report them early with what you know and what you are doing about it.
• Only talking to your own team. Relationships with neighbouring teams make work easier later.
• Ignoring the plan after writing it. Review it with your manager at each milestone.

Quick recap

• First 90 days: learn (1–30), contribute (31–60), own (61–90).
• Give each phase measurable outcomes and review them with your manager.
• Meet key people early, deliver small things reliably and write things down.
• Keep a brag document from day one.

Try it

Open the Do tab to write your own 30-60-90 day plan.