Writing a getting-started README for a new joiner — what is the most critical section?
README priority: "from zero to running locally in under 30 minutes" = good README. Sections: prerequisites → clone → configure → install dependencies → run → verify working.
The ADR template asks for 'Context and Problem Statement' — what should it contain?
ADR Context: future reader empathy. "In Q3 2023, we needed to choose a queue for async job processing. Constraints: existing Redis infrastructure, team unfamiliar with Kafka, expected volume < 10K/day..."
The onboarding docs have a 'Who to ask about what' section — why is this one of the most valuable resources?
"Who to ask": reduces invisible friction. Format: "For questions about X → ask @person or #channel". Empowers new joiners to seek help confidently.
Key vocab: "knowledge directory", "domain ownership map", "who-to-ask guide", "internal networking for new joiners".
4 / 10
The wiki was last updated 18 months ago — what is documentation drift and how does it affect onboarding?
Documentation drift: the longer since last update, the less trustworthy. Mitigation: documentation review on each substantial change, "last verified date" stamps, "known outdated" notices.
Writing a 'system overview' document for a new joiner — what level of detail is appropriate?
System overview: mental model first. Purpose → components → data flow → externals → "for more detail on X, see Y". Avoids detail overload before the mental model exists.
Key vocab: "system overview", "mental model document", "component map", "data flow", "jumping-off point to deeper docs".
6 / 10
Sarah (Senior Backend Engineer) just posted a comment on your code review: 'This function doesn't handle edge cases. Consider what happens when the input is null.' What's the MOST appropriate response to Sarah in this context, aiming for clear communication and collaboration?
[Code Review Comment]
This question focuses on responding constructively in a code review scenario. Option 2 demonstrates acknowledgement of the issue, proposes a solution, and invites further discussion – exactly what's needed when receiving feedback about edge cases. Options A and D are dismissive or incorrect. Option C is acceptable but doesn't proactively address Sarah's concern.
7 / 10
David (Team Lead) sends you the following Slack message: 'Hey team, just a reminder that all new feature documentation needs to include a brief overview of the system architecture. It's crucial for onboarding.' Why is David emphasizing this specific element in his communication?
[Slack Message]
This tests understanding of architectural awareness during onboarding. David is highlighting that documenting system architecture isn't just about compliance (option A) but fundamentally helps new developers grasp *context* and understand how their work relates to the broader system – a critical element for effective knowledge transfer and reducing rework. Options B, C, and D are secondary benefits or misinterpretations.
8 / 10
You're drafting a PR description for a bug fix that improves the error handling in a microservice. The description needs to be clear and concise for new team members. Which of the following is the MOST effective way to phrase the purpose of your change?
[PR Description]
Option 1 provides a succinct and factual description of the fix. It avoids jargon and clearly states what was addressed. Option 2 is too detailed for a PR description intended for onboarding (it's more suitable for a technical commit message). Options B and C are vague or overly focused on process, while D is far too simplistic.
9 / 10
Maria (Documentation Specialist) informs you that the company's internal API documentation has been updated with a new endpoint for user authentication. However, no one on the team has yet reviewed or incorporated this change into their workflow. What is the MOST immediate concern regarding potential documentation drift?
[Standup Update]
This question focuses on the practical consequences of outdated documentation. While option A is a possible result (and a valid concern), option B highlights the *direct* impact – reduced productivity and potential errors – that arises when developers don't utilize updated information. Options C and D represent secondary concerns or misinterpretations.
10 / 10
You're creating a system overview document for a new developer joining the team. The document needs to provide a high-level understanding of the project's components and their interactions. Which level of detail is MOST appropriate to include regarding the database schema?
[System Overview Document]
Option 1 is far too granular for an introductory system overview. New developers don't need a complete schema diagram initially; it would overwhelm them. Option 2 provides a balanced approach – enough detail to understand relationships without getting bogged down in specifics. Options B and C are overly simplified, while option A is excessively detailed and likely irrelevant at this stage.
What will I practise in "Documentation for Onboarding"?
This module focuses on Onboarding & Knowledge Transfer — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Onboarding & Knowledge Transfer exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around onboarding & knowledge transfer — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Onboarding & Knowledge Transfer exercises?
See the Onboarding & Knowledge Transfer hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.