# How to qualify leads using job postings
> Use job descriptions to find a company's exact pain points and use those insights to write LinkedIn outreach scripts that actually get replies.
- HTML: https://getkinlead.com/qualifying-leads-by-job-description
- Markdown: https://getkinlead.com/qualifying-leads-by-job-description.md

**Short answer:** Find companies hiring for roles that fix the problem your product solves. Read the responsibilities and requirements to find the pain they're paying a salary to solve, then use their own language in your first message.

## Start with roles that signal a real problem

Some job posts tell you nothing. A company hiring a general marketing manager might be replacing someone who left, and the seat stays the same. Others are a public statement that something is broken. You want the second kind.

Builder roles are the strongest signal. When a company hires a Head of Revenue Operations or an Implementation Lead, the post usually describes a process that doesn't exist yet. They're paying a salary to create it, which means there's budget and a deadline attached.

Second hires matter too. If a company adds a second person to a role that one person handled, the workload has outgrown the process behind it. They feel the pressure of scale and will read a message about removing manual work.

**Roles that tell you little**

- Marketing Manager, no context in the post
- Operations Associate, admin duties only
- Account Executive, standard quota language

**Roles that name a problem**

- Head of Revenue Operations, "rebuild funnel reporting"
- Demand Generation Lead, "own the pipeline number"
- Customer Success Architect, "cut churn in mid-market"

## Read the responsibilities for the confession

A job description is a public list of what a company lacks. Skip the title and read the responsibilities. That section is where the hiring manager describes work they can't get done today.

Look for verbs that admit a problem: fix, rebuild, reduce, clean up, consolidate, automate, replace. "Rebuild the lead routing logic" means routing depends on spreadsheets and one person's memory. "Consolidate reporting across three tools" means nobody trusts the numbers.

1. **Read the responsibilities twice.** The first pass gives you the list of duties. The second pass is for the words that describe a broken state, which is where you find the sentence you'll quote.
2. **Check the requirements for the stack.** If the post lists four tools that do the same job, they have a fragmentation problem. If it lists one legacy tool plus an integration, they're mid-migration and feeling it.
3. **Find the metric.** "Cut time to onboard from 30 days to 10" is the number the hiring manager is judged on. Put it in the message and you sound like a colleague.
4. **Note the start date.** "Start immediately" or "as soon as possible" means the pain is here now. A post for next quarter is a note for later.

> Write the pain in one sentence before you write the message: they need someone to do X because Y is broken. If you can't fill in both blanks, the post isn't a lead yet.

## Find the postings and pick who to message

LinkedIn Jobs search covers most of what you need. Search the role title, filter by company size and location, and sort by date. Company career pages catch the roles that never reach LinkedIn, and a saved Google alert on a careers URL catches them early.

Send to one person per company first. Three messages to the same company on the same day looks like a mail merge.

- The hiring manager: the director or VP the role reports to. They wrote the post and hold the budget.
- The peer: whoever does that job today, often the founder in a company under 50 people.
- The adjacent owner: the ops or RevOps lead who has to integrate whatever the new hire buys.

## Map the post to your offer

Turn the pain into an angle. The hire is evidence of the problem. Your product is one way to solve it before the new person starts, or to make that person's first quarter easier.

Lead with what the hire implies. "You're standing up an outbound function" says more than "I saw your job post". The first is a statement about their business, the second is a statement about your morning.

| | Job post phrase | Implied pain | Angle for your message |
| --- | --- | --- | --- |
| Manage 50+ lead sources manually | Overwhelmed by manual data entry | Fifty sources is a lot of copy and paste. We take that step out so the new hire starts on analysis. |
| Fix fragmented data across platforms | Nobody trusts the reporting | Fragmented data usually means two teams quoting two numbers. We sync them into one view. |
| Scale outreach from 10 to 100 calls a week | The current process breaks at volume | Going from 10 to 100 calls breaks most setups. We hold the volume without the spreadsheets. |

## Write the first message

Three sentences is enough. Show you read the post, name the problem it implies, and offer one small next step. Skip the paragraph about your company.

- **you:** Hi Sarah, you're hiring a Head of Growth to build outbound from scratch. That usually lands on one person doing manual prospecting between strategy calls. We handle the prospecting part so the new hire spends week one on the plan. Open to 15 minutes Thursday?
- **them:** That's roughly where we are. I'm covering it myself until someone starts. How does it work?
- **you:** You describe the customer you want, it finds matching people on LinkedIn and runs the first message from your account. Thursday at 10 works if that suits.

```
Hi {{first_name}}, you're hiring a {{role}} to {{outcome from the post}}. In teams that size, {{implied pain}} usually lands on one person. We {{what you do in one line}} so {{result}}. Worth 15 minutes?
```

## Follow up without sounding like a recruiter

Postings stay live for weeks, so the signal holds. Two follow-ups a week apart cover most of the window. Each one adds something: a similar company you helped, an observation about the role, or a simpler ask.

When someone says the role is filled, ask who took it over and what they're tackling first. That answer is the same pain with a name attached.

Keep volume modest. LinkedIn doesn't publish invite or message limits, so watch your acceptance rate and slow down when it drops.

> A filled role still leaves you a lead. The person who took it over has the problem the post described, and nobody has written to them about it yet.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe and scores each lead from 0 to 100 against that profile, so the hiring manager and the peer arrive ranked before you write anything. Leads below the fit line are not kept.

Import a CSV of profile URLs from the companies you found, or run a search, and keep them in a lead group. Put your job-post angles into the campaign's sales playbook and the AI writes the first message from the goal, tone and your script. Connection notes can open with why that person became a lead, under 200 characters.

Replies from every campaign land in one inbox classified by intent, with an email when someone answers. Set a campaign to hand the conversation to you at the first reply, or let the AI keep going until a meeting is booked. Pro costs $99 a month after a 7-day free trial, and there's a [minimum booking guarantee](/minimum-booking-guarantee) if you want the terms in writing. [Start here](/signup) when your list is ready.

## Related

- [Find leads with AI](https://getkinlead.com/tools/find-leads.md)
- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Lead scoring for niche markets](https://getkinlead.com/ai-lead-scoring-for-niche-markets.md)

## Common questions

**Should I message the hiring manager or the person doing the job today?**

Message the person who owns the outcome. For a junior or mid-level role that's the director above it. For a leadership role it's usually the founder or CEO.

**What if the posting is a month old?**

Still useful. A live post after 30 days means they haven't found the fix, so the pressure has grown. Check the date before you write so you don't congratulate them on a hire they already made.

**Does mentioning the job post feel intrusive?**

No, as long as it's a bridge to a business problem. One clause about the role, then the problem it implies. People notice when you've read their actual post instead of a template.

**What if they post the same role every quarter?**

That pattern points to a process problem the role can't fix on its own. Lead with what keeps breaking rather than the person they're trying to hire.

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