md-pr-reviewShiftySlothe/demo-docs #42 — Add Q4 onboarding plan
Front matter
titleQ4 Onboarding Plan
ownerCharles Forson
statusdraft

Q4 Onboarding Plan

This plan describes how new hires ramp up during Q4, from day one paperwork through their first shipped change.

Timeline

  1. Week 1: orientation
  2. Week 2: first contributions
    • Pair on a small bug fix
    • Ship a one-line docs change
  3. 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

RoleResponsibilityOwner
ManagerWeekly 1:1sAlex
BuddyDaily check-ins (week 1)Priya
MentorCode review guidanceSam

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

  1. Rosetta is required for one legacy build tool; native support is tracked in INFRA-482. ↩