5 min read

Hire Developers Who Aren’t on LinkedIn (They’re in Their IDE)

Why InMails and job boards miss passive engineers, how tech-stack matching works, and how to post a role developers will actually open.

Hire Developers Who Aren’t on LinkedIn (They’re in Their IDE)

Hire Developers Who Aren’t on LinkedIn (They’re in Their IDE)

LinkedIn Recruiter is where you talk to people who agreed to be talked to. Job boards are where you talk to people who opened a tab called “jobs.” A lot of the engineers you want did neither this week. They opened Cursor.

That is not a vibe. It is the whole hiring leak: passive developers — already employed, open to a better seat, allergic to InMails written like ads. Traditional channels price that leak as “more seats, more InMails.” You get more of the same list.

Idlen sits in the IDE and the browser while they work. Two products, one audience:

  1. Idlen Jobs — a listing matched on real stack, not a keyword salad.
  2. In-IDE / overlay ads — the same role, shown in a wait state, to people who never opened a job board.

The recruiting industry page is the long version (tech recruiting). This article is what to do on Monday.

Why your current mix keeps missing them

LinkedIn optimizes for titles and self-reported skills. “React” on a profile from 2022 is not React this quarter. CPMs in tech are also the expensive ones — the ad network playbook puts LinkedIn in the $33–$65 CPM band. Fine for named-account ABM. Painful for “we need two backend people who actually touch Postgres.”

Job boards optimize for active search. Useful. Incomplete. Anyone happy-enough-for-now never sees the post.

Agencies optimize for speed and a spreadsheet of people who answered the phone last year.

None of those watch package.json.

What “verified stack” means here

Idlen sees tools in use — IDE, browser, the dependencies in the project that is open — locally, for targeting. You are not buying a lookalike of “software engineer.” You are asking for people who shipped with the stack this week.

That is the same mechanism as product ads (tech stack targeting), pointed at a role:

You needYou target
Staff backendGo or Rust + Postgres, not “backend”
Product engineerTypeScript + React + the cloud you actually run
ML platformPython + the orchestrator you support
SecurityThe languages your codebase is in, not “cyber passionate”

Seniority is inferred, not a dropdown of 10 years. Complex repos and wide stacks correlate with experience. It is a prior, not a background check. Say that in the job post so nobody thinks you have their HR file.

Two ways to use it (use both if the role is hard)

1. Post the job

On the job board:

  • Company in a few minutes
  • Role, must-have skills, salary band, remote / hybrid / on-site
  • Matching + score (0–100) against profile, stack, location
  • Applicants can get alerts when the fit is real

Cost to post: €0. You are not buying a banner. You are entering a pool of people who already use the product while they code.

2. Promote the role in the IDE

Same copy, paid reach, idle moments. Treat it like any other first campaign: one stack, one geo, one ad. The €200 welcome credit is for product ads and hiring if that is the job. Do not run “we’re a family” over a Rust filter.

Write the unit like a product ad — 30-minute format — not like a careers-page poem.

The job ad developers will open

Developers apply when the post answers four things in the first screen:

  1. What they will ship in 90 days — a system, not “drive impact.”
  2. Stack that is true — if you still have a jQuery island, say it.
  3. Money — a band. “Competitive” is a bounce.
  4. How you work — remote policy, on-call, how many meetings. Lie once, lose the offer stage.

Kill: “ninja,” “rockstar,” “fast-paced family,” unpaid take-home that recreates your product, “must be passionate about our mission” as line one.

Keep: repo or product they can click, interview steps counted, visa reality.

A hiring overlay can be shorter than the listing:

Headline: Staff Go, Postgres, EU remote, €90–110k
Body: On-call one week in six. Two interview loops, no weekend homework.
CTA: Read the role

The listing holds the rest. The ad only has to earn the click.

Monday checklist

  1. Post the role on Idlen Jobs with a salary band and a real stack.
  2. Reuse that first screen as the in-IDE ad if you promote.
  3. Point the click at the job URL, not a “talent community” form.
  4. After a week: look at match scores and stack on applicants, not raw volume. Fifty mismatched CVs is the old job board.

If you are also running product ads, keep hiring and product in separate campaigns. Mixed CTAs teach you nothing.

FAQ

Why isn’t LinkedIn enough?

It reaches people who live there. Many strong engineers do not. They will move for a sharp role and a real band. They will not refresh InMail.

How is this different from Indeed or Welcome to the Jungle?

Those sites still depend on someone searching or opting in. Idlen can match on stack in use and, if you pay, show the role in the IDE during idle time — including people who did not open a job tab.

Can I target React only?

Yes. Filter and promote on technologies observed in daily work, not a 2019 skill tag.

What does posting cost?

€0 to list. Promotion and in-IDE reach are optional spend, including the welcome credit if you use it for hiring.


If the people you want are coding, talk to them there. Post the role.

Reach developers where they work

Advertise directly inside developer tools. Native ads, real engagement, zero wasted impressions.

90%
developer audience
CPM from $2
competitive pricing
5 min
to launch

Ready to reach developers?

Claim €200 in ad credit, then create your Ads Manager account with the same email. The credit is added automatically — no setup fees.

€200 welcome credit Launch in 5 minutes Cancel anytime