Before Day One

Set up accounts: email, Slack, GitHub, project management tools, cloud access. Prepare a welcome document: team members, meeting cadence, architecture overview, development setup guide. Assign an onboarding buddy — a peer (not the manager) who answers "dumb" questions without judgment. Order hardware and ship it early for remote hires. First impressions matter — a chaotic day one signals a chaotic organization.

First Week: Ship Something

Day 1: Welcome, team introductions, culture overview. Day 2: Development environment setup — this should take hours, not days. If setup takes more than a day, your docs are broken. Day 3-4: First PR — a small bug fix, typo correction, or minor feature. The specific task doesn't matter — shipping code in the first week builds confidence and signals belonging. Day 5: Architecture walkthrough with a senior engineer. The goal: the new hire feels productive and connected by Friday.

First Month: Build Context

Weeks 2-3: Pair program on a medium-sized feature with the buddy. Shadow on-call rotation (observe, don't respond). Attend all team meetings and ask questions. Read key architecture decision records (ADRs). Week 4: Own a feature end-to-end with minimal guidance. Have a 1:1 with the manager: "What's going well? What's confusing? What do you need?" By month end, the new hire should understand the codebase well enough to review PRs.

Essential Onboarding Docs

Setup guide: Step-by-step from zero to running code. Test it monthly — broken setup docs are the #1 onboarding complaint. Architecture overview: System diagram, key services, data flow. Team norms: PR size expectations, communication channels, meeting etiquette. Glossary: Domain-specific terms and acronyms. Decision log: Why we chose React, why we use PostgreSQL, why the API is structured this way. New hires need context for decisions, not just the decisions themselves.

The Buddy System

The buddy is not a mentor or manager — they're a safe person to ask questions. Buddy responsibilities: check in daily for the first 2 weeks, answer questions promptly, introduce the new hire to key people, share unwritten norms. Rotate buddies across hires to spread the load and build connections. Buddies should be compensated with reduced sprint commitments during onboarding periods. Being a good buddy is a skill — train people for it.

Remote Onboarding Specifics

Remote onboarding requires more intentional social connection. Schedule virtual coffee chats with 5-6 team members in the first 2 weeks. Use video for 1:1s — cameras on builds rapport. Create a dedicated Slack channel for the new hire's questions. Over-communicate — in remote settings, the new hire can't overhear conversations that provide context. Record architecture walkthroughs so they can be rewatched. Check in more frequently than you think necessary.

Measuring Onboarding Success

Time to first PR: Target: within 5 business days. Time to first solo feature: Target: within 4 weeks. 30/60/90 day surveys: "Do you understand the codebase? Do you feel productive? What's blocking you?" Retention: Good onboarding correlates with higher 1-year retention. Track these metrics and iterate on your process. Every new hire is an opportunity to improve onboarding documentation — have them update docs as they encounter gaps.