Skip to main content

📚 New Hire Onboarding Ladder

Get access, prove the local checks, ship a small reviewed change, then learn operations.

Day 1: access and local health​

  • Join the GitHub organization and engineering channel.
  • Get the minimum Firebase role needed for your work.
  • Do not receive admin access unless your role requires it.
  • Read the C4 model and one current ADR.
  • Run the checks for your primary repository.

For Flutter:

cd acesense-frontend
flutter pub get
flutter analyze --no-fatal-infos
flutter test
flutter run -d chrome

For Functions:

cd acesense-auth-function
pnpm install --frozen-lockfile
pnpm lint && pnpm test && pnpm build

Day 7: ship a bounded change​

Choose a change with one owner, a clear test, and a small rollback surface. Before merge:

  • Add or update the relevant test.
  • Update the owning documentation and last_verified only after checking it.
  • Run the repository's full relevant checks.
  • Have another engineer review security-sensitive or data-model changes.

Deploy only with explicit authorization and follow the deployment guide.

Day 30: own a surface​

  • Explain its data flow and authorization boundary.
  • Diagnose a representative failure from logs and state.
  • Know its deploy and rollback path.
  • Read the relevant runbooks and one postmortem.
  • Know which changes require an ADR.

GPU backend ownership has a separate onboarding path and is outside this verified checklist.

Manager checklist​

  • Grant least-privilege access, not blanket Editor/admin access by default.
  • Assign a buddy and a low-blast-radius first task.
  • Review the first production deploy together.
  • Add the engineer to on-call only after a supervised incident drill.