"I'd like to understand your existing mental model before I explain."
Why does a senior engineer check the listener's mental model first?
Checking the mental model enables a targeted explanation — one that fills the specific gap rather than starting from scratch:
Outcome without check
Outcome with check
Explaining things already understood (patronising)
Build efficiently on what's already correct
Assuming foundations that don't exist (confusing)
Fill the exact gap — not a broader or narrower one
Missing the actual misconception
Correct the specific wrong assumption
Useful check phrase: "What's your current understanding of how X works?" Key vocabulary: "mental model check", "assess current understanding", "build on existing knowledge", "targeted explanation", "explain the delta".
4 / 14
After explaining a concept during pairing, you want to check if your partner understood.
Which check is most effective?
"Explain it back" is the Feynman technique applied to pairing comprehension checks:
Check type
What it reveals
"Did you understand?" / "Is that clear?" / "Any questions?"
Almost always gets "yes" — social pressure prevents "no" even when understanding is incomplete
B ✓ — "Explain it back in your own words"
Immediately reveals: gaps in understanding, misconceptions, partial comprehension
The quality of the explanation back tells you exactly what to rephrase. Key vocabulary: "explain it back", "in your own words", "Feynman technique", "comprehension check vs. yes/no question", "active understanding verification".
5 / 14
"I'm handing this part of the codebase over to you after today's session."
What should a knowledge handover during a pairing session cover?
A knowledge handover should prioritise context over code — what isn't obvious from reading the code is most valuable:
Handover item
Why it matters
Purpose and scope of the section
Frames all future decisions — what should and shouldn't go here
Non-obvious design decisions + reasoning
Prevents "why was this done this way?" reverse engineering
Review Comment: 'This function's logic is a bit convoluted. Could you explain the intention behind using nested loops like this? It's not immediately clear what problem it's solving.'
Which of the following best describes how to respond effectively in this code review scenario, focusing on knowledge sharing?
The key here is to address the root of the reviewer's concern – their lack of clarity about the function's purpose. Simply explaining the loops isn't enough; you need to demonstrate an understanding by detailing the transformations and why they are necessary. Ignoring the comment or pushing a fix without clarification will likely escalate the issue and hinder effective knowledge transfer.
7 / 14
Slack Message from Alex (Senior Developer): 'Hey @Ben (Junior Developer), just wanted to quickly run through how the batchSize parameter affects query performance. It's a bit tricky to visualize, but essentially, larger batches can improve throughput...'
Which of the following is the MOST effective follow-up question Ben should ask Alex to ensure he fully understands?
Ben's response should focus on directly addressing the core of Alex's explanation – the impact of batchSize. Asking for an example is ideal because it forces Alex to demonstrate the concept in a practical way. The other options are too broad or don't actively engage with the specific information provided.
8 / 14
PR Description: 'Fixes issue #1234 – inefficient database queries. Optimized query logic using prepared statements and batching for improved performance. Added logging to monitor execution times.'
Which element is MOST crucial to add to this PR description to better facilitate knowledge sharing with the team?
While the current description is functional, it lacks a crucial element – an explanation of *why* prepared statements and batching were chosen. This provides context and allows others to understand the design decisions and their benefits, fostering better knowledge sharing within the team. Simply stating that tests passed doesn't convey the 'how' or 'why'.
9 / 14
Standup Update from Maria: 'Yesterday, I was working on improving the error handling in the authentication service. I implemented a new retry mechanism with exponential backoff to handle transient network issues. I'm still investigating the root cause of some intermittent failures.'
Which statement best summarizes what Maria should add to her standup update to effectively share knowledge and highlight areas needing support?
Maria needs to clearly articulate the *outcome* of her work – the reduced error rates due to the retry mechanism. This provides concrete evidence of her progress and demonstrates the value she added. Simply stating she's investigating without quantifying the impact isn't as effective for knowledge sharing.
10 / 14
Sarah (Senior) is pairing with David (Junior) on a complex algorithm. David asks: 'Can you walk me through the reasoning behind this recursive call? I'm struggling to see how it avoids infinite loops.' Which of the following approaches would be MOST effective for Sarah to use?
The most effective approach here is to guide David through the logic step-by-step using a concrete example. This avoids overwhelming him with abstract concepts and allows him to actively participate in understanding the algorithm's flow. Simply explaining line by line can be passive; tracing manually forces engagement. Focusing on output alone doesn't address the core challenge of understanding recursive behavior.
11 / 14
During a code review session, Liam (Junior) submits a pull request with a large block of SQL. The reviewer, Chloe (Senior), comments: 'This query is very complex and difficult to understand. Could you explain the rationale behind using this specific join strategy?' Which action should Chloe take NEXT to ensure Liam fully understands the implications?
Chloe needs to delve beyond just the technical aspects of the code. Understanding *why* a particular strategy was chosen is crucial for Liam's learning. Asking about performance bottlenecks and alternative approaches encourages critical thinking and demonstrates the importance of considering context when designing database queries. Dismissing it as 'efficient' doesn't foster understanding.
12 / 14
Mark (Senior) is mentoring Emily (Junior). After explaining a new API endpoint, he asks: 'So, to be sure you've grasped this, can you describe how you would use this endpoint in a typical scenario?' What does Mark primarily assess with this question?
Mark is evaluating Emily's *understanding* beyond just rote memorization. He wants to see if she can translate the technical details into a real-world use case – demonstrating that she truly grasps the endpoint's purpose and how it fits into the broader system. This tests her ability to apply knowledge, not simply recall facts.
13 / 14
During a Slack discussion about debugging an issue, Daniel (Senior) writes: 'I'm running some diagnostics on the server to isolate the root cause. I'll let you know what I find.' What is Daniel primarily communicating in this message?
Daniel's message indicates that he's actively engaged in troubleshooting. He's stating his intention to investigate and share findings – this conveys transparency and proactive communication, essential for effective knowledge sharing within a development team. It is not an urgent alert or a request for help.
14 / 14
You are handing over ownership of a module to a new developer, Alex. Which statement best summarizes the key information you should include during this handover?
A successful knowledge handover needs more than just a description of what the module *does*. It should cover key components, their relationships (dependencies), and any known limitations or potential problems. This provides Alex with the context needed to confidently maintain and extend the code.
What will I practise in "🎓 Knowledge Sharing & Mentoring Vocabulary"?
This module focuses on Pair Programming & Collaboration — real workplace phrasing you'll use on the job. It contains 14 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 14 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 Pair Programming & Collaboration exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around pair programming & collaboration — 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 Pair Programming & Collaboration exercises?
See the Pair Programming & Collaboration 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.