Ruzora
Remote Teams

Engineering Onboarding Metrics: Time to 1st Commit

Time to first commit and ramp-up time are the two onboarding metrics worth tracking. Here are the benchmarks and how to measure them.

RE

CEO, Ruzora

Updated 7 min read

Time to first commit (TTFC) is the number of business days between a new engineer's start date and their first merged pull request. High-performing teams get there in 3 to 5 business days, and the industry median is 2 to 3 weeks (em-tools).

Pair it with one more number, time to full productivity, and you have the two engineering onboarding metrics that matter. Most orgs track neither. They 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 (Proxify); weak onboarding stretches that out.
  • 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.

What Is a Good Time to First Commit?

Time to first commit 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.

MilestoneStrong onboardingTypical
First commit3–5 days2–3 weeks
Full productivity8–12 weeks (Proxify)Longer
First owned feature~month 1month 2–3

How Do You Measure Time to First Commit and Ramp-Up Time?

You don't need a tool for this. A spreadsheet works.

1. Record two dates per hire: the start date and the merge date of their first meaningful pull request. Count business days, not calendar days, so a Monday start isn't punished for the weekend.

2. Define "meaningful" up front. A typo fix in the README doesn't count. A small bug fix or a scoped feature change that went through normal review does. Keep the definition the same for every hire or the numbers stop being comparable.

3. Note the blockers. Waiting four days for repo access or a VPN account is an onboarding bug, not a performance problem. Write it down next to the date.

4. Track ramp-up with milestones, not feelings. Time to first owned feature (about a month in a strong program) and time to working independently (around month three) are easier to agree on than "fully productive."

Review the sheet every quarter. Patterns show up fast: one team that always takes three weeks, or a setup step that stalls every hire. em-tools suggests five business days as a target that is ambitious but achievable for most teams, as long as it's used to fix the process and not to pressure the new hire (em-tools).

What Does a Slow Time to First Commit Mean?

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.

Does Onboarding Affect Retention?

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.

Frequently Asked Questions

What is time to first commit?

The business days between a new engineer's start date and their first merged, meaningful pull request. It's the earliest onboarding metric you can measure, and the easiest to fix.

What's a good time to first commit for a new engineer?

Strong teams get a new engineer's first commit in 3–5 business days; the industry median is about 2–3 weeks. Some teams with excellent developer tooling report one to two days.

How long is ramp-up time for a new software engineer?

With strong onboarding, 8–12 weeks to full productivity (Proxify). Without it, ramp-up runs longer, and a structured 30-60-90 plan is what closes that gap.

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.

Should you set a time to first commit target?

Yes, if you use it to find onboarding blockers. Five business days is a reasonable target for most teams. Don't use it to grade the new hire.

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.

Hiring your next engineer and want them shipping in week one? See vetted senior LATAM engineers, or tell us the role and get a vetted shortlist within 72 hours.

Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers.

RE

CEO, Ruzora

Roberto is the founder and CEO of Ruzora. He works directly with US startup founders and CTOs on staff-augmentation and software-factory engagements, and personally reviews senior engineer placements.

Senior LATAM engineers

Get a vetted shortlist within 72 hours.

Tell us the role and the stack. Within 72 hours you're reviewing a vetted shortlist of senior LATAM engineers who match it.