Onboarding
Day 1, first week, first month. Ship in week 1.
A new hire should ship something meaningful in week 1. This is the structured path that makes that real.
The first 24 hours (Day 1)
Section titled “The first 24 hours (Day 1)”The canonical hour-by-hour Day 1 plan lives in Day 1 Onboarding.
Quick reference of the Day 1 milestones:
| Hour | What happens |
|---|---|
| 0–1 | Laptop, accounts, name your sidekick |
| 1–2 | Start Here reading list (top 5 pages) |
| 2–4 | Clone the repo, run locally, see the app working |
| 4–6 | Identify first PR target (a small bug or doc fix) with your manager |
| 6–8 | Pair with manager on first PR |
Week 1 milestone
Section titled “Week 1 milestone”By Friday of week 1, you should have:
- Merged your first PR
- Written one wiki page (a runbook, a doc fix, or a session note)
- Attended your first weekly check-in
- Had 1:1s with everyone on the team (small enough that this is feasible)
Month 1 milestone
Section titled “Month 1 milestone”By end of month 1:
- Shipped a complete feature (planning → spec → PRs → ship → postmortem if any)
- Identified an area you want to own
- Started contributing to ADRs / RFCs in your area
Onboarding rituals
Section titled “Onboarding rituals”- Name the sidekick. Everyone names theirs. It’s a calmness ritual + a 30-Second-Rule reminder.
- Read the wiki. Start Here is mandatory in your first 2 hours.
- Write a session note. End of Day 1: a few paragraphs of what you learned, what surprised you. Goes in [sessions/].
Related
Section titled “Related”- Day 1 Onboarding — canonical hour-by-hour plan
- Start Here — first-hour reading list
- Org & Roles — who you’re working with
- Hiring — what we look for (the trajectory you’re now expected to live up to)