Engineering onboarding redesign
The problem
New engineers were taking roughly six months to reach full productivity. Onboarding was ad hoc — a mix of shadowing, tribal knowledge, and scattered documents — so ramp time varied widely by manager and no one could see where a new hire actually stood.
How I diagnosed it
I mapped the existing path, interviewed managers and recent hires, and grouped what a productive engineer actually needs into distinct capability areas. The gap was structure: there was content, but no defined sequence, no checkpoints, and no shared definition of "ready."
The decisions
- Replace time-in-seat with tiered competency levels and a defined progression.
- Build structured pathways per role so every hire follows the same backbone.
- Make progress visible to managers instead of implicit.
What I built & how it rolled out
A four-tier pathway (Foundations → Core → Applied → Certified) with clear entry and exit criteria at each tier, delivered through the LMS with manager checkpoints. Piloted with one cohort, adjusted the sequence and checkpoints, then scaled across engineering.