Practise the IT-English phrasing of cold outreach emails to developers: subject lines, personalisation, value-first and clear CTAs.
0 / 18 completed
1 / 18
Which is the most effective cold-email 'subject line' for a busy developer?
A specific, relevant subject signals genuine context and respects the reader's time without sounding spammy.
2 / 18
Why open with 'personalisation' referencing the recipient's work?
Genuine personalisation shows the outreach is relevant and not a generic blast, improving reply rates.
3 / 18
A 'value-first' cold email does what?
Value-first outreach offers something helpful up front, earning attention before asking for anything.
4 / 18
What makes a good 'call to action' (CTA) in a cold email?
A single, easy, specific CTA makes it simple for the reader to say yes.
5 / 18
Which closing line is appropriately respectful of a non-reply?
Giving a graceful opt-out keeps the tone respectful and professional.
6 / 18
Sarah from our team sent this PR description to the codebase review channel:
`Fix: Resolve minor bug in user authentication. Updated JWT validation logic.
@JohnDoe - Could you take a look when you have a moment? Thanks!`
Which of the following phrases would be most appropriate for Sarah to add *before* her original description to improve the cold outreach aspect of this review request, assuming she's initially contacting John Doe who is known for being very busy?
The key here is understanding that 'cold outreach' isn't just about sending an email; it's about efficiently getting someone's attention and making them want to help. Option A sounds demanding and doesn't acknowledge John Doe's potential busyness. Option B is too informal for a code review request, and option C focuses solely on the technical details without offering context or seeking assistance. Option D emphasizes urgency in an overly dramatic way – highlighting the blocking factor isn't necessary and can feel pushy. Option 1 acknowledges John Doe's time constraints while politely requesting his input, which is ideal for a productive interaction.
7 / 18
JohnDoe is a senior developer and known for receiving many code review requests. Sarah wants to initially contact him about a JWT validation update within the user authentication PR. Which of the following additions to her original description would be most effective in initiating a productive conversation, acknowledging his time constraints?
The best option (2) demonstrates respect for John's time by acknowledging the issue is 'minor' and framing the request as seeking his 'feedback'. This softens the approach compared to a demanding CTA or an overly assertive statement. Options A and D are too direct and potentially overwhelming, while Option B simply requests a review without any context or consideration of John's workload.
8 / 18
Sarah from our team sent this PR description to the codebase review channel:
`Fix: Resolve minor bug in user authentication. Updated JWT validation logic.
@JohnDoe - Could you take a look when you have a moment? Thanks!`
Which of the following phrases would be most appropriate for Sarah to add *before* her original description to improve the cold outreach aspect of this review request, assuming she's initially contacting John Doe who is known for being very busy?
The key here is understanding that 'cold outreach' isn't just about sending an email; it's about efficiently getting someone's attention and making them want to help. Option A sounds demanding and doesn't acknowledge John Doe's potential busyness. Option B is too informal for a code review request, and option C focuses solely on the technical details without offering context or seeking assistance. Option D emphasizes urgency in an overly dramatic way – highlighting the blocking factor isn't necessary and can feel pushy. Option 1 acknowledges John Doe's time constraints while politely requesting his input, which is ideal for a productive interaction.
9 / 18
JohnDoe is a senior developer and known for receiving many code review requests. Sarah wants to initially contact him about a JWT validation update within the user authentication PR. Which of the following additions to her original description would be most effective in initiating a productive conversation, acknowledging his time constraints?
The best option (2) demonstrates respect for John's time by acknowledging the issue is 'minor' and framing the request as seeking his 'feedback'. This softens the approach compared to a demanding CTA or an overly assertive statement. Options A and D are too direct and potentially overwhelming, while Option B simply requests a review without any context or consideration of John's workload.
10 / 18
Sarah from our team sent this PR description to the codebase review channel:
`Fix: Resolve minor bug in user authentication. Updated JWT validation logic.
@JohnDoe - Could you take a look when you have a moment? Thanks!`
Which of the following phrases would be most appropriate for Sarah to add *before* her original description to improve the cold outreach aspect of this review request, assuming she's initially contacting John Doe who is known for being very busy?
The key here is understanding that 'cold outreach' isn't just about sending an email; it's about efficiently getting someone's attention and making them want to help. Option A sounds demanding and doesn't acknowledge John Doe's potential busyness. Option B is too informal for a code review request, and option C focuses solely on the technical details without offering context or seeking assistance. Option D emphasizes urgency in an overly dramatic way – highlighting the blocking factor isn't necessary and can feel pushy. Option 1 acknowledges John Doe's time constraints while politely requesting his input, which is ideal for a productive interaction.
11 / 18
JohnDoe is a senior developer and known for receiving many code review requests. Sarah wants to initially contact him about a JWT validation update within the user authentication PR. Which of the following additions to her original description would be most effective in initiating a productive conversation, acknowledging his time constraints?
The best option (2) demonstrates respect for John's time by acknowledging the issue is 'minor' and framing the request as seeking his 'feedback'. This softens the approach compared to a demanding CTA or an overly assertive statement. Options A and D are too direct and potentially overwhelming, while Option B simply requests a review without any context or consideration of John's workload.
12 / 18
Sarah from our team sent this PR description to the codebase review channel:
`Fix: Resolve minor bug in user authentication. Updated JWT validation logic.
@JohnDoe - Could you take a look when you have a moment? Thanks!`
Which of the following phrases would be most appropriate for Sarah to add *before* her original description to improve the cold outreach aspect of this review request, assuming she's initially contacting John Doe who is known for being very busy?
The key here is understanding that 'cold outreach' isn't just about sending an email; it's about efficiently getting someone's attention and making them want to help. Option A sounds demanding and doesn't acknowledge John Doe's potential busyness. Option B is too informal for a code review request, and option C focuses solely on the technical details without offering context or seeking assistance. Option D emphasizes urgency in an overly dramatic way – highlighting the blocking factor isn't necessary and can feel pushy. Option 1 acknowledges John Doe's time constraints while politely requesting his input, which is ideal for a productive interaction.
13 / 18
JohnDoe is a senior developer and known for receiving many code review requests. Sarah wants to initially contact him about a JWT validation update within the user authentication PR. Which of the following additions to her original description would be most effective in initiating a productive conversation, acknowledging his time constraints?
The best option (2) demonstrates respect for John's time by acknowledging the issue is 'minor' and framing the request as seeking his 'feedback'. This softens the approach compared to a demanding CTA or an overly assertive statement. Options A and D are too direct and potentially overwhelming, while Option B simply requests a review without any context or consideration of John's workload.
14 / 18
Mark is reaching out to a senior developer, Alex, about a potential integration with their new API. Mark wants to frame the conversation positively. Which of the following opening lines would be MOST effective in a Slack message?
mark@example.com
Option 1 directly highlights the potential benefit of the integration – aligning with 'value-first' outreach. Options 2 and 3 are too vague or focus on the request without establishing value. Option 4 is a generic call to action that doesn't immediately demonstrate understanding or interest in Alex's work; developers respond best when they see a clear reason for a conversation.
15 / 18
During a stand-up meeting, David wants to briefly explain that he's investigating a performance bottleneck in the user profile service. Which of the following statements is the MOST concise and appropriate for this context?
(David is speaking to his team)
Option 3 is the most direct and concise, suitable for a stand-up update. It clearly states the issue and David's action without getting bogged down in technical details. Options 1 & 2 are overly verbose; option 4 is too informal for a team meeting.
16 / 18
You're writing the description for a pull request that fixes a bug in a payment processing microservice. Which of the following phrases BEST describes the purpose of this PR?
payment-processor
Option 1 clearly states the *purpose* of the PR – fixing a bug related to payment processing. It's specific and informative. The other options describe different types of changes (UI, refactoring, dependency updates) that don't accurately reflect the core objective of the PR.
17 / 18
Liam is sending a cold email to Maria, a developer at a competitor company. He wants to subtly highlight his team's expertise in similar technologies. Which of the following sentences would be MOST effective?
(Liam's Email Subject Line)
Option 1 is a subject line that subtly references shared interests (tech trends) without being overly salesy. It's more likely to pique Maria's interest than a generic greeting or announcement of new features. The other options are too vague or focused on promotion.
18 / 18
Sarah is following up with David after sending him a PR request for review. She wants to politely check if he's had a chance to look at it. Which of the following messages is MOST appropriate?
(Sarah's Slack Message)
Option 2 directly references the PR and politely asks if David has seen it – this is the most efficient and professional approach. Options 1 & 3 are too informal; option 4 is a generic check-in that doesn't specifically address the PR.
What does the "Cold Outreach to Developers" exercise cover?
Practise the IT-English phrasing of cold outreach emails to developers: subject lines, personalisation, value-first and clear CTAs.
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.
How many questions are in "Cold Outreach to Developers"?
This exercise has 18 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Email & Writing exercises?
Browse the full Email & Writing hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.