Onboarding is the most under-measured process in most engineering orgs. Teams obsess over interview rubrics, then hand the hire a laptop and hope. If you can't say when a new engineer should ship their first commit, you can't tell whether onboarding is working.
Key Takeaways
- Industry median time to first commit is about 2–3 weeks; strong teams hit it in 3–5 business days (em-tools).
- Strong onboarding reaches full productivity in 8–12 weeks versus the typical 3–6 months (Proxify).
- A useful milestone model: ~80% productive by day 30, 90%+ by day 60, independent by month 3.
- Slow first commits usually signal documentation gaps, not a weak hire.
The Benchmarks Worth Tracking
Time to first commit (TTFC) is the cleanest early signal. The industry median is roughly 2–3 weeks, while high-performing teams get a new engineer's first commit in three to five business days. Past that, the milestone model is straightforward: a small feature shipped by month one, independent work by month three.
| Milestone | Strong onboarding | Typical |
|---|---|---|
| First commit | 3–5 days | 2–3 weeks |
| Full productivity | 8–12 weeks | 3–6 months (Proxify) |
| First owned feature | ~month 1 | month 2–3 |
What a Slow Start Actually Tells You
When a capable engineer takes a long time to their first commit, the problem is usually the environment, not the person: missing docs, an undocumented setup, or no clear first task. Treat a slow TTFC as a documentation and process bug to fix, which also speeds up every future hire.
Onboarding and Retention Are Linked
Onboarding does double duty: it ramps the engineer and it shapes whether they stay. A new engineer who ships quickly and feels effective in the first month is far more likely to stay, which ties straight back to why engineers quit and to developer experience. For distributed hires specifically, a structured first 90 days matters even more, which we cover in building a remote engineering team. See available engineers.
Frequently Asked Questions
What's a good time to first commit?
Strong teams get a new engineer's first commit in 3–5 business days; the industry median is about 2–3 weeks. It's the cleanest early onboarding signal.
How long until a new engineer is fully productive?
With strong onboarding, 8–12 weeks. Without it, the typical range is 3–6 months. Structured onboarding roughly halves the ramp.
What does a slow first commit mean?
Usually a documentation or setup gap, not a weak hire. Fix the environment and you speed up every future onboarding too.
The Bottom Line
Measure onboarding like you measure delivery. Track time to first commit and the 30-60-90 milestones, fix the documentation gaps a slow start reveals, and you ramp engineers faster and keep them longer.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers in 72 hours. See available engineers.
