Onboarding
The goal: a new engineer ships something to production in week one and owns a real ticket in week two.
Before day 1 (lead's responsibility)
- Workspace email created
- GitLab account created at
gitlab.internal - Jira account added to the team's projects
- Slack account created and added to team channels
- Fingerprint registered for door access
- Buddy assigned (not the lead)
- First-week ticket picked: trivial change to a real codebase
Day 1
- Welcome chat with lead (30 min): team context, expectations, how we work
- Walkthrough with buddy (60 min): repos, services, dev environment
- Local dev environment running by EOD
- Read this playbook
- Read
conventional/source-structure.md- what a service looks like, what runs where, and the sharedaioz-commonlibrary. Written to be read cold on day one
Week 1
- Ship the pre-picked starter PR
- One-on-ones with each teammate (30 min each) — let them describe what they own
- Read recent ADRs and last 2 postmortems
Week 2
- Pick up a real ticket from the backlog — follow the full task workflow
- Pair with the domain owner on it
Month 1
- Lead a small project end-to-end (issue → implement → ship)
- First real code review given (not just received)
Month 2
- Write or co-author an ADR
- Take primary on-call (with secondary briefed and ready)
Month 3
- Fully ramped. Owns at least one domain (possibly co-owned).