← leadl.aiRU

Social Recruiting: Finding Candidates Where They Already Are

Social recruiting means sourcing candidates through the platforms where they spend their professional life, rather than through job boards. In practice most tools read this as "search LinkedIn" — which leaves out the places where specialists actually discuss their work.

What social recruiting covers

Three different activities share the name, and they need different things:

This page is about the third.

What each platform actually shows you

Platforms differ in what evidence they carry, and that decides which roles they suit.

Reddit and Discord: the part most tools skip

Both are dismissed as unsearchable, and both carry signal the professional networks do not. Someone answering a detailed question about a framework in a Discord server at midnight is demonstrating knowledge nobody put on a CV.

The etiquette is different and it matters. These are communities, not candidate databases. Blasting members with recruiting messages gets accounts banned and does the employer brand no favours. The workable approach is to treat public activity as evidence of skill, then contact people through a channel where that contact is expected — not by messaging them mid-thread.

We built this into the product deliberately: see community sourcing.

What social recruiting does not solve

Two honest limits.

It is slow by hand. Reading someone's public activity across four platforms to judge whether they fit takes real time. Do it for forty candidates and the week is gone. This is why most teams default back to LinkedIn: not because it is better, but because it is faster to skim.

Public activity is uneven. Excellent engineers exist who have never pushed public code, and whole professions leave almost no public trace. Social sourcing finds people who are visible — a subset, not the market.

Making it work without losing the week

  1. Pick platforms by role, not by habit. Backend engineer — GitHub and Stack Overflow. Designer — portfolio sites and Discord communities. Sales — LinkedIn and track record.
  2. Judge evidence, not presence. A GitHub account with three forked repos proves nothing. What matters is what someone actually built or answered.
  3. Assemble one profile per person. The same human appears under different handles on different platforms. Merging those fragments is most of the work.
  4. Write something specific. Reference the actual work. Reply rates to templated outreach on these platforms are close to zero.

How leadl.recruit handles it

Paste a job description and it searches GitHub, Stack Overflow, LinkedIn, Reddit and Discord in parallel, merges what it finds into one profile per person, and returns a shortlist where each candidate has a written verdict: what matches, what does not, the risks found, and what to ask at interview.

That removes the reading, which is the part that makes social sourcing impractical by hand. It does not remove the judgement — the hiring decision stays with a person.

Pricing is public: free plan, then €49, €149 and €399 a month. You pay per search run rather than per contact revealed. See pricing and candidate sourcing.