Practise vocabulary for staff engineer mentoring: levelling vocabulary, feedback language, engineering growth conversations, and coaching patterns.
0 / 12 completed
1 / 12
When a staff engineer gives feedback, saying '___, and here's what impact it had' uses the ___ feedback pattern.
SBI (Situation-Behaviour-Impact) structures feedback: describe the specific situation, the observed behaviour, and its impact. This is more actionable than vague feedback and less personal than character judgements.
2 / 12
'___ questions help engineers discover solutions themselves rather than being told the answer.' Which word fits?
Coaching questions (open-ended, reflective) guide engineers to their own insights: 'What do you think is the biggest risk here?' or 'What would you do differently next time?' This builds autonomous problem-solving rather than dependency on the mentor.
3 / 12
When discussing career growth with a senior engineer, a staff engineer should frame expectations in terms of ___ rather than tenure.
Staff-level promotion is based on scope and impact: the breadth of systems influenced, the ambiguity navigated, and the organisational change achieved. Framing growth conversations around impact rather than skills or tenure aligns with how staff-level roles are evaluated.
4 / 12
'___ engineering' is the concept that staff engineers should multiply team output — their leverage comes from enabling others, not personal output.
Multiplier engineering (or 10x engineering through leverage) means a staff engineer's value comes from making 10 engineers more effective, not from being 10x personally productive. Mentoring, tooling, processes, and documentation are multiplier activities.
5 / 12
When a junior engineer asks a staff engineer to make a decision for them, the coaching response is often ___.
Coaching engineers to make decisions themselves builds their confidence and capability. 'What options have you considered?' forces structured thinking and often reveals the engineer already has the answer — they just need validation and a framework.
6 / 12
Sarah, a Staff Engineer, is reviewing David's PR proposing a new caching layer for the API. David has followed best practices for code style and testing but the performance impact hasn't been fully considered. Sarah comments: 'This is good work, and here's what impact it had – the initial load times for users in Europe will increase by approximately 15% due to the added network latency.' Which feedback pattern is Sarah using?
Sarah's comment directly links the technical action (the PR) to its real-world consequences – increased latency for European users. This is a key element of the 'impact' feedback pattern, which focuses on helping the developer understand *why* their work matters and what potential issues they need to address beyond just pointing out code flaws. Options A and C are overly directive; option B is too vague, while D only addresses one aspect of the problem.
7 / 12
Mark, a Senior Engineer, asks Emily (a Staff Engineer) for guidance on prioritizing a complex refactoring task. Emily responds: 'I think we should focus on the areas with the highest risk of failure first.' Which principle does this response best represent?
Emily's statement encourages Mark to take ownership and critically evaluate the situation. This aligns with the principle of 'facilitation', where a staff engineer guides by suggesting frameworks for decision-making rather than dictating solutions – essentially empowering the Senior Engineer to problem-solve. Options A and D represent control; option B is too vague.
8 / 12
Liam, a Senior Engineer, sends the following Slack message to Chloe (a Staff Engineer): 'This feature is great! But I'm concerned about the long-term maintainability. Can we discuss some strategies for ensuring it remains scalable?' Which of the following best describes Chloe's role in this interaction?
Chloe's response is crucial because it moves beyond simply agreeing with Liam. It demonstrates her role as a mentor by actively seeking to understand the root of his concern (maintainability) and guiding him toward potential solutions. Dismissing Liam's concerns would be counterproductive, while offering immediate technical fixes isn't the staff engineer's primary function.
9 / 12
Ben, a Staff Engineer, is reviewing a PR submitted by a junior developer. The code is functional but lacks detailed documentation. Ben's feedback focuses on 'adding comments to explain the logic' and 'writing API contracts'. What principle does this approach primarily represent?
Ben's focus on documentation and API contracts directly addresses technical debt. By encouraging clear explanations and well-defined interfaces, he's helping the team avoid future issues caused by a lack of understanding. While coding standards are important, Ben is prioritizing long-term maintainability over strict rule enforcement.
10 / 12
Ava, a Staff Engineer, is leading a standup meeting. A developer raises the following concern: 'I'm blocked on getting access to the database due to an authentication issue.' Ava responds: 'Okay, let's troubleshoot the authentication flow together.' Which of the following best captures Ava's approach?
Ava's response signifies a collaborative approach, aligning with the staff engineer's role in empowering team members. Instead of simply assigning the problem or ignoring it, she offers immediate support and willingness to work together towards a resolution. Delegation or instruction would be less effective in this situation.
11 / 12
Daniel, a Staff Engineer, is describing the concept of 'systems thinking' to his team. He states: 'We need to consider not just the immediate impact of our code changes but also how those changes will affect other parts of the system and potential downstream consequences.' What does this primarily emphasize?
Daniel's statement highlights the importance of 'systems thinking,' which is central to a staff engineer's role. It emphasizes that decisions should be made with an awareness of the broader system and potential unintended consequences, moving beyond purely localized optimizations.
12 / 12
Frank, a Staff Engineer, is reviewing a PR from a junior engineer. The PR implements a new feature with detailed unit tests but lacks performance testing. Frank's feedback to the engineer includes: 'Let's run some load tests to identify any bottlenecks.' What does this suggest about Frank's primary goal?
Frank's suggestion of running load tests demonstrates a focus on risk mitigation. Performance is often a critical and frequently overlooked area, especially in complex systems. By proactively seeking performance data, Frank is safeguarding the team against potential issues that could impact scalability or user experience.
What will I learn from the "Staff Engineering Mentoring Language" exercise?
Practise vocabulary for staff engineer mentoring: levelling vocabulary, feedback language, engineering growth conversations, and coaching patterns.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 12 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Staff Engineer Communication exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss staff engineer communication topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 12 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Staff Engineer Communication exercises?
See the full Staff Engineer Communication exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.