5 exercises — practise the professional English for LinkedIn cold messages, responding to recruiter InMail, asking for referrals, and rewriting generic networking messages into ones that get replies.
LinkedIn networking essentials
Cold message: name + why this person + one specific credential + soft CTA — keep it under 100 words
InMail reply (interested): confirm openness + ask about the project/team + propose a call
InMail reply (not now): stay warm + give a brief honest reason + ask them to keep you on their radar
Referral ask: reconnect → name the role → remind them of the relationship → give them an out
Avoid: "pick your brain" · "would love to connect" with no reason · attaching CV without dialogue
0 / 13 completed
1 / 13
You want to send a cold LinkedIn message to a senior DevOps recruiter at a company you'd like to work for. Which message is most likely to get a response?
Option B uses the cold message formula that consistently generates higher response rates: ① Use the recruiter's name — personalisation immediately signals this isn't a mass-send. ② Explain why this recruiter / this company — "I noticed you're hiring for DevOps roles at [Company]" shows you've done basic research. ③ One concrete credential — instead of listing everything on your CV, pick one achievement: a technology + a result. "5 years with Kubernetes and CI/CD — led a migration that cut deployment time by 40%." This is immediately interesting to a technical recruiter. ④ Soft call-to-action — "would you be open to a quick chat?" is low-friction. It doesn't demand anything and is easy to say yes or no to.
Cold message template (adapt this): "Hi [Name], I see [Company] is growing its [X] team. I've been working with [technology] for [N] years — most recently [specific achievement]. Would you be open to a brief call to discuss whether there's a fit?"
Option A is generic and passive. Option C is enthusiastic but vague — "culture fit" without evidence isn't compelling. Option D attaches a CV unprompted, which feels presumptuous before any dialogue.
2 / 13
A recruiter sends you an InMail about a Senior Backend Engineer role. You're genuinely interested. Which reply best moves the conversation forward?
Option B is the ideal recruiter InMail reply when you are interested because it: ① Responds promptly and warmly — "Thanks for reaching out!" signals you're engaged (recruiters track response rate and enthusiasm). ② Confirms you're open — "currently open to new opportunities" is the professional way to say "I want a new job" without appearing desperate. It also lets the recruiter use this in their notes. ③ Shows curiosity about the right things — asking about "the project and the team" rather than salary first shows professional maturity. ④ Proposes a concrete next step — "are you available for a call this week or next?" moves from message-thread to conversation, which is where real screening happens.
When responding to recruiter InMail (interested) — key signals to send: Express interest clearly · Mention you're open · Ask one thoughtful question · Propose / agree to a call · Keep it under 100 words
Option A is too short and transactional — it puts all the work back on the recruiter. Option C overwrites the reply with a CV summary — this is for a call, not a message thread. Option D creates unnecessary friction before even confirming interest.
3 / 13
A recruiter messages you about an opportunity but the timing is wrong — you just started a new role three months ago. Which reply is most professional?
Option C is the professionally recommended response for declining a recruiter while maintaining the relationship: ① Personal opener — using the recruiter's name signals this is a genuine reply, not a canned response. ② Gracious tone — "Thanks so much for thinking of me" is important. Recruiters remember candidates who are warm even when declining. ③ Brief honest reason — "just started a new role and want to give it proper time" is honest without oversharing. It frames the decline as a timing issue, not a rejection of the company. ④ Keeps the door open explicitly — "I'd love to stay on your radar" is the key phrase. It gives the recruiter a reason to keep your profile and reason to follow up. ⑤ Sets a timeline — "6–12 months" is specific and makes the follow-up actionable.
Not-now InMail reply formula: "Thanks for reaching out, [Name]. Timing is off for me right now — [brief reason]. That said, I'd love to stay on your radar for future opportunities. Feel free to reach back out [timeframe]!"
Option A is dismissive. Option B implies the recruiter has done something wrong. Option D is accurate but too long and formal — it reads like an excuse rather than a relationship-building reply.
4 / 13
You want to ask a former colleague (you haven't spoken to in 2 years) for a referral at their company. Which LinkedIn message is most appropriate?
Option B demonstrates how to ask for a referral without making it feel transactional or entitled: ① Reconnect naturally first — "hope you're doing well" is brief but human. Jumping straight to the ask (Options A, C) ignores the fact that this is a personal favour from someone you haven't spoken to recently. ② Mention the role specifically — "Senior iOS Engineer opening at [Company]" shows you've done your research. It also makes it easy for your contact to visualise the ask. ③ Reference a genuine memory — "I really respected working with you at [Previous Company]" re-establishes the relationship. It's not flattery — it's reminding them who you are and why you matter to each other. ④ Signal your current skill relevance — "I've been deep into SwiftUI and ARKit since then" quickly establishes that you're up-to-date on the technical stack. This helps your contact decide whether the referral makes sense. ⑤ Give them an easy out — "Totally understand if the timing isn't right" removes pressure and makes the ask feel low-stakes. This counterintuitively increases yes rates.
Referral request formula: Reconnect → Name the role → Remind them of the relationship → Signal skill fit → Make the ask → Give them an out
5 / 13
Which of the following is a strong rewrite of this weak LinkedIn networking message: "Hi, I saw that you work in tech and I was hoping we could connect. I would love to pick your brain and maybe you could share some advice."
Option C transforms the weak message with four targeted improvements:
What's wrong with the original message? ① "I saw that you work in tech" — too vague; shows no real research ② "pick your brain" — widely disliked phrase; implies the recipient's only value is giving away their time for free ③ "maybe you could share some advice" — no specific ask; forces the recipient to guess what you actually want ④ No indication of who you are or why they should care
Why Option C works: ① "I came across your profile while researching backend engineering at scale" — explains exactly how you found them and why you found them relevant ② "I really liked your post about distributed tracing" — shows you engaged with their content; they're a person, not just a job contact ③ "I'm a backend engineer with 4 years of experience exploring opportunities in observability tooling" — tells them who you are in one sentence; gives context for why this conversation makes sense ④ "Would you be open to a 15-minute chat?" — a specific, time-bounded, low-friction ask replaces the vague "pick your brain"
General rule: Specificity is the strongest signal of genuine intent in networking. Generic messages look like mass outreach; specific messages feel like real connection.
Phrases to avoid in networking:"pick your brain" · "synergise" · "circle back" · "I'm just reaching out to connect" (with no reason) · "I saw that you work in [broad field]"
6 / 13
You're reviewing a pull request submitted by Maria. The commit message reads: 'Fix: Improved error handling'. Maria has included a detailed code review comment suggesting further optimization for performance. Which response is the most constructive and professional way to respond?
This question tests your ability to respond effectively during a code review. Option A uses an inappropriate phrase and doesn't address the comment. Option B is irrelevant. Option C demonstrates active engagement, seeking clarification on Maria's changes and acknowledging her contribution, which is crucial for collaborative development. Option D dismisses the feedback without discussion.
7 / 13
You receive an email from a recruiter at Apex Solutions regarding a Lead Data Scientist role. The email states: 'Apex is seeking a highly motivated individual with extensive experience in machine learning and deep learning to join our growing team.' Which response best expresses your interest without immediately committing to an interview?
This question focuses on initial communication with a recruiter. Option A is a polite and professional response that requests further information, allowing you to assess the opportunity before committing. Option B is an appropriate expression of interest while maintaining control of the conversation. Options C and D are overly dismissive or immediately demanding.
8 / 13
You're crafting a LinkedIn update to announce your transition from a Senior Front-End Developer role at BetaCorp. You want to highlight your key skills and experience while subtly indicating your interest in exploring new opportunities. Which of the following updates is most effective?
This assesses your ability to present yourself professionally on LinkedIn. Option A is a well-rounded update highlighting key skills and expressing openness to connections - it's subtly signaling interest without explicitly stating you're looking for a job. Options B and C are too brief or direct, while option D is overly demanding.
9 / 13
David, a recruiter at StellarTech, sends you this Slack message: 'Hey! Just wanted to check if you're still looking for roles. Heard some interesting things about our new microservices architecture.'
You're currently exploring opportunities in distributed systems. Which response is most effective?
The best response seeks clarification. David's message is vague and potentially pushy. Asking for elaboration demonstrates interest without immediately committing to a conversation. Options A and B are either too enthusiastic or dismissive; option D is overly blunt and could damage the connection.
10 / 13
Elena, a recruiter at QuantumLeap Solutions, messages you on LinkedIn: 'Hi [Your Name], I came across your profile and noticed your experience with React.js. We're looking for a Frontend Engineer.'
Which reply best leverages this initial contact?
Elena has identified a shared skill (React.js), so it's crucial to acknowledge this and move the conversation forward. Asking for more details shows genuine interest in the role and allows you to assess its suitability. Option A is unprofessional; option C misrepresents your skills; and option D shuts down the opportunity.
11 / 13
Mark, a recruiter at Innovate Dynamics, contacts you about a Software Engineer position. He says: 'We need someone who can quickly pick up our legacy codebase.'
Which response is the most appropriate given your situation – you've been working on modern cloud-native applications for the past five years?
Honesty and a willingness to learn are key in networking. While your experience isn't directly relevant to legacy systems, expressing openness to learning demonstrates adaptability. Option A is dismissive; option C focuses on the recruiter's needs rather than yours; and option D is inappropriate at this stage.
12 / 13
Sarah, a former colleague who now works at TechForward Inc., messages you on LinkedIn: 'Hey [Your Name]! Long time no see. I'm hiring for a Senior Data Engineer and thought of you immediately.'
Which message is the MOST appropriate to send back?
Sarah initiated contact and expressed interest. A direct request for information is perfectly acceptable and shows you value her offer. Option A suggests a casual meeting without confirming the role; option C declines the opportunity prematurely; and option D is incredibly unprofessional.
13 / 13
You're writing a PR description for LinkedIn to announce your move from Lead DevOps Engineer at CloudSolutions to Principal Architect at NovaTech. You want to emphasize your expertise in automation and cloud infrastructure.
Which sentence is the MOST effective?
Specificity is key in professional networking. Directly stating your expertise (automation and cloud infrastructure) immediately highlights your value proposition. Options A and B are too generic; option C focuses on personal growth rather than your contributions, and option D lacks impact.
What does "LinkedIn & Recruiter Networking in English — Practice for IT Professionals" cover?
Practice LinkedIn networking English: cold recruiter messages, responding to InMail, asking for referrals, and rewriting weak networking messages. 5 exercises for IT professionals.
How many questions are in this interview set?
This set has 13 exercises, each with a full explanation.
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.
Do these exercises include model answers?
Yes. Each interview question gives you several possible responses and asks you to pick the one that communicates most clearly and completely — the explanation then breaks down exactly why that answer works, including the specific vocabulary a strong candidate would use.
What if I choose an answer that isn't the strongest one?
You'll see which option was correct and read a full explanation of why it's stronger than the alternatives, plus the key vocabulary and phrasing worth reusing in a real interview.
Can I retry the questions?
Yes — use the "Try again" button on the results screen to reset and go through the set again.
Is this the same as a real technical or behavioural interview?
No — it's focused practice for the language side of interviewing: recognising which phrasing sounds precise and confident versus vague, and knowing the vocabulary interviewers expect for this role. It won't replace mock interviews, but it builds the vocabulary you'll need in one.
Where can I find interview prep for other roles?
Browse the full Interview exercises hub for 170+ modules covering behavioural, technical, and system design rounds across dozens of IT roles, or check the "Next up" link below to continue.
Do I need an account, and is my progress saved?
No account is needed. Progress is tracked only for your current visit — reloading or leaving the page resets the counter.
Who writes these interview questions?
Every question is written by the CoderSlingo team based on real technical interview patterns for this role, then reviewed for accuracy and clarity.