5 exercises — how to write effective LinkedIn messages in job search contexts: connection requests, responding to recruiters, referral requests, rewriting weak messages, and handling vague InMails.
LinkedIn message golden rules
Personalize always — no generic "join my network" requests
Be specific — name the role, mention shared context, give a real reason
Ask for one thing — don't pile multiple asks in one message
Never share your CV unsolicited — wait until asked
Low-commitment ask — "15-minute call?" beats "can we talk?"
Protect your data — don't share salary / phone number in first messages
0 / 22 completed
1 / 22
You want to connect with a senior engineer at a company you'd like to work for. The LinkedIn connection request note has a 300-character limit. Which message is most effective?
LinkedIn connection request — what works and why
The default message ("join my network") is ignored by most professionals. A personalized note immediately sets you apart.
Why option B is best: ✅ Addresses the person by name (personalizes immediately) ✅ Shows specific research — mentions a real talk/post ✅ States who you are in one sentence ✅ Gives a clear, reasonable reason to connect ✅ Fits within the 300-character limit
Problems with the others: ❌ Option A: Generic — could be sent to anyone; gives no reason to accept ❌ Option C: Way over 300 characters; lists skills instead of building connection; sounds like a spam application ❌ Option D: Asks for a job immediately — transactional and presumptuous on first contact
Template structure for a good connection request: "Hi [Name], [specific reason you know them / common ground]. I'm a [role] interested in [relevant area]. Would love to connect."
Key principle: Give before you ask. Show genuine interest in them first.
2 / 22
A recruiter sends you a LinkedIn InMail about a Senior DevOps role. You're interested but currently in your notice period — you can start in 3 weeks. Which reply is most professional?
Responding to recruiter InMail — best practices
Recruiters send many InMails. A professional, clear response that addresses their main question (availability) gets a quick, positive reply.
Why option A is best: ✅ Acknowledges the message warmly but briefly ✅ States clearly you're interested (answers their primary question) ✅ Gives concrete timeline information proactively ✅ Asks a clarifying question to move the conversation forward ✅ Professional tone — not too formal, not too casual
Problems with the others: ❌ Option B: Brushes them off unnecessarily — 3 weeks is a very short wait, not months ❌ Option C: Claims to be "available immediately" when you aren't — dishonest; also jumps straight to salary before a conversation is established ❌ Option D: Sharing your phone number publicly in a message is a privacy risk; "ASAP" sounds demanding
Key vocabulary for job-search LinkedIn messages: • "I'm currently serving my notice period" or "I'm wrapping up my current role" • "I'd be available from [date]" — specific dates are better than "in a few weeks" • "Would that timeline work for your process?" — invites them to continue the conversation • "Happy to discuss further" / "I'd welcome a call" — professional next step offers
3 / 22
You want to ask a former colleague to refer you internally at their current company. They worked with you on a project 2 years ago. Which message is best?
Referral request — getting it right
Asking for a referral is sensitive. You're asking someone to put their name behind you. The right message makes it easy to say yes.
Why option A is best: ✅ Warm opener — reconnects genuinely before the ask ✅ Mentions the specific role (reduces work for them) ✅ References specific shared work — shows it's not a mass message ✅ Frames the referral as their honest judgment ("if you think so") — reduces pressure ✅ Explicit "no pressure" — makes it easy to decline gracefully ✅ Conversational LinkedIn tone — not stiff, not too casual
Problems with the others: ❌ Option B: No context, "urgency" makes it about your needs, not the opportunity ❌ Option C: Overly formal for LinkedIn — reads like a legal letter; impersonal ❌ Option D: Too many vague questions; asking them to forward your CV is overstepping on first contact
Referral etiquette checklist: • Reconnect briefly before the ask • Name the specific role clearly • Remind them of your shared context • Give them an easy way to say no • Don't ask more than one favor at a time • Follow up with a thank-you regardless of their answer
4 / 22
Rewrite this weak LinkedIn message to make it stronger:
"Hello. I am a developer. I want to work at your company. Can we talk?"
Which rewrite is most effective?
The anatomy of a strong LinkedIn message
The original message ("Hello. I am a developer. I want to work at your company. Can we talk?") fails on every dimension: no specifics, no shared context, no value to the reader.
Why option A is best: ✅ Names the person ✅ Gives a specific role and concrete skills (not just "developer") ✅ Shows research into the company's specific work ✅ Connects your interest to your skills — relevant fit ✅ Makes a specific, low-commitment ask (15 minutes) instead of "can we talk?"
Problems with the others: ❌ Option B: All buzzwords ("highly motivated", "results-driven", "passion for innovation") — meaningless, sounds like a form letter ❌ Option C: Asks "are you hiring?" — recruiter/connection can't know this; go to the careers page instead ❌ Option D: Overly formal, possibly AI-generated corporate letter tone — wrong register for LinkedIn messages
The "I-you-we" principle for networking messages: • Mention them first (what caught your attention about their work) • Then tell them who you are (one specific sentence) • Then suggest what we could do (a clear, low-friction next step)
5 / 22
A recruiter sends you this InMail: "Hi — I saw your profile and I think you'd be great for a role. We're not able to share details publicly yet, but it's at a top tech company. Interested?" What is the most professional and safe reply?
Responding to vague recruiter InMails
Recruiters sometimes send vague InMails to gauge interest before revealing the client company. This is standard practice — but you should ask for basic details before committing.
Why option B is best: ✅ Polite and professional tone ✅ Asks for minimum required information to make a decision ✅ Doesn't commit to anything yet ✅ Leaves the door open ("generally open to the right opportunity") — positive signal without over-committing ✅ No private information shared yet
Problems with the others: ❌ Option A: "Ready to interview whenever" before knowing the role, salary, or company — over-commitment with no information ❌ Option C: Unnecessarily dismissive — vague first messages are common; politely asking for details is the professional response ❌ Option D: Never share your CV in a LinkedIn message before you know who you're talking to (spam risk, data privacy). Never volunteer current salary in a first message — it reduces your negotiating position
Information to ask for in a first reply: • Role title and level (Senior, Staff, Lead?) • Company name (or sector if under NDA) • Location / remote policy • Salary range (you can ask politely)
"I'd like to understand the role better before moving forward — could you share the role title and whether there's flexibility on location?"
6 / 22
Sarah: "Hey Mark, just finished the latest pull request. A few minor style issues – mostly around whitespace and naming conventions. Let's discuss these in detail when you have a moment."
The key here is framing your response effectively when receiving code review feedback. Option A is dismissive and doesn't acknowledge the need for discussion. Option B is passive and lacks initiative. Option C accurately describes an ideal response – it's specific, invites collaboration, and shows you're taking the feedback seriously. Option D overstates the level of detail expected in a simple message, focusing on immediate action rather than initiating a conversation.
7 / 22
David: 'Hey team, just finished implementing the new API endpoint. I've added extensive logging for debugging purposes and have included unit tests covering all critical scenarios. It's deployed to staging and seems stable so far. Let me know if you spot any issues.'
Which of the following LinkedIn messages would David use to follow up with the team lead, Emily, after sharing this update?
This scenario focuses on clear communication after sharing technical updates. Option A is too abrupt and doesn't encourage further discussion. Option B is a reasonable follow-up but lacks specific requests for information. Option C correctly prompts David to provide critical details needed for effective monitoring, demonstrating proactive communication and knowledge sharing – crucial in IT. Option D, while not incorrect, is overly cautious and doesn't leverage the existing update effectively.
8 / 22
David wants to share his API endpoint update with the team lead, Emily, via LinkedIn. He needs to craft a concise and informative message that encourages discussion. Which of the following messages would be most appropriate?
Option B is the most effective because it clearly states what David accomplished (implementing the API), highlights key features (extensive logging, unit tests) and provides a specific location for review (staging). The other options are either too informal (A), too vague (C), or lack crucial details about deployment and testing. It's important to frame updates in terms of value – David is communicating that his work benefits the team through improved debugging and validation.
9 / 22
Sarah: "Hey Mark, just finished the latest pull request. A few minor style issues – mostly around whitespace and naming conventions. Let's discuss these in detail when you have a moment."
The key here is framing your response effectively when receiving code review feedback. Option A is dismissive and doesn't acknowledge the need for discussion. Option B is passive and lacks initiative. Option C accurately describes an ideal response – it's specific, invites collaboration, and shows you're taking the feedback seriously. Option D overstates the level of detail expected in a simple message, focusing on immediate action rather than initiating a conversation.
10 / 22
David: 'Hey team, just finished implementing the new API endpoint. I've added extensive logging for debugging purposes and have included unit tests covering all critical scenarios. It's deployed to staging and seems stable so far. Let me know if you spot any issues.'
Which of the following LinkedIn messages would David use to follow up with the team lead, Emily, after sharing this update?
This scenario focuses on clear communication after sharing technical updates. Option A is too abrupt and doesn't encourage further discussion. Option B is a reasonable follow-up but lacks specific requests for information. Option C correctly prompts David to provide critical details needed for effective monitoring, demonstrating proactive communication and knowledge sharing – crucial in IT. Option D, while not incorrect, is overly cautious and doesn't leverage the existing update effectively.
11 / 22
David wants to share his API endpoint update with the team lead, Emily, via LinkedIn. He needs to craft a concise and informative message that encourages discussion. Which of the following messages would be most appropriate?
Option B is the most effective because it clearly states what David accomplished (implementing the API), highlights key features (extensive logging, unit tests) and provides a specific location for review (staging). The other options are either too informal (A), too vague (C), or lack crucial details about deployment and testing. It's important to frame updates in terms of value – David is communicating that his work benefits the team through improved debugging and validation.
12 / 22
Sarah: "Hey Mark, just finished the latest pull request. A few minor style issues – mostly around whitespace and naming conventions. Let's discuss these in detail when you have a moment."
The key here is framing your response effectively when receiving code review feedback. Option A is dismissive and doesn't acknowledge the need for discussion. Option B is passive and lacks initiative. Option C accurately describes an ideal response – it's specific, invites collaboration, and shows you're taking the feedback seriously. Option D overstates the level of detail expected in a simple message, focusing on immediate action rather than initiating a conversation.
13 / 22
David: 'Hey team, just finished implementing the new API endpoint. I've added extensive logging for debugging purposes and have included unit tests covering all critical scenarios. It's deployed to staging and seems stable so far. Let me know if you spot any issues.'
Which of the following LinkedIn messages would David use to follow up with the team lead, Emily, after sharing this update?
This scenario focuses on clear communication after sharing technical updates. Option A is too abrupt and doesn't encourage further discussion. Option B is a reasonable follow-up but lacks specific requests for information. Option C correctly prompts David to provide critical details needed for effective monitoring, demonstrating proactive communication and knowledge sharing – crucial in IT. Option D, while not incorrect, is overly cautious and doesn't leverage the existing update effectively.
14 / 22
David wants to share his API endpoint update with the team lead, Emily, via LinkedIn. He needs to craft a concise and informative message that encourages discussion. Which of the following messages would be most appropriate?
Option B is the most effective because it clearly states what David accomplished (implementing the API), highlights key features (extensive logging, unit tests) and provides a specific location for review (staging). The other options are either too informal (A), too vague (C), or lack crucial details about deployment and testing. It's important to frame updates in terms of value – David is communicating that his work benefits the team through improved debugging and validation.
15 / 22
Sarah: "Hey Mark, just finished the latest pull request. A few minor style issues – mostly around whitespace and naming conventions. Let's discuss these in detail when you have a moment."
The key here is framing your response effectively when receiving code review feedback. Option A is dismissive and doesn't acknowledge the need for discussion. Option B is passive and lacks initiative. Option C accurately describes an ideal response – it's specific, invites collaboration, and shows you're taking the feedback seriously. Option D overstates the level of detail expected in a simple message, focusing on immediate action rather than initiating a conversation.
16 / 22
David: 'Hey team, just finished implementing the new API endpoint. I've added extensive logging for debugging purposes and have included unit tests covering all critical scenarios. It's deployed to staging and seems stable so far. Let me know if you spot any issues.'
Which of the following LinkedIn messages would David use to follow up with the team lead, Emily, after sharing this update?
This scenario focuses on clear communication after sharing technical updates. Option A is too abrupt and doesn't encourage further discussion. Option B is a reasonable follow-up but lacks specific requests for information. Option C correctly prompts David to provide critical details needed for effective monitoring, demonstrating proactive communication and knowledge sharing – crucial in IT. Option D, while not incorrect, is overly cautious and doesn't leverage the existing update effectively.
17 / 22
David wants to share his API endpoint update with the team lead, Emily, via LinkedIn. He needs to craft a concise and informative message that encourages discussion. Which of the following messages would be most appropriate?
Option B is the most effective because it clearly states what David accomplished (implementing the API), highlights key features (extensive logging, unit tests) and provides a specific location for review (staging). The other options are either too informal (A), too vague (C), or lack crucial details about deployment and testing. It's important to frame updates in terms of value – David is communicating that his work benefits the team through improved debugging and validation.
18 / 22
Mark, a senior engineer, sends you this LinkedIn message: 'Hey @JohnDoe, saw your work on the Phoenix project. Interested in exploring opportunities at NovaTech?'. What's the MOST appropriate response to maintain professional boundaries and politely decline without dismissing his interest?
This scenario tests responding to an unsolicited connection request. Option A is the best as it politely acknowledges interest while firmly stating your current focus. Options B and C are too forward, suggesting a discussion without proper vetting. Option D is overly casual and doesn't clearly decline.
19 / 22
You need to inform your team lead, Lisa, about a critical bug you discovered in the new authentication service via LinkedIn. The message should be concise and actionable. Which of the following is the MOST effective option?
This tests conveying urgency and providing specific details. Option 1 clearly states the issue's severity and the need for immediate action, aligning with professional communication expectations. Options B is too vague; option 3 lacks any information about the problem, while option 4 is completely irrelevant.
20 / 22
You've spent weeks developing a new microservice for data processing. Before announcing it to the team, you want to gauge initial reactions and gather feedback. Which LinkedIn message would be most suitable for initiating this discussion?
This focuses on collaborative communication. Option 1 is overly enthusiastic and promotional. Option 2 directly invites feedback and encourages discussion. Options B and C are too informal and lack specifics about the microservice.
21 / 22
During a daily standup, David mentions he's deployed a new feature to production but experienced minor latency issues. He wants to quickly inform Emily, the team lead, via LinkedIn. Which message would be most appropriate?
This assesses conveying technical information concisely and proactively. Option 1 downplays the issue, while option 3 is irrelevant. Option 2 clearly states the deployment, identifies the problem (latency), and indicates ongoing monitoring – crucial for a team lead's awareness.
22 / 22
You are a DevOps engineer and need to update your LinkedIn profile with details about automating the deployment process for a critical application. Which of the following statements would be MOST effective in describing this accomplishment?
This tests quantifying achievements and using technical language. Option 1 is vague. Option 2 provides specific details about the tools used (Jenkins), the measurable impact (30% reduction in release times), and the benefit (minimizing errors) – showcasing your value to a potential employer.
What does the "LinkedIn Messages for IT Professionals — Exercise Set" exercise cover?
Practice professional LinkedIn communication: connection requests, responding to recruiters, referral requests, and rewriting weak messages. 5 exercises with templates and explanations.
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 "LinkedIn Messages for IT Professionals — Exercise Set"?
This exercise has 22 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.