Developer Relations: Community & Developer Outreach Phrases
5 exercises on DevRel key phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
Which phrase best acknowledges user feedback in a public developer forum without making promises?
"Thanks for the feedback — we'll look into it" is the standard DevRel response because it acknowledges the user, expresses gratitude, and signals action without over-promising a fix or timeline. Option A ("fix right away") sets an expectation you may not meet. Option C ("personally make sure") is an overcommitment that can backfire. Option B is dismissive and damages community trust. In developer relations, managing expectations professionally is as important as solving the technical problem itself.
2 / 10
A user has requested a feature that your team plans to build in a future release. Which reply is most appropriate?
"We've added that to our roadmap" is the professional DevRel standard for communicating planned-but-unscheduled work. It validates the user's request, signals that the team has taken it seriously, and avoids committing to a specific date. Option A ("next week") is a false promise unless the release is truly imminent. Option C is a conversation stopper and undermines confidence in the product. Option D is dismissive and alienates users. "Roadmap" is a well-understood term in tech communities that sets realistic expectations.
3 / 10
A user reports a critical bug affecting their production system. Your team is investigating but has no fix yet. What do you say?
"Here's a workaround while we investigate" is exactly the right DevRel move: it unblocks the user immediately while the real fix is being worked on. This two-part response — interim relief plus transparency about the investigation — is a hallmark of excellent developer support. Option B delays help unnecessarily. Option C forces the user to wait with no relief. Option D ("known limitation") dismisses the problem as a feature, which is damaging when the user's production system is down. Always try to unblock users first.
4 / 10
A developer has shared a creative use case for your API that could make a great case study. How do you follow up?
"Your use case is really interesting — would you be open to a call?" is the ideal DevRel follow-up. It flatters the developer authentically, opens a deeper relationship, and creates an opportunity for a case study, testimonial, or advisory conversation. Option A shuts down a potential partnership. Option B is a bureaucratic deflection that kills enthusiasm. Option D ("seen it before") is dismissive and makes the developer feel their work is unremarkable. In DevRel, turning enthusiastic users into advocates is a core goal — this phrase opens that door.
5 / 10
A developer has submitted a detailed bug report with logs, reproduction steps, and environment info. What is the most appropriate response opening?
"We appreciate the detailed bug report" is the correct opener because it explicitly rewards the behaviour you want to encourage. Detailed bug reports with logs and reproduction steps are invaluable — acknowledging this encourages the community to maintain the same quality. Option A ("already know") is dismissive and makes the effort feel wasted. Option C ("more information") is inappropriate when the report is already detailed and signals you haven't read it. Option D is accusatory and incorrect. Positive reinforcement of good reporting is a key DevRel community health practice.
6 / 10
Liam from the onboarding team sent you this Slack message: 'Hey @developer_user, awesome work on that integration! Seriously considering using it in our internal tools.'
Which response best acknowledges Liam's enthusiasm while maintaining professional boundaries?
The key here is balancing appreciation with a focus on constructive engagement. Option 2 politely acknowledges the compliment without immediately committing to further discussion or implying an expectation of ongoing support. Options A and D are too informal, while option 3 invites unnecessary conversation about usage details at this stage.
7 / 10
Sarah (Product Manager) replies to a developer's request for a new data visualization feature:
'We've noted your suggestion regarding the enhanced charting library. This is something we're actively exploring as part of our Q3 roadmap.'
What is the most appropriate follow-up response from you, as a Developer Advocate?
Sarah has provided an acknowledgment of the request's value. Your response should demonstrate proactive engagement and elicit further information. Option 1 is too brief, option 3 asks for unnecessary details at this point, and option 4 is passive and unhelpful – you need to show interest.
8 / 10
Mark reports a critical error in your application's API. The response from the monitoring system indicates a spike in latency affecting users accessing endpoint /users/{user_id}:
'Error: HTTP 502 Bad Gateway. Duration: 12ms.'
What's the best initial message to send back to Mark?
The monitoring response provides crucial information – the specific endpoint and error code. Option 2 asks for details that Mark has already provided through his report. Option 3 is the most targeted question to help narrow down the problem quickly, while option 4 avoids active investigation.
9 / 10
David (Lead Developer) asks you to review this PR description:
'Fixed a bug where users were getting incorrect data. Updated the database query.'
Which response is most effective when providing feedback on this PR?
A good PR description should provide sufficient context for reviewers. Option 1 asks for redundant information. Option 3 is overly brief and doesn't offer constructive criticism. Option 4 is only necessary if the PR itself lacks a link to the issue – this description already implies that.
10 / 10
Emily (Community Manager) asks you to draft an update for the standup meeting:
'Any progress on getting the new documentation released?'
Which of the following is the MOST appropriate way to respond in your update?
Providing specific information about the delay is crucial for transparency. Option 1 is vague and doesn't offer a timeline. Option 3 is unhelpful as it confirms inaction. Option 4 is overly optimistic without acknowledging any problems.
What will I practise in "Developer Relations: Community & Developer Outreach Phrases"?
This module focuses on Phrasebook — 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 Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — 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 Phrasebook exercises?
See the Phrasebook 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.