Writing a transition document before leaving — what should it contain?
Transition doc: successor-centric, not author-centric. Not "here's what I was proud of". Yes: "here's where the landmines are, who to call when X breaks, what's not done and what it would take to finish."
The departing engineer is telling team members the news — what tone is most appropriate?
Leaving communication: gratitude + respect + forward-looking. "Working with this team taught me X" + "I'm leaving to pursue Y" (brief, positive). Don't disparage, over-explain, or burn bridges.
The engineer was the sole owner of a legacy system no one else understands — what is their responsibility?
Sole-knowledge system: bus factor = 1 = highest risk. Mitigation: pair with designated successor, create video walkthrough, write runbooks for all operational scenarios, seek temporary extension if needed.
David, the senior backend engineer, is sending a Slack message to announce his departure. He wants to ensure a smooth handover. Which of the following messages best reflects professional and helpful communication?
'Just letting you know I'm leaving. Don't bother contacting me.'
The correct response demonstrates proactive communication and a willingness to assist during the transition. Options A and D are unprofessional and unhelpful. Option B focuses solely on technical details without acknowledging the human element of the departure, while option C highlights a specific responsibility but doesn't offer broader support.
7 / 10
Maria is writing a comment on a code review for a feature she's handing over to Ben. The code contains a complex algorithm. What's the best way to guide Ben's understanding?
'Looks good, just merge it.'
Providing specific technical context is crucial for effective knowledge transfer. The correct option details the core functionality of the code, prompting Ben to verify its correctness and test thoroughly. Options A and B are too vague, while D offers no guidance and potentially encourages a lack of scrutiny.
8 / 10
John is preparing a pull request description for a substantial code change. He needs to clearly communicate the impact of his work to the team. Which sentence best summarizes this?
'Fixed some bugs.'
A good PR description needs to articulate *why* the change was made and its potential impact. The correct option explains the functionality of the new feature and its benefits – a key element in facilitating understanding and acceptance by reviewers. Options A and B provide technical details without context, while D is completely insufficient.
9 / 10
Sarah's role involved maintaining a critical API endpoint – the customer-data service. She's documenting her handover. What should she include in her documentation regarding the 'shadow period'?
'I'll be available for questions until my last day.'
The 'shadow period' is a critical phase where a successor observes the departing engineer in action. The correct option outlines this process, emphasizing observation and learning from practical experience. Options A and B offer inadequate support, while D is dismissive and unhelpful.
10 / 10
Tom is the sole maintainer of a legacy system that no one else understands. He's preparing to leave. What's his primary responsibility regarding this system?
'Let someone else take over.'
Even though the system might be outdated, Tom has a responsibility to ensure its continued operation. The correct option highlights the crucial step of providing knowledge transfer – documentation, training, or support – to enable another engineer to take over. Options A and B are irresponsible, while D is completely derelict.
What will I practise in "Leaving a Team: Handover Language"?
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.