# Finding and messaging developers on LinkedIn
> How to find developers on LinkedIn using competitor comments and technical signals, then write first messages they will actually answer today.
- HTML: https://getkinlead.com/linkedin-outbound-for-api-products
- Markdown: https://getkinlead.com/linkedin-outbound-for-api-products.md

**Short answer:** Find developers by reading the comments under competitor posts, not by filtering job titles. Engineers describe what breaks in their own words there, and that sentence becomes your opening line. Send something useful first, like a snippet, a doc page or a fix, and ask for a call only after they have used it.

## Start with the person who feels the problem

Most founders aim at the CTO. The CTO signs the contract, but someone else spends a week inside your docs before that happens. If the staff engineer running the migration hates your SDK, the deal stalls and nobody tells you why.

The person you want has a ticket open right now. They are wiring a webhook, fighting a rate limit, or explaining to their manager why the current vendor's latency is a problem. Titles to look for: staff engineer, principal engineer, platform engineer, DevOps lead, backend engineer at a company small enough that people pick their own tools.

Company size matters more than title. At a 15-person startup the engineer often holds a company card. At a 2,000-person company the same title has a procurement process in front of them and no authority to try anything new this quarter.

**Too broad to write to**

- CTO at a 50-person SaaS company
- VP of Engineering
- Software engineer, any company, any stack

**Specific enough to open a message**

- Staff engineer whose profile mentions a Kubernetes migration this year
- Platform engineer posting about Postgres connection pooling
- Backend lead at a 30-person company that just posted a job for a second DevOps hire

## Find developers in competitor comment threads

Developers do not announce that they are shopping for an API. They do argue in the comments under a competitor's release post about why the new feature misses their case. That argument is the signal.

Open the company pages of five to ten tools that sit next to yours in a stack. Read the comments on their last month of posts. You want people explaining a limitation in their own words, or asking a question the social media manager cannot answer and the engineers never reply to.

Some posts have no comments at all. Skip those. A thread with three engineers disagreeing about pagination is worth more than fifty posts with likes and nothing else.

1. **List the tools your buyer already runs.** Write down five to ten products that would appear in the same architecture diagram as yours. Follow their company pages from your own account.
2. **Read the comments, not the posts.** The post is marketing. The comments are where someone writes 'this breaks when you paginate past 10k rows'.
3. **Copy their exact words.** Save the sentence they wrote. Their phrasing becomes the first line of your message, and that is the only personalization that matters to an engineer.
4. **Check that they can buy or block.** Open the profile. You want an engineer at a company in your size range, not a developer advocate at a vendor and not another seller.
5. **Group them by problem, not by company.** Everyone who mentioned the same limitation goes into one list. One message per problem beats one message per industry.

## Write a first message that gets past a developer's filter

Engineers read LinkedIn messages the way they read recruiter mail. Two lines in, they decide whether you understand their job. Anything that sounds like a brochure gets closed.

Skip the compliment about their impressive background. Open with the thing they wrote, then say what you did about it. If you have a snippet, a doc page or a repo that answers their question, send that before you mention your product.

Do not ask for a call in the first message. Ask nothing, or ask whether they want the link. The call happens after they have used the thing you sent.

**Reads like a pitch**

- Hi Sarah, I came across your impressive profile and wanted to reach out about our platform, which helps engineering teams do more with less.
- Hi Sarah, quick question, do you have 15 minutes this week to discuss how we can help your team scale?

**Reads like a person who has the same problem**

- Hi Sarah, you mentioned Acme's Python SDK timing out on long polls. We hit that last spring and wrote a retry wrapper to get around it. Want the link?
- Hi Sarah, saw your comment about Postgres connection limits. We ended up pooling at the app layer instead. Happy to share what broke and what didn't.

