Front matter
| title | Q4 Onboarding Plan |
| owner | Charles Forson |
| status | draft |
Q4 Onboarding Plan
This plan describes how new hires ramp up during Q4, from day one paperwork through their first shipped change.
Timeline
- Week 1: orientation
- Meet the team
- Set up local dev environment
- Read the engineering handbook
- Week 2: first contributions
- Pair on a small bug fix
- Ship a one-line docs change
- Week 3-4: first project
- Own a small feature end to end
Checklist
- Laptop provisioned
- Accounts created
- First PR merged
- Onboarding buddy assigned
Roles and responsibilities
| Role | Responsibility | Owner |
|---|---|---|
| Manager | Weekly 1:1s | Alex |
| Buddy | Daily check-ins (week 1) | Priya |
| Mentor | Code review guidance | Sam |
Ramp curve
The expected time-to-first-merge follows a fairly standard curve:
Process flow
graph TD;
A[Day 1: Orientation] --> B[Week 1: Environment setup];
B --> C[Week 2: First PR];
C --> D[Week 3-4: First project];
D --> E[30-day check-in];
Warning
Do not grant production access until the security training checklist is complete.
Local setup
Run the bootstrap script once your accounts are provisioned:
git clone git@github.com:example/monorepo.git
cd monorepo
./scripts/bootstrap.sh
Troubleshooting bootstrap failures
If bootstrap.sh fails on macOS with a permissions error, run chmod +x scripts/bootstrap.sh and try again. On an M-series Mac, make sure Rosetta is installed for the legacy toolchain1.
Further reading
See the platform team's runbook for on-call rotation details.
Footnotes
-
Rosetta is required for one legacy build tool; native support is tracked in INFRA-482. ↩