Practice team assessment vocabulary in technical due diligence: bus factor, team composition, hiring pipeline, technical hiring velocity, and team health indicators.
0 / 10 completed
1 / 10
A due diligence report says 'the bus factor is 1 for the core payment service'. What is the bus factor?
Bus factor (or truck factor) measures team knowledge concentration risk. A bus factor of 1 means only one person has the knowledge to maintain a system — if they leave, the team loses critical institutional knowledge. In due diligence, a bus factor of 1 on critical services is a significant retention and operational risk that affects valuation.
2 / 10
'The team has 3 experienced engineers and 2 recent hires.' What does this team composition signal in due diligence?
Team composition analysis in due diligence examines the balance of senior and junior engineers, their tenure, and specialisation coverage. A team too heavy on recent hires with few senior engineers may struggle with architectural decisions and delivery quality. Acquirers assess whether the team can scale and maintain quality post-acquisition.
3 / 10
'The engineering hiring pipeline is strong.' What does a strong hiring pipeline indicate?
A strong hiring pipeline means the company can scale its engineering team effectively: it has a known employer brand, a sourcing strategy, a structured interview process, and a competitive offer process. In due diligence, a weak or non-existent hiring pipeline is a growth risk — post-acquisition scaling may be slower and more expensive than projected.
4 / 10
What is 'technical hiring velocity' in a team assessment?
Technical hiring velocity measures how fast and effectively a company can add engineering talent. It includes metrics like time-to-hire (from job posting to accepted offer), offer acceptance rate, and how many qualified candidates pass the technical screen. Low velocity means the team cannot scale quickly — a risk for growth plans and post-acquisition integration timelines.
5 / 10
In a team health assessment, what does 'team attrition risk' refer to?
Attrition risk assesses the likelihood that valuable engineers will leave after the acquisition. Common triggers include: compensation packages that lag post-acquisition norms, culture clashes between the acquired and acquiring companies, key engineer retention clauses not being offered, and uncertainty about role changes. High attrition risk for key engineers is a major due diligence flag.
6 / 10
During a standup meeting, Sarah says, 'I spent the morning debugging an issue with the user authentication service. It turned out to be a race condition caused by concurrent requests.' What does 'race condition' likely refer to in this context?
A race condition occurs when the outcome of a program depends on the unpredictable order in which multiple threads or processes access and modify shared resources. Sarah's description directly points to this scenario – concurrent requests competing for access to the authentication service.
7 / 10
A Slack message reads: 'David's PR introduces a potential null pointer exception in the API endpoint handler. The error occurs when the input data is missing a required field.' What does this suggest about David's code quality?
The mention of a 'null pointer exception' indicates a vulnerability in David's code – specifically, the lack of proper input validation. This can lead to unexpected crashes or errors if the API endpoint doesn't receive all required data, signifying a need for improved error handling and defensive programming.
8 / 10
A code review comment reads: 'This function could benefit from more unit tests to cover edge cases.' What does this comment highlight?
The comment emphasizes the importance of thorough testing. 'Edge cases' are unusual or boundary conditions that often cause bugs if not explicitly tested. Insufficient unit tests leave the system vulnerable to these types of errors and highlight a critical area for improvement.
9 / 10
During a team assessment, a report states: 'The team's average code review turnaround time is 24 hours.' What does this primarily indicate?
A long turnaround time for code reviews suggests a potential bottleneck. This could be due to factors like limited reviewer availability, complex changes, or inefficient review processes, impacting the overall team velocity.
10 / 10
A PR description states: 'This change refactors the legacy authentication module to improve performance and maintainability. It introduces a new dependency on the identity service.' What is the primary concern highlighted by this description?
Introducing a new dependency always carries risk. While the description mentions performance improvements, it's crucial to assess the impact of this dependency on long-term maintainability and potential compatibility problems as the identity service evolves - highlighting a key aspect of technical debt.
What does this Technical Due Diligence Language exercise cover?
This exercise, "Team Assessment Vocabulary", tests your understanding of technical due diligence language vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Due Diligence Language exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical due diligence language topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Due Diligence Language exercises?
Browse the full Technical Due Diligence Language exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.