21 milestones · Week 1 + 30/60/90

Full-stack Engineer onboarding plan

What a strong ramp looks like for a new full-stack engineer. Week 1 universals + 30/60/90 day milestones, each with an accountable owner — manager, new hire, team, or HR.

TL;DR

A new Full-stack Engineer typically hits full ramp around Day 90. Week 1 is universal (workspace, tools, intro calls, first small win, plan review). Days 1-30 focus on context absorption, Days 31-60 on first owned outputs, and Days 61-90 on operating at full output. Per BambooHR's onboarding research, new hires with a structured 30/60/90 plan are 69% more likely to still be at the company three years later.

Glassdoor's research on bad hires puts the cost at ~30% of first-year salary when a new hire fails — most often because onboarding lacked owned milestones. Every item in the 21 milestones below has a named owner (Manager / New Hire / Team / HR), so accountability is explicit. Use this as your master Full-stack Engineer onboarding checklist; copy it into Notion, ClickUp, or whatever you use.

Week 1

Get them productive on tools, oriented to people, and clear on what success looks like in their first 90 days.

  1. 1Day 1: workspace + tooling set up before they arrive (laptop, accounts, Slack, email). New hire's first email should be 'everything just works.'Manager
  2. 2Day 1: 30-min welcome with their manager — share the team's mission, their first project, and book recurring 1:1s.Manager
  3. 3Day 1-2: meet & greet calls with 4-6 people they'll work with most. 15-20 min each, calendar-blocked in advance.Manager
  4. 4Day 3: have them ship something small (a Slack post, a document, a tiny PR) — confidence-building, momentum-setting.New hire
  5. 5Day 5: review the 30/60/90 plan together. New hire confirms it sounds achievable; manager confirms it's the right shape.Manager
  6. 6End of Week 1: HR / People check-in. Surface friction (access issues, missing context, mismatched expectations) early.HR

Days 1-30

Get both sides of the stack running. Ship a small full-stack PR.

  1. 1Local dev running with both API + frontend. Ship a small PR that touches both sides (a new field, a settings toggle).New hire
  2. 2Read both the API contract docs and the frontend state-management patterns. Identify the seams.New hire
  3. 3Pair with one backend specialist and one frontend specialist. Different mental models, useful contrast.New hire
  4. 4Take on one well-scoped full-stack feature (3-5 days). Spec, API endpoint, UI, test, ship.New hire
  5. 5Sit in on on-call rotation as shadow.New hire

Days 31-60

Own a feature start to finish. Get comfortable in both halves of prod.

  1. 1Own a multi-week full-stack feature from spec to ship.New hire
  2. 2Carry one primary on-call rotation across both API + frontend issues.New hire
  3. 3Review 8+ PRs across both halves of the stack.New hire
  4. 4Identify one cross-stack improvement (e.g., shared types between API + frontend, better error propagation).New hire
  5. 5Document one workflow that was unclear when you onboarded.New hire

Days 61-90

Operate at full output. Find work others miss (it usually lives at the seams).

  1. 1Operate at full output. Confirmed with manager + team.Manager
  2. 2Lead the design of one feature that crosses 2+ services or APIs.New hire
  3. 3Run one performance investigation that's cross-stack (e.g., perceived slowness — is it backend or frontend?).New hire
  4. 4Mentor next full-stack hire. Pair on their first full-stack PR.New hire
  5. 5Retro + onboarding-docs update.New hire

Hire a Full-stack Engineer worth onboarding.

The best 30/60/90 plan won't save a wrong hire. Raffi interviews every Full-stack Engineer applicant, scores them, and hands you the top 3-5. SaaS, $25 starter credit, no card.

Hire a Full-stack Engineer with Raffi — $25 credit →Interview questions for Full-stack Engineer

Onboarding plans for other roles

SDR (Sales Development Rep)Account ExecutiveCustomer Success ManagerBackend EngineerFrontend Engineer