Career Strategy

First 90 Days at a Tech Company: The 30-60-90 Day Plan That Actually Works in 2026

By Blake Crosley · Last verified

Method note

The structural framework in this guide (the five transition types, the listening-tour mechanic, the IC-vs-management split) is drawn from Michael Watkins's The First 90 Days (Harvard Business School Press, 2003; revised 2013) and Genesis Advisers's published guidance. The tactical specifics (week-by-week cadence, specific stakeholder counts, weekly-digest format) are our editorial interpretation based on cross-company observations, not a direct quote from those sources. We have flagged the distinction inline where it matters.

In short

The first 90 days at a new tech-company role are about calibration, not output. The Watkins framework maps five distinct transition types and gives each its own onboarding shape. In our experience, the most common first-90-days mistake is treating the new role as a continuation of the previous one and applying rituals that were load-bearing elsewhere but read as foreign at the new company. Two related patterns we see often: shipping output before relationship credit, and skipping the listening tour because the answer feels obvious.

Key takeaways

  • Listen first, ship second. The first 30 days are spent identifying eight to twelve key stakeholders, scheduling 30-minute introductions, and asking three structured questions. The signal is the pattern across answers, not any single one. Per Watkins's Genesis Advisers, this is where transition success is decided.1
  • Match the transition type. Watkins names five (start-up, turnaround, accelerated growth, realignment, sustaining success). The plan that wins a turnaround mandate fails in a sustaining-success role, and vice versa. Diagnosis comes before prescription.1
  • Early wins should be visible to your skip-level when possible. A small ship in the first few weeks demonstrates production fluency; the stronger signal is when the value of the ship is obvious to leadership beyond your immediate team. Timing varies by role and team rhythm.
  • The manager 90-days plan differs from the IC plan. Managers spend the first 30 days listening to the team's existing rhythm; ICs spend it on technical onboarding. Will Larson's StaffEng notes that staff IC plans are closer to manager plans than to senior IC plans because the work is a force multiplier, not direct production.2
  • Pushback comes after credit, not before. Disagreement on direction in week one (absent a safety or production-stability issue) reads as arrogance even when correct. Build the relationship credit first.

The five Watkins transition types

The most-misapplied 30-60-90 plans are templates designed for one transition type but applied to a different one. Watkins's framework (genesisadvisers.com/the-first-90-days) names five distinct shapes:1

  • Start-up. Building from scratch. The mandate is to assemble the team, infrastructure, and operating cadence. Listening tour is short (there is little institutional history); execution is fast (every day delays revenue).
  • Turnaround. Visible dysfunction; the mandate is explicit and decision-making authority is up-front. Listening tour is brief and structured; the early-90-days move is to make a hard call quickly to demonstrate that the dysfunction is being addressed.
  • Accelerated growth. The product works; the org is doubling. The mandate is to scale operations without breaking what currently works. Listening tour identifies the load-bearing pieces of the existing rhythm; the trap is changing those.
  • Realignment. The org thinks things are fine; outside leadership disagrees. The mandate is to surface the gap before fixing it; the early-90-days move is data-collection to make the case for change.
  • Sustaining success. The role's predecessor was successful; the team is healthy. The mandate is to not break the system. Listening tour is long; visible early-ship pressure is low; the trap is wanting to make a mark.

Diagnosing the transition type is the week-one task. Ask the hiring manager directly: "Which of these five shapes is this?" The answer changes the plan.

Days 1-30: listen and orient

The 30-day phase is structured listening. Strong candidates treat this as a research project with deliverables; weak candidates treat it as a soft warm-up.

  1. Stakeholder map (week 1). Identify the eight to twelve people whose work intersects yours: skip-level, peers, downstream consumers of your team's output, upstream providers, the security, infra, design, data, and product partners. Write the map down explicitly so you can revisit it.
  2. Listening conversations (weeks 1-3). 30 minutes with each. Three structured questions. What do you wish a new hire in this role knew earlier. What is currently broken in our collaboration. What would make me successful in your view. Write what you heard within an hour of the meeting; otherwise the data degrades.
  3. Codebase / org observation (weeks 1-2 for IC, weeks 1-3 for manager). Read the production-readiness reviews, the postmortems, the recent design docs, the team's last quarterly OKRs. Take notes on what is load-bearing and what is residual. Names of the things will come later; understanding the shape is the goal.
  4. Small early ship (week 2 or 3 for IC). A documentation fix, a flaky-test repair, a tooling improvement. Proves production access, build fluency, and review discipline without claiming context you do not yet have.
  5. Weekly digest to manager (every Friday). What I learned this week. What I am still confused about. What I plan to do next week. The Friday digest is the calibration channel; do not skip it.

Days 30-60: contribute and validate

