Onboard a New Engineer

Build a 30-day onboarding plan for a new engineer.

Role: [Role]
Team and what it owns: [Team and What It Owns]
Their first project: [First Project]
Key people: [Key People]

Produce:

**Week 1 — Running code.** Environment set up, first trivial change shipped to production (however small), the 3 docs/systems worth reading FIRST and the ones to skip for now.

**Week 2 — Context.** The team's architecture in one diagram-worth of prose; pairing sessions with each key person, each with a stated purpose; the on-call/support rhythm.

**Weeks 3–4 — Real work.** Concrete milestones on [First Project] sized so they ship something reviewable each week; who reviews their work; the "you're doing fine" signals for THEM (not just the manager).

Rules:
- Every item is an action with a done-condition, not a topic ("Ship a docs fix via the full PR flow" not "Learn the PR flow").
- Front-load shipping over reading — one merged change teaches more than three wikis.
- Flag the two riskiest assumptions in this plan given what I've told you, so the manager can correct them early.