Intermediate
Vocabulary
#onboarding
#time-to-first-pr
#ramp-up
Developer Onboarding Metrics Vocabulary
5 exercises — the language of developer onboarding metrics: time to first PR, time to first production deploy, ramp-up period, and friction language.
Key onboarding metrics
- Time to first PR — days from start date to first pull request; proxy for setup friction
- Time to first production deploy — days until first ship to production; measures pipeline confidence
- Ramp-up period — time until developer reaches defined output threshold (e.g. 75% of team median)
- Onboarding friction — any barrier slowing new developers: broken scripts, stale docs, unclear ownership
- ROI formula — weeks saved × engineers hired = engineer-weeks recovered → £ value
0 / 25 completed
1 / 25
A DX lead presents onboarding improvements to the VP of Engineering: "Before the platform changes, our time to first PR was 11 days. We have reduced it to 3 days."
What does "time to first PR" measure, and why is it a valuable onboarding metric?
What does "time to first PR" measure, and why is it a valuable onboarding metric?
Time to first PR measures how many days pass between a new hire's start date and their first pull request. It is a powerful onboarding metric because: (1) it is objective and automatically measurable via the version control system; (2) it exposes friction in the setup chain — local environment, access permissions, documentation clarity, toolchain install time; (3) it is a leading indicator of ramp-up velocity — new hires who open a first PR within 3 days onboard 40-60% faster on average (per DX research). A 3-day target requires: working local dev environment in < 1 hour, clear first-task documentation, a good "good first issue" backlog. In presentations: "Reducing time to first PR from 11 days to 3 days means new engineers are contributing 8 days earlier — significant at scale."
2 / 25
An engineering manager explains an onboarding initiative: "We also track time to first production deploy — separate from time to first PR — because shipping to production requires additional access, understanding of the deploy pipeline, and confidence in the process."
Why is "time to first production deploy" a different and complementary metric to "time to first PR"?
Why is "time to first production deploy" a different and complementary metric to "time to first PR"?
Time to first production deploy and time to first PR measure different stages of the onboarding journey. A developer might open a first PR on day 3 (good!) but not deploy to production until day 30 because: (1) production access requires a security review; (2) the deploy process is undocumented or complex; (3) they lack confidence and are waiting for a mentor; (4) the staging-to-production promotion workflow is opaque. The gap between the two metrics identifies where the second phase of onboarding friction lives. A healthy pattern: first PR by day 3, first production deploy by day 7-10. A gap of 3+ weeks signals deploy-pipeline documentation or access-provisioning problems. In DX reporting: "Time to first PR is 3 days; time to first production deploy is 28 days — the 25-day gap indicates our production access and deploy documentation needs urgent improvement."
3 / 25
A platform team proposes measuring the ramp-up period as an onboarding KPI. A senior engineer asks: "How do you define when a developer is 'fully ramped up'? That seems subjective."
Which definition of ramp-up period is most measurable and defensible in a DX programme?
Which definition of ramp-up period is most measurable and defensible in a DX programme?
A ramp-up period is most defensible when defined by measurable output thresholds rather than time or subjective judgement. Option C uses a quantitative benchmark: PR throughput and review participation at 70-80% of team median for two consecutive weeks. This approach: (1) is objective and measurable from existing data; (2) accounts for individual variation — some engineers ramp in 4 weeks, others in 12; (3) identifies stalled ramp-ups early, triggering intervention before 90 days; (4) creates a feedback loop between onboarding investments and their outcomes. Alternative measurable definitions include: "steady deployment frequency for 4 consecutive weeks" or "independent PR review with no escalation for 2 weeks." In DX vocabulary: "We define full ramp-up as reaching 75% of team median PR throughput — our median ramp-up period improved from 11 weeks to 6 weeks after the onboarding programme."
4 / 25
A developer experience researcher identifies patterns in onboarding exit surveys: "The top three sources of onboarding friction reported by new joiners are: (1) broken local setup scripts, (2) outdated documentation, and (3) unclear ownership of who to ask for help."
Which metric best captures the aggregate impact of these friction sources?
Which metric best captures the aggregate impact of these friction sources?
Time to first PR is the best single aggregating metric for onboarding friction because it is directly downstream of all three cited sources: (1) a broken local setup script prevents the developer from running the project → delays first PR; (2) outdated documentation means the developer cannot follow the setup guide → delays first PR; (3) unclear ownership means the developer spends hours waiting for someone to help unblock them → delays first PR. The metric does not tell you why it is slow (you need exit survey data for that), but it reliably signals that friction exists and quantifies its total cost. This is why time to first PR is the cornerstone onboarding metric: it is objective, automatically measurable, and sensitive to all major friction categories. To diagnose the cause, combine it with qualitative data from onboarding exit surveys or friction logs.
5 / 25
An engineering director presents onboarding improvements to the board: "We hired 20 engineers last quarter. By reducing onboarding friction, we reduced the average ramp-up period from 10 weeks to 6 weeks — a saving of 4 weeks per engineer."
Which statement best translates this improvement into a business outcome the board can evaluate?
Which statement best translates this improvement into a business outcome the board can evaluate?
Option C applies the DX ROI multiplication formula to onboarding: (1) per-person saving: 4 weeks per engineer; (2) team multiplier: × 20 engineers = 80 engineer-weeks; (3) business translation: 80 weeks ≈ 1.5 FTEs for a quarter, valued at £90K (assuming £60K annual salary = £1,125/week × 80). This is the exact framing boards respond to — it converts an HR/DX metric into financial and capacity terms. Option A is a satisfaction score (good supporting data but not board-primary). Option B is an activity metric (documents written) without outcome translation. Option D is anecdotal. The pattern for all onboarding ROI presentations: "N engineers × W weeks saved = total engineer-weeks recovered = £X in engineering capacity, delivered by a programme that cost £Y."
6 / 25
PR#1234 has a comment from @reviewer: 'This looks good overall, but the error handling needs to be more robust. Consider adding logging and retry mechanisms.' After reviewing this PR, a new developer, Sarah, spent 8 hours implementing these changes. Which of the following metrics *most* accurately reflects the efficiency of Sarah's onboarding experience in addressing this specific feedback? While line count and feedback severity offer *some* context, the most accurate measure of onboarding efficiency is directly tied to how effectively a new developer addresses specific feedback. Sarah's total time spent on the PR – including revisions and communication – provides a tangible metric for evaluating the onboarding process's ability to equip developers with the skills to handle common review comments. Focusing solely on code changes or feedback severity obscures the crucial element of learning and adapting within the context of a collaborative development workflow.
7 / 25
PR#5678 has a comment from @lead_engineer: 'The API response format is inconsistent with the documentation. Ensure consistent use of JSON schema validation and clear error codes.' After reviewing this PR and attempting to integrate it into their project, Ben spent 12 hours refactoring his code to align with these requirements. Which metric provides the *most* granular insight into the effectiveness of the onboarding process in addressing this specific technical challenge? While all options relate to onboarding metrics, the question specifically asks for insight into *this* particular challenge – API integration and adherence to documentation. Option 3 directly measures how often developers are seeking clarification on a specific technical aspect during onboarding, which is the most focused metric for understanding that experience. Options A & B offer broader views of code review efficiency and successful integrations, while option C focuses on a different type of feedback.
8 / 25
PR#9012 has a comment from @senior_dev: 'The code style is inconsistent with our team's conventions. Please adhere to the established naming standards and formatting guidelines.' Following this feedback, David spent 3 hours reformatting his entire module to comply with these requirements. Which metric most accurately reflects the impact of this stylistic feedback on David's onboarding experience? The correct answer is High technical debt. The comment highlights a significant issue – inconsistent code style – which directly contributes to increased effort and rework. While the other options could be contributing factors, the core problem identified in the comment centers around the level of established standards and the impact on David's work. Misconceptions might include thinking low complexity or insufficient training were primary drivers; these are secondary issues that can arise from poor adherence to conventions.
9 / 25
During a Slack conversation about onboarding metrics, Alex writes: 'I'm seeing a high rate of initial bug reports on PRs. It's costing us time and slowing down the team.' Liam responds: 'Let's track the number of critical bugs found in the first 7 days after a developer's PR is merged. That gives us a good signal about how well they're grasping core concepts and best practices.' What does Liam primarily intend to measure with this metric?
Liam is focusing on 'early bug incidence,' which directly addresses Alex's concern about frequent initial issues. Tracking this metric – the number of critical bugs in the first week after PR merge – provides a clear indication of whether developers are understanding and applying fundamental principles during their early contributions. This contrasts with measuring code quality or documentation effectiveness, which are broader metrics; velocity focuses on output rather than quality.
10 / 25
A developer experience analyst is presenting a report to the engineering leadership team. The report highlights that new developers take an average of 3 weeks to complete their first major feature and consistently rate the documentation as 'unhelpful' in their onboarding surveys. Which metric, when combined with the documentation feedback, offers the *most* actionable insight into identifying areas for improvement within the onboarding process?
While all options represent potential data points, the core issue is 'unhelpful' documentation. Tracking time spent searching internal knowledge bases directly correlates with that pain point and provides a measurable indication of how effectively information is being delivered. The other options – code review volume, overwhelmed feelings, or lines of code – are tangential and don't directly address the documented problem with the onboarding documentation itself. This allows for targeted improvements to the documentation resources.
11 / 25
PR#1234 has a comment from @reviewer: 'This looks good overall, but the error handling needs to be more robust. Consider adding logging and retry mechanisms.' After reviewing this PR, a new developer, Sarah, spent 8 hours implementing these changes. Which of the following metrics *most* accurately reflects the efficiency of Sarah's onboarding experience in addressing this specific feedback? While line count and feedback severity offer *some* context, the most accurate measure of onboarding efficiency is directly tied to how effectively a new developer addresses specific feedback. Sarah's total time spent on the PR – including revisions and communication – provides a tangible metric for evaluating the onboarding process's ability to equip developers with the skills to handle common review comments. Focusing solely on code changes or feedback severity obscures the crucial element of learning and adapting within the context of a collaborative development workflow.
12 / 25
PR#5678 has a comment from @lead_engineer: 'The API response format is inconsistent with the documentation. Ensure consistent use of JSON schema validation and clear error codes.' After reviewing this PR and attempting to integrate it into their project, Ben spent 12 hours refactoring his code to align with these requirements. Which metric provides the *most* granular insight into the effectiveness of the onboarding process in addressing this specific technical challenge? While all options relate to onboarding metrics, the question specifically asks for insight into *this* particular challenge – API integration and adherence to documentation. Option 3 directly measures how often developers are seeking clarification on a specific technical aspect during onboarding, which is the most focused metric for understanding that experience. Options A & B offer broader views of code review efficiency and successful integrations, while option C focuses on a different type of feedback.
13 / 25
PR#9012 has a comment from @senior_dev: 'The code style is inconsistent with our team's conventions. Please adhere to the established naming standards and formatting guidelines.' Following this feedback, David spent 3 hours reformatting his entire module to comply with these requirements. Which metric most accurately reflects the impact of this stylistic feedback on David's onboarding experience? The correct answer is High technical debt. The comment highlights a significant issue – inconsistent code style – which directly contributes to increased effort and rework. While the other options could be contributing factors, the core problem identified in the comment centers around the level of established standards and the impact on David's work. Misconceptions might include thinking low complexity or insufficient training were primary drivers; these are secondary issues that can arise from poor adherence to conventions.
14 / 25
During a Slack conversation about onboarding metrics, Alex writes: 'I'm seeing a high rate of initial bug reports on PRs. It's costing us time and slowing down the team.' Liam responds: 'Let's track the number of critical bugs found in the first 7 days after a developer's PR is merged. That gives us a good signal about how well they're grasping core concepts and best practices.' What does Liam primarily intend to measure with this metric?
Liam is focusing on 'early bug incidence,' which directly addresses Alex's concern about frequent initial issues. Tracking this metric – the number of critical bugs in the first week after PR merge – provides a clear indication of whether developers are understanding and applying fundamental principles during their early contributions. This contrasts with measuring code quality or documentation effectiveness, which are broader metrics; velocity focuses on output rather than quality.
15 / 25
A developer experience analyst is presenting a report to the engineering leadership team. The report highlights that new developers take an average of 3 weeks to complete their first major feature and consistently rate the documentation as 'unhelpful' in their onboarding surveys. Which metric, when combined with the documentation feedback, offers the *most* actionable insight into identifying areas for improvement within the onboarding process?
While all options represent potential data points, the core issue is 'unhelpful' documentation. Tracking time spent searching internal knowledge bases directly correlates with that pain point and provides a measurable indication of how effectively information is being delivered. The other options – code review volume, overwhelmed feelings, or lines of code – are tangential and don't directly address the documented problem with the onboarding documentation itself. This allows for targeted improvements to the documentation resources.
16 / 25
PR#1234 has a comment from @reviewer: 'This looks good overall, but the error handling needs to be more robust. Consider adding logging and retry mechanisms.' After reviewing this PR, a new developer, Sarah, spent 8 hours implementing these changes. Which of the following metrics *most* accurately reflects the efficiency of Sarah's onboarding experience in addressing this specific feedback? While line count and feedback severity offer *some* context, the most accurate measure of onboarding efficiency is directly tied to how effectively a new developer addresses specific feedback. Sarah's total time spent on the PR – including revisions and communication – provides a tangible metric for evaluating the onboarding process's ability to equip developers with the skills to handle common review comments. Focusing solely on code changes or feedback severity obscures the crucial element of learning and adapting within the context of a collaborative development workflow.
17 / 25
PR#5678 has a comment from @lead_engineer: 'The API response format is inconsistent with the documentation. Ensure consistent use of JSON schema validation and clear error codes.' After reviewing this PR and attempting to integrate it into their project, Ben spent 12 hours refactoring his code to align with these requirements. Which metric provides the *most* granular insight into the effectiveness of the onboarding process in addressing this specific technical challenge? While all options relate to onboarding metrics, the question specifically asks for insight into *this* particular challenge – API integration and adherence to documentation. Option 3 directly measures how often developers are seeking clarification on a specific technical aspect during onboarding, which is the most focused metric for understanding that experience. Options A & B offer broader views of code review efficiency and successful integrations, while option C focuses on a different type of feedback.
18 / 25
PR#9012 has a comment from @senior_dev: 'The code style is inconsistent with our team's conventions. Please adhere to the established naming standards and formatting guidelines.' Following this feedback, David spent 3 hours reformatting his entire module to comply with these requirements. Which metric most accurately reflects the impact of this stylistic feedback on David's onboarding experience? The correct answer is High technical debt. The comment highlights a significant issue – inconsistent code style – which directly contributes to increased effort and rework. While the other options could be contributing factors, the core problem identified in the comment centers around the level of established standards and the impact on David's work. Misconceptions might include thinking low complexity or insufficient training were primary drivers; these are secondary issues that can arise from poor adherence to conventions.
19 / 25
During a Slack conversation about onboarding metrics, Alex writes: 'I'm seeing a high rate of initial bug reports on PRs. It's costing us time and slowing down the team.' Liam responds: 'Let's track the number of critical bugs found in the first 7 days after a developer's PR is merged. That gives us a good signal about how well they're grasping core concepts and best practices.' What does Liam primarily intend to measure with this metric?
Liam is focusing on 'early bug incidence,' which directly addresses Alex's concern about frequent initial issues. Tracking this metric – the number of critical bugs in the first week after PR merge – provides a clear indication of whether developers are understanding and applying fundamental principles during their early contributions. This contrasts with measuring code quality or documentation effectiveness, which are broader metrics; velocity focuses on output rather than quality.
20 / 25
A developer experience analyst is presenting a report to the engineering leadership team. The report highlights that new developers take an average of 3 weeks to complete their first major feature and consistently rate the documentation as 'unhelpful' in their onboarding surveys. Which metric, when combined with the documentation feedback, offers the *most* actionable insight into identifying areas for improvement within the onboarding process?
While all options represent potential data points, the core issue is 'unhelpful' documentation. Tracking time spent searching internal knowledge bases directly correlates with that pain point and provides a measurable indication of how effectively information is being delivered. The other options – code review volume, overwhelmed feelings, or lines of code – are tangential and don't directly address the documented problem with the onboarding documentation itself. This allows for targeted improvements to the documentation resources.
21 / 25
PR#1234 has a comment from @reviewer: 'This looks good overall, but the error handling needs to be more robust. Consider adding logging and retry mechanisms.' After reviewing this PR, a new developer, Sarah, spent 8 hours implementing these changes. Which of the following metrics *most* accurately reflects the efficiency of Sarah's onboarding experience in addressing this specific feedback? While line count and feedback severity offer *some* context, the most accurate measure of onboarding efficiency is directly tied to how effectively a new developer addresses specific feedback. Sarah's total time spent on the PR – including revisions and communication – provides a tangible metric for evaluating the onboarding process's ability to equip developers with the skills to handle common review comments. Focusing solely on code changes or feedback severity obscures the crucial element of learning and adapting within the context of a collaborative development workflow.
22 / 25
PR#5678 has a comment from @lead_engineer: 'The API response format is inconsistent with the documentation. Ensure consistent use of JSON schema validation and clear error codes.' After reviewing this PR and attempting to integrate it into their project, Ben spent 12 hours refactoring his code to align with these requirements. Which metric provides the *most* granular insight into the effectiveness of the onboarding process in addressing this specific technical challenge? While all options relate to onboarding metrics, the question specifically asks for insight into *this* particular challenge – API integration and adherence to documentation. Option 3 directly measures how often developers are seeking clarification on a specific technical aspect during onboarding, which is the most focused metric for understanding that experience. Options A & B offer broader views of code review efficiency and successful integrations, while option C focuses on a different type of feedback.
23 / 25
PR#9012 has a comment from @senior_dev: 'The code style is inconsistent with our team's conventions. Please adhere to the established naming standards and formatting guidelines.' Following this feedback, David spent 3 hours reformatting his entire module to comply with these requirements. Which metric most accurately reflects the impact of this stylistic feedback on David's onboarding experience? The correct answer is High technical debt. The comment highlights a significant issue – inconsistent code style – which directly contributes to increased effort and rework. While the other options could be contributing factors, the core problem identified in the comment centers around the level of established standards and the impact on David's work. Misconceptions might include thinking low complexity or insufficient training were primary drivers; these are secondary issues that can arise from poor adherence to conventions.
24 / 25
During a Slack conversation about onboarding metrics, Alex writes: 'I'm seeing a high rate of initial bug reports on PRs. It's costing us time and slowing down the team.' Liam responds: 'Let's track the number of critical bugs found in the first 7 days after a developer's PR is merged. That gives us a good signal about how well they're grasping core concepts and best practices.' What does Liam primarily intend to measure with this metric?
Liam is focusing on 'early bug incidence,' which directly addresses Alex's concern about frequent initial issues. Tracking this metric – the number of critical bugs in the first week after PR merge – provides a clear indication of whether developers are understanding and applying fundamental principles during their early contributions. This contrasts with measuring code quality or documentation effectiveness, which are broader metrics; velocity focuses on output rather than quality.
25 / 25
A developer experience analyst is presenting a report to the engineering leadership team. The report highlights that new developers take an average of 3 weeks to complete their first major feature and consistently rate the documentation as 'unhelpful' in their onboarding surveys. Which metric, when combined with the documentation feedback, offers the *most* actionable insight into identifying areas for improvement within the onboarding process?
While all options represent potential data points, the core issue is 'unhelpful' documentation. Tracking time spent searching internal knowledge bases directly correlates with that pain point and provides a measurable indication of how effectively information is being delivered. The other options – code review volume, overwhelmed feelings, or lines of code – are tangential and don't directly address the documented problem with the onboarding documentation itself. This allows for targeted improvements to the documentation resources.
Frequently Asked Questions
What does the "Developer Onboarding Metrics Vocabulary" exercise practise?
Practice the vocabulary of developer onboarding metrics: time to first PR, time to first production deploy, ramp-up period, onboarding friction, and ROI communication.
How many questions are in this exercise?
This exercise has 25 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Developer Experience Metrics category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Developer Onboarding Metrics Vocabulary" part of a larger series?
Yes — it's one exercise in the Developer Experience Metrics category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Developer Experience Metrics category page for related exercises, or browse the main Exercises hub for other IT English topics.