The 60-day phase is when the listening tour pays off. By day 30 you should be able to articulate the team's actual problem space (which differs from the on-paper problem space stated in the JD); by day 60 you should be contributing meaningfully to it.

  1. Articulate the actual problem space (day 30 deliverable). A one-page document. What this team actually does, what is going well, what is dysfunctional, what is load-bearing-but-imperfect, what is broken-and-no-one-cares. Share it with your manager; correct the calibration based on their reaction.
  2. Take ownership of one meaningful unit of work (days 30-45). Not the team's hardest project; not its easiest. Something where shipping it well demonstrates that you understood the listening-tour signal. Lara Hogan's Resilient Management framing is helpful here: trust is built through repeated competence demonstration, not heroics.3
  3. Map the relationships you need to invest in (day 45). Of the eight to twelve stakeholders, which two or three need ongoing investment, which two or three are load-bearing-but-currently-fine, which are background. Allocate 1:1 cadence accordingly.
  4. Form a hypothesis on the year-one plan (day 60 deliverable). Not a confident proposal; a hypothesis. Three things you think the team should commit to in year one, with the calibration risk on each one named explicitly. Share with your manager; iterate.

Days 60-90: propose and execute

The 90-day phase is when you ship the year-one plan. The plan is no longer speculative; it is grounded in 60 days of observation.

  1. Year-one plan document (days 60-75). Three to five commitments with success metrics. An explicit list of what you have decided NOT to do in year one and why. Partnership commitments to your stakeholder map (what you will do with each, what you need from each). Reviewed with manager and skip-level.
  2. First on-call rotation or first cross-team commitment (days 75-90 for IC). The transition from "new hire being onboarded" to "team member being depended on." For managers: the first hard people decision (a difficult feedback conversation, a scope adjustment, a hiring move).
  3. The 90-day retrospective (day 90). What I got right in my early calibration. What I got wrong. What I would do differently. Send to manager and skip-level. The retrospective is the artifact that distinguishes deliberate transition from drift.

Manager versus IC differences

The 30-60-90 plan shape differs materially between tech-IC and tech-management roles. Conflating them is the second-most-common first-week mistake.

  • IC plan. Heavy on technical onboarding. Codebase, deploy pipeline, on-call shadow, a small early ship. Day 30 to 60 contributes meaningfully to a project; day 60 to 90 takes ownership of an area. Year-one plan is technical: what you will design, what you will ship, what you will stop maintaining.
  • Senior IC plan. Half technical, half relationship. Same codebase work as IC, plus stakeholder mapping at the staff+ partnership layer. Year-one plan includes mentorship and design-review participation as scope.
  • Staff and principal IC plan. Closer to a manager's plan than a senior IC's. Per Will Larson's StaffEng, your work at L6+ is a force multiplier on other engineers; the early-90-days move is figuring out which fulcrums exist on this team and which are still being formed.2
  • Manager plan. Technical onboarding is light; team observation is heavy. Week one includes 1:1s with every direct, listening for the team's existing rhythm rather than imposing yours, identifying which dysfunctions you will and will not address in year one. Charity Majors's Engineer / Manager Pendulum framing is the canonical 2026 reference for the mindset shift.

Five common failure modes

  1. Treating the role as a continuation of the previous one. The single best signal of long-term success is whether the candidate explicitly recalibrated their working style to the new company in the first 60 days. The candidate who comes from a high-autonomy SaaS shop and assumes FAANG bureaucracy is dysfunctional rather than load-bearing struggles; the candidate who comes from FAANG and assumes the new SaaS startup will adopt their rituals struggles. Watkins paraphrases this risk: repeating what got you hired in a context where it no longer applies.1
  2. Pushing back on direction before building credit. Disagreement that ignores institutional history reads as arrogance even when correct. Build the relationship credit first; spend it later.
  3. Shipping output before listening. The candidate who refactors a piece of the codebase in week two without understanding why the original shape exists is the candidate who has to undo the refactor in month four.
  4. Skipping the year-one not-doing list. The strongest day-90 signal is naming what you have decided NOT to address in year one. Without that, scope creep is structural, not avoidable.
  5. Treating onboarding as a checklist rather than calibration. The plan exists to give you a structured way to ask the right questions. Mechanical execution of a generic 30-60-90 template tells the org that you did not adjust to the actual situation.

Common questions

Should I actually write a 30-60-90 day plan when starting a new tech-company role?

Yes for tech-management and staff+ IC roles; optional for senior IC and below. The plan is less about checking boxes and more about giving you a structured way to ask the right questions during onboarding. Watkins's framework, codified at Genesis Advisers (the consultancy founded around the book), maps five transition types: start-up, turnaround, accelerated growth, realignment, sustaining success. The plan you write differs by transition type. A standardized 30-60-90 template applied to a turnaround when the actual transition is a sustaining-success role is the most common first-week mistake.

What is the single most important early-90-days activity at a tech company?

Relationship mapping. The first 30 days are spent identifying the eight to twelve people whose work intersects yours, scheduling 30-minute introductory conversations with each, and explicitly asking three questions: what you wish a new hire in this role knew earlier, what is currently broken in our collaboration, what would make me successful in your view. The signal is not the answers; it is the pattern across answers. Lara Hogan's Resilient Management framing of trust-building as 1:1 cadence and repeated competence demonstration is the canonical 2026 reference.

Should I ship code in the first 30 days as an engineer?

Yes, even if it is small. The early-win pattern at FAANG-tier and SaaS-tier engineering orgs is: a small visible commit in week one or two (a documentation fix, a flaky-test repair, a tooling improvement) demonstrates production access, build fluency, and review discipline. The strong signal is that you submitted a PR, took review feedback graciously, and shipped without breaking anything; the weak signal is shipping a feature that misreads the codebase architecture because you did not spend the first two weeks reading. The senior+ version of this principle: an early win is one whose value is obvious to your skip-level, not just your team.

How does the 30-60-90 day plan differ for a tech manager versus a tech IC?

Materially. A new IC's plan is dominated by technical onboarding (codebase, deploy pipeline, on-call rotation, a small early ship). A new manager's plan is dominated by team observation: 1:1s with every direct in week one, listening for the team's existing rhythm rather than imposing yours, identifying which team-level dysfunctions you will and will not address in year one. Will Larson's StaffEng notes the parallel for staff IC: your 90-day plan is closer to a manager's than to a senior IC's because your work is a force multiplier on other engineers, not direct production. Charity Majors's Engineer / Manager Pendulum framing applies here: the manager-mindset entry shape is different from the IC-mindset entry shape.

When is it OK to push back on direction during the first 90 days?

Day 1 if there is a safety or production-stability issue. Day 30 to 90 for everything else. The Watkins framing: in the early window your judgment is undercalibrated to the team's history; disagreement that ignores history reads as arrogance even when correct. Build the relationship credit (small ships, demonstrated competence, evidence you understood the room) before you spend it on direction-level pushback. The exception: if you were hired specifically to drive a turnaround, the explicit mandate is the relationship credit; skipping the listening tour is the failure mode.

What is the most common 30-60-90 day failure mode at FAANG-tier?

Treating the role as a continuation of the previous one. The single best signal of long-term success in exit-interview data from new-hire-success programs is whether the candidate explicitly recalibrated their working style to the new company in the first 60 days. The candidate who comes from a high-autonomy SaaS shop and assumes FAANG bureaucracy is dysfunctional rather than load-bearing struggles; the candidate who comes from FAANG and assumes the new SaaS startup will adopt their rituals struggles. Watkins paraphrases this risk: repeating what got you hired in a context where it no longer applies.

How do I write a 30-60-90 day plan during the interview process?

Recruiters and hiring managers at staff+ and manager-track interviews increasingly ask for one. The right shape: 30 days is listen and learn (named stakeholders, codebase or org observation, explicit non-actions). 60 days is contribute and validate hypotheses (small early win, narrowed plan based on what you found in 30 days). 90 days is propose and execute (documented plan with success metrics for year one, partnership commitments, an explicit list of items you have decided NOT to address in year one). The interview-stage plan is necessarily speculative; the strong signal is that you named the calibration risk (these are my hypotheses, here is how I will validate them) rather than presenting it as a confident roadmap.

Sources

  1. Genesis Advisers, The First 90 Days framework (Michael D. Watkins). The author-maintained consultancy site for The First 90 Days (Harvard Business School Press, 2003; revised and expanded 2013). Codifies the five transition types (start-up, turnaround, accelerated growth, realignment, sustaining success) and the calibration-before-execution sequencing that defines the framework.
  2. Will Larson, StaffEng (2021). The canonical 2024-2026 reference for the staff+ IC track at FAANG-tier and SaaS-tier. Larson's framing of staff work as a force multiplier on other engineers (rather than direct production) shapes how the staff IC 30-60-90 plan differs from the senior IC plan.
  3. Lara Hogan, Resilient Management. Author-maintained landing page for the canonical 2026 reference on engineering management practice; trust-building through 1:1 cadence and repeated competence demonstration is the framing the relationship-mapping work draws from.
  4. Harvard Business Review. Editorial and applied management research. Watkins's First 90 Days articles, Heidi Grant's onboarding research, and the broader HBR archive on transitions are the supporting evidence base for the framework.
  5. Marty Cagan, Silicon Valley Product Group. Cagan's writing on autonomous product teams and the IC-vs-management decision shapes the product-side equivalent of the framework, particularly relevant to product-manager and design-manager 30-60-90 plans.

The 30-60-90 day plan applies across every role. Pair with the role-specific level guide on:

  • Engineering Manager: line-manager through senior-director; how the manager transition shape evolves with scope.
  • Design Manager: the design-leadership equivalent; how the IC-to-manager transition differs in design orgs.
  • Product Manager: APM through principal; the partnership-mapping work that PM transitions specifically require.
  • Software Engineer: junior through staff and principal; the technical onboarding shape that IC plans depend on.
  • DevOps / SRE Engineer: production-readiness and on-call onboarding; the SRE transition includes a structured handoff of on-call ownership.
  • Salary Negotiation Guide: the conversation that precedes the first 90 days.
  • System Design Interview Guide: the interview round that decides whether you get to write the 30-60-90 plan in the first place.