# How to message prospects who share job openings
> Turn shared job posts into B2B sales leads: name the business pain the new hire is meant to fix, then offer a practical fix before the role is filled.
- HTML: https://getkinlead.com/message-prospects-who-share-job-postings
- Markdown: https://getkinlead.com/message-prospects-who-share-job-postings.md

**Short answer:** Don't ask for a referral when someone shares a job opening. Name the business pain that created the vacancy and explain how you solve it. Message the person who shared the post, since they're often a peer or manager already feeling the problem the new hire is meant to fix.

## Identify the real problem behind the job post

Most people see a job post and think about the vacancy. To sell, think about the gap. A job opening is a public admission that a company has a problem it can't solve with its current headcount, and that admission is usually written down in more detail than any discovery call you'd get.

Hiring managers are flooded with resumes and ignore cold messages. The person sharing the post is often a peer or a cross-functional lead, the one doing the extra work or absorbing the inefficiency the new hire is supposed to fix. They feel the problem today, not in three months when the role is filled. That makes them a warmer reader than the person who will eventually interview candidates.

A company hiring a Head of Demand Gen is usually struggling with lead volume or quality. A company hiring a DevOps Engineer has developers tired of slow deploys and manual errors. Read the role as a symptom and you have something to say that isn't about your product at all.

**The job seeker approach**

- Who is the hiring manager for this role?
- I'm interested in this position, can you refer me?
- I see you're hiring, I'd love to apply.

**The partner approach**

- Usually when a team hires for this, it's because the current process is too manual.
- I imagine the team is feeling the pressure of [specific pain] while you search for this person.
- Most companies hiring for this role are struggling with [specific outcome].

## Read the job description for pain

You can't guess the pain. Find it in the text of the job description. The responsibilities and requirements sections map out what is broken or missing right now, written by someone who has been living with it for months.

Look for verbs that signal a struggle. Scale, fix, rebuild, own, clean up, bring structure to. Each one points at a business problem you can name in the first line of a message. A post that says 'build the outbound function from scratch' tells you nobody owns outbound today, which means pipeline is probably coming from referrals and luck.

Write the pain down in one sentence before you write the message. If you can't, you don't have a hook yet and the message will read like every other pitch in their inbox.

1. **Find the action verbs.** Scan the post for phrases like 'optimize lead flow', 'reduce churn' or 'own the reporting stack'.
2. **Translate task to pain.** If they need to 'scale lead gen', the pain is that they aren't getting enough leads right now.
3. **Identify the chaos.** If the post says 'build from scratch', the pain is that they have no process and things are likely messy.
4. **Match it to your value.** Connect that chaos or lack of volume to the one thing your product actually fixes.

## Write the first message

Keep it short and about their situation. No company history, no long introduction, no praise about their growth. They posted a job, not an announcement, and they're reading your message between interviews.

Open with the post, name the pain, offer the value, end with a low-friction ask. The goal is a reply. Booking a call comes later, once they've told you the problem in their own words.

- **you:** Hi Sarah, saw you shared that opening for a Head of Demand Gen. Usually when a team is hiring for that, it's because the current lead flow is too manual or inconsistent.
- **them:** That's an understatement. We're spending 20 hours a week just cleaning lists.
- **you:** That's exactly why I reached out. We take the sourcing and list work off the team so the new hire can start on strategy instead of cleanup. Worth a short chat while you're still searching?

> Keep the first message under 50 words. If they have to scroll to read your pitch, they'll archive it.

```
Hi {first name}, saw you shared the {role} opening. Teams hiring for that usually have {pain} piling up while they search. We take {pain} off the team's plate so the new hire starts on {outcome} instead of cleanup. Worth a short chat?
```

## What if the person who posted is the hiring manager

Sometimes the poster owns the problem directly, like a VP of Sales posting for an SDR manager. That's a better lead. The message just changes.

Skip the 'I saw you're hiring' framing and speak to the outcome the hire is meant to deliver. They already know the role is open. What they don't know is that you've watched other teams in the same spot and can tell them what happened next.

- Name the outcome, not the role. 'Getting the new SDR manager to quota faster' beats 'your SDR manager search'.
- Offer something useful during the search, like what other teams handed their first sales manager in the first 90 days.
- Ask about timing. If the role starts next month, the pain is live right now and they'll talk.
- Don't pitch a replacement for the hire. Pitch the thing that makes the hire work.

## Avoid these mistakes

The biggest mistake is sounding like a candidate. Once you ask about the hiring manager or the application process, you're filed as a job seeker and the conversation is over. You lose your standing as a business partner in one sentence.

The second mistake is vague praise. Telling someone they're growing fast or have a great culture signals a template. They've read that line before, from people who never looked at the business.

A third is sending a deck or a calendar link in the first message. Neither answers the question in their head, which is whether you understand why they're hiring.

| | Mistake | Result |
| --- | --- | --- |
| Asking for the hiring manager | You look like a job seeker, not a partner. |
| Sending a pitch deck immediately | Immediate archive or mark as spam. |
| Using vague praise | Prospect knows it's a generic message. |
| Pitching a replacement for the hire | Sounds like you didn't read the post. |

## What to do when they reply

A reply is not a meeting. Treat the first reply as the start of a conversation about the problem, and keep the product out of it until they ask. The person who complains about list cleaning for two messages is the person who books the call themselves.

1. **Ask one question about the problem.** 'How much of that list cleaning is landing on the team right now?' keeps them talking and gives you the language to use later.
2. **Give a specific example.** 'A 40-person agency had the same gap and moved sourcing to a part-time contractor until the hire started.' Concrete beats a claim.
3. **Offer the call when they describe the pain.** Once they've said the problem in their own words, ask for 15 minutes. Before that, you're guessing.
4. **Note the start date.** If the role begins in six weeks, set a reminder. The pain gets worse right before the hire lands, and that's when they'll want help.

## Doing this with Kinlead

Finding the people who share these posts by hand is slow, and the good ones are buried in comment threads. Kinlead finds people on LinkedIn who match a customer profile you describe, or your website, and scores each lead from 0 to 100 against it. Leads below the fit line are not kept.

The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented, so you know which opening they were reacting to.

1. **Set up the agent.** Point it at the company pages and profiles where your buyers post about hiring.
2. **Write the playbook.** Add your own sales script as the playbook so the AI connects the role in the post to your product's value.
3. **Launch the campaign.** Connection notes are AI-written, under 200 characters, and open with why that person became a lead.
4. **Handle replies.** Replies from every campaign land in one [unified inbox](/features/unified-inbox), classified by intent, with interested replies first.

## Related

- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)

## Common questions

**Should I connect first or send a message?**

Send a connection request with a short note. A message without a connection often lands in the Other tab or needs InMail, which feels too formal for a conversation about a job post.

**What if the person sharing the post is a recruiter?**

Recruiters rarely feel the operational pain. Pivot to how your product makes the new hire productive sooner or helps the company hit the goal behind the role.

**How many follow-ups should I send if they don't reply?**

Two. The first can be a specific example of a similar company with the same problem. The second can close the loop politely so you're not left hanging.

**What if the role is already filled by the time I message?**

Ask how the first month went. New hires surface the same problem the job post described, and the person who shared the post usually has an opinion about it.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