- **you:** Hi Sarah, you commented on Acme's post about their Python SDK timing out on long polls. We hit the same wall last spring. I have the retry wrapper we wrote to get around it, want me to send it over?
- **them:** Yeah, send it. We've been retrying blindly for two weeks.
- **you:** Here it is: github.com/example/retry-wrapper. It's 40 lines and not pretty. If you'd rather not maintain it yourself, I build a queue that handles this natively, docs are at example.dev/docs. No call needed unless you want one.
- **draft:** Follow-up if they go quiet for a week: 'Did the retry wrapper hold up? We added a backoff table to it after a customer hit a thundering herd on reconnect.'

> Open with what they wrote, not with what you sell. If the first sentence could go to anyone else on your list, rewrite it.

## Make your own profile worth a reply

Before you send anything, a developer will open your profile. They are checking whether you are an engineer, a seller or a recruiter. The page answers that in about four seconds, and the answer decides whether your message gets read.

- Headline says what you build and for whom. 'Building a managed queue for Node backends' beats 'Founder | Visionary | Speaker'.
- Feature one technical post. A short write-up of a bug you fixed in your own product does more than a list of awards.
- Link the docs, not the pricing page. Developers click docs first and bounce if they land on a form.
- Use a real photo and your actual name. Stock imagery and titles like 'Growth Ninja' read as spam.
- Post once a week about a problem your users hit. The comments on your own posts are a lead source you do not have to scrape.

## Pace the outreach so the account stays usable

LinkedIn does not publish how many invites or messages an account can send. Anyone quoting a number is guessing, and the number shifts with account age, acceptance rate and how many people have reported you. Work from what your own account tells you instead.

Send in small batches spread across the day, and stop when acceptance drops. If your last twenty invites produced one acceptance, the message is wrong and more volume makes it worse.

Clear out stale invitations. Requests sitting unanswered for weeks drag your acceptance rate down and take up the room you need for new ones.

| | Activity | What goes wrong | What to do |
| --- | --- | --- | --- |
| Connection requests | Bursts of invites in one sitting look automated | Spread them through the day and stay below the point where acceptance drops |
| First messages | Long pitches to people who accepted an hour ago | One short note tied to why you connected, sent a day later |
| Pending invites | Hundreds unanswered, acceptance rate falls | Withdraw the ones older than a few weeks |
| Replies | Left sitting for days while you keep sending invites | Answer the same day and pause new sends while a conversation is live |

## Doing this with Kinlead

Kinlead's [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 your opening line is already written.

Lead search runs on LinkedIn's standard search, so a Sales Navigator seat is not required. Every lead is scored 0 to 100 against the buyer you describe, and anything below the fit line is dropped.

1. **Describe the buyer.** Give Kinlead the profile: staff or principal engineer, company size, the stack they mention. Leads get scored against it and low scorers are not kept.
2. **Point the agent at competitors.** Add the company pages and, if you want, the founder or engineer profiles whose posts collect the technical comments.
3. **Load your own script as a playbook.** Paste the messages that already work for you. Messages and follow-ups are written from that playbook, the campaign goal and the tone you set.
4. **Read the queue before it sends.** Queued messages sit on the Actions page. Edit them or pause the campaign before anything goes out.
5. **Take over at the first real question.** Set the campaign to hand the conversation to you at the first reply, or let the AI answer until a meeting is booked on your scheduling link.

## Related

- [Steal customers feature](https://getkinlead.com/features/steal-customers.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)

## Common questions

**Do I need Sales Navigator to find developers on LinkedIn?**

No. Competitor comment threads and profile searches run on standard LinkedIn. Navigator helps with saved searches and filters, but the signal you care about comes from posts and comments.

**How do I answer a developer who asks for pricing right away?**

Give a real number or a real range and explain what moves it. A vague 'it depends, let's jump on a call' ends the conversation with technical buyers.

**What do I send if they accept my invite and say nothing?**

One short follow-up a few days later with something useful: a doc page, a fix for the problem you mentioned, or a note that the thing they complained about is now handled. If that gets nothing, stop.

**Should the first message mention my product?**

Mention it in one clause at the end, after the useful part. Leading with the product is what makes an engineer close the tab.

**How many developers should I message a week?**

LinkedIn does not publish a limit, so set your own from your acceptance rate. If acceptance falls, your list or your message is off, and sending more will not fix it.

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