30 / 60 / 90
We measure onboarding by what a new hire ships, not what they read. Each milestone is a concrete, verifiable outcome.
timeline title Onboarding milestones Day 30 : Ship a small change through the full pipeline Day 60 : Own a feature end to end Day 90 : Run a QA cycle or a support rotation
What each milestone means per track
Section titled “What each milestone means per track”| Track | Day 30 — ship | Day 60 — own | Day 90 — run |
|---|---|---|---|
| Backend | Merge a small API change through review + CI to qa |
Own a feature: story to UAT sign-off | Lead a support rotation; triage + fix a production bug |
| Frontend | Ship an Angular/PrimeNG component change to qa |
Own a screen/feature end to end with the client demo | Handle a UAT round; own frontend expedite items |
| Mobile | Ship a small native change to a dev build | Own a feature across Android or iOS to UAT | Run a release candidate build + store-readiness pass |
| QA | Write + run test cases for one story | Own the QA gate for a feature end to end | Run a full QA cycle for a cadence, or a support rotation |
The through-line
Section titled “The through-line”flowchart LR A["Ship<br/>day 30"] --> B["Own<br/>day 60"] --> C["Run<br/>day 90"]
- Ship (30): proves the pipeline works for them — branch, PR, review, CI,
qa. See Branching & PRs. - Own (60): proves they can carry a work item from Ready to Done without hand-holding.
- Run (90): proves they can hold a gate or a rotation others depend on.
Requesting access for any of this: Tools & Access.
← Back: Day-1 Checklist