You're joining a new team next Monday — what types of questions should you ask in your first week?
Good first questions: curious and learning-oriented. Avoid questions that imply criticism before understanding context. "Could you help me understand..." vs. "Why did you choose to..."
Building rapport with a remote team you've never met in person — which strategy is most effective?
Remote rapport: intentionality required (no water cooler). Virtual coffee = informal conversation. Public acknowledgment ("great catch on that PR review").
Your second-week retrospective is happening — how should you participate as a new joiner?
Retro as new joiner: "fresh eyes framing" = valuable but should be offered lightly. "I've only been here two weeks, take this with a grain of salt, but I noticed..."
Key vocab: "fresh eyes perspective", "light touch contribution", "new joiner retro participation", "observation before prescription".
4 / 13
The team uses informal communication norms you're not familiar with — how do you learn them without offending anyone?
Informal norms: observable before asking. "I noticed people emoji-react instead of typing 'sounds good' — is that the preferred acknowledgment?" = good buddy question.
Your first pull request receives several review comments — how should you respond?
First PR review response: engaged, humble, curious. "Good catch — I missed the convention around X. For the Y comment, I chose this approach because Z — does that reasoning make sense?"
Key vocab: "first PR response", "engaged with feedback", "ask clarifying questions", "reasoning explanation in PR", "constructive review dialogue".
6 / 13
Alex from the Backend team sends you this Slack message: 'Hey, can you take a look at the new API endpoint? Seems like it's returning null values sometimes. 🤔' As a newly integrated developer, what's your *most* appropriate initial response?
The best response here is to request documentation. Simply acknowledging the issue isn't helpful; you need to understand the API's intended behavior and the root cause of the null values. Asking for context demonstrates proactive engagement and avoids assumptions. Option 'B' is correct because it gathers vital information before attempting any debugging.
7 / 13
You're writing a PR description for a feature that adds a new user authentication flow. The team uses the following convention: 'Implemented [Feature Name] - Briefly describe changes and link to relevant tickets.' Which of the following descriptions best follows this style?
The provided convention prioritizes brevity and clear connection to related tickets. Option 'A' is best because it's concise, describes the key changes, and implicitly references the ticket(s) without verbose detail. Options 'B', 'C', and 'D' are too descriptive and don't align with the specified PR description format.
8 / 13
During a standup meeting, Ben says: 'I spent yesterday debugging a memory leak in the user profile service.' What's the *most* effective follow-up question you could ask him to gain more insight?
Asking about the *type* of memory leak and the resolution steps demonstrates genuine interest in Ben's work. This allows you to understand the technical details and potential implications. Option 'A' is purely reactive; options 'B', 'C', and 'D' are too superficial or irrelevant to the situation.
9 / 13
Sarah, a new member of the Frontend team, notices that many developers are using emojis liberally in Slack conversations. She wants to integrate smoothly. Which approach is MOST likely to be well-received?
The best approach is to observe and learn. Immediately adopting a behavior you're unsure of can seem forced. Respecting existing norms demonstrates awareness and avoids potential offense. Asking the lead is also good, but observation first minimizes disruption. Simply asking for more emojis is likely to be met with resistance.
10 / 13
You're reviewing a pull request submitted by David from the Mobile team. The code is well-written and functional but lacks clear documentation. What's the MOST appropriate response to give him in the code review comment?
Providing constructive feedback about documentation is crucial for long-term maintainability. A simple positive acknowledgement coupled with a suggestion for improvement is polite and helpful. Avoid overly critical or demanding language. The other options are too blunt or unhelpful.
11 / 13
During the daily standup, Emily mentions she's struggling with a complex algorithm in the data processing service. What's the MOST effective question you could ask her to understand the situation better and offer support?
Asking Emily to 'walk you through' allows her to explain her thought process and where she's getting stuck. This provides valuable insight into the technical challenge. The other options are too general or simply express sympathy without seeking understanding.
12 / 13
You receive this API response from a third-party service:
HTTP/1.1 200 OK
Content-Type: application/json
{
"status": "error",
"message": "Invalid request parameters"
}
As a developer, what's the BEST immediate action to take?
The response indicates an issue with the input data. The most responsible action is to investigate and correct the request parameters based on the API documentation. Simply ignoring the error or proceeding without correction could lead to further problems. Logging the error is important for debugging but doesn't solve the root cause.
13 / 13
The team uses a convention of writing PR descriptions like this: 'feat: Added support for dark mode. Resolves #1234.' What does the 'feat' prefix indicate?
The 'feat' prefix is a common convention for indicating that the pull request contains a *new* feature. It's part of the Conventional Commits specification, which helps with automated changelog generation and release notes. Understanding these prefixes is key to quickly grasping the purpose of each PR.
What will I practise in "Team Integration Language"?
This module focuses on Onboarding & Knowledge Transfer — real workplace phrasing you'll use on the job. It contains 13 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 13 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.