Where to find candidates beyond LinkedIn

Candidates beyond LinkedIn are found where they do their actual work and talk shop: GitHub and open source projects for engineers, portfolio and critique communities for designers, industry Slack and Discord groups, conference speaker lineups, niche newsletters, and local meetups. Each watering hole shows you something a LinkedIn profile cannot, which is the work itself. The trade-off is that these are communities first and talent pools second, so how you approach people matters as much as where you look.

Why look anywhere else when LinkedIn has everyone?

LinkedIn has nearly everyone listed, which is exactly the problem. Listed is not reachable: senior engineers, designers and data people get so much templated outreach there that response rates have been sliding for years, and many of the best candidates have effectively muted the channel. A profile is also a self-portrait. It tells you what someone claims; a code repository, a published talk or a design critique thread shows you what they can actually do.

None of this means abandon LinkedIn; it remains the broadest single index of professionals, and whether you need tooling on top of it is a separate question we cover in do I need an ATS if I use LinkedIn. The argument here is narrower: for hard roles, an hour in a niche community beats an hour sending InMail number fifty-one.

Which watering hole fits which candidate?

The mistake is treating “beyond LinkedIn” as one channel. It is a dozen, each suited to a different kind of candidate. A rough map:

Candidate type	Where they gather	What you can see there
Software engineers	GitHub, open source projects, Stack Overflow, language Slacks/Discords	Real code, code review tone, consistency over time
Designers	Dribbble, Behance, Layers, design Slack groups, portfolio sites	Actual work, range, how they take critique
Data and ML people	Kaggle, GitHub, paper repositories, ML Discords	Modeling choices, rigor, how they explain results
DevOps and infra	Tool-specific Slacks (Kubernetes, HashiCorp), GitHub, conference CFPs	Operational depth, incident war stories
Marketers and growth	Industry newsletters, marketing Slack communities, podcast guest lists	How they think, written communication
Product managers	Product communities, conference lineups, newsletters they write	Judgment, framing, communication
Everyone, locally	Meetups, user groups, regional conferences	Willingness to show up, network gravity

The right-hand column is the point: each source gives you evidence, not claims, which makes outreach specific and screening shorter. And the same person often appears in three of these places; triangulating (active in the Kubernetes Slack, spoke at a regional conference, maintains a small tool on GitHub) beats any single profile.

How do you actually source from GitHub and open source?

GitHub sourcing fails when recruiters treat it as a resume database with green squares. It works when you read it as evidence of how someone works.

Start from the projects, not from people search. Pick the libraries and tools your team actually uses, then look at who maintains them, who lands non-trivial pull requests, and who answers issues patiently. A contributor who writes clear commit messages and handles a disagreement in a code review gracefully has just shown you two things no interview reliably surfaces.

Then widen the net deliberately. The maintainer of a popular project is over-contacted; the person who contributed the third-best pull request this year usually is not. This is the same logic as searching adjacent job titles and skills: the obvious target is saturated, so the value is one ring out.

When you reach out, reference the actual work. “I read your PR adding retry logic to X and the discussion about backoff strategy” is an opener no template produces, and engineers can smell the difference instantly. And a caution: contributing to open source on evenings does not mean someone wants to be contacted about it constantly. One message, genuinely specific, then leave them alone if they decline.

What about Slack groups, Discords and forums?

Nearly every profession now has invite-cheap communities: language and framework Slacks for engineers, design critique groups, marketing operator communities, regional tech Discords. They are the densest concentrations of relevant people you will find anywhere, and the easiest place to torch your reputation.

The rules are simple and non-negotiable:

• Read the rules first. Most communities allow hiring posts in a designated jobs channel and ban them everywhere else. Post there, in their format, and nowhere else.
• Do not bulk-DM. Mass-messaging members off the member list is the fastest route to a ban, and word travels between communities.
• Participate before you pitch. Answer a question, share something useful, be a person. A recruiter who has been visibly helpful for a month gets replies that a drive-by account never will.
• DM individuals only with a reason. Responding to something they posted publicly (“you mentioned you are wrapping up a contract”) is fine. Cold-pitching someone whose name you scraped is not.

The slower pace is the feature. One placement sourced from a community where you have standing tends to refer the next two.

Are speaker lists, newsletters and meetups worth the effort?

Yes, for senior and scarce profiles especially, because these channels pre-filter for exactly what is hard to assess: communication and depth.

Conference speaker lists are public, free and underused. Anyone who got a talk through a competitive CFP can structure an argument and explain their work, and past lineups (most events keep an archive) give you years of names. The approach mirrors GitHub: reference the talk itself, not the fact of speaking.

Newsletters cut both ways. Niche newsletter authors are candidates and connectors, and a thoughtful reply to an issue is a warm opening. Many also run small job boards that reach exactly the audience you want for a fraction of a major board’s price.

Meetups are the long game. Showing up regularly to a local user group makes you the recruiter people already know when they start looking. It does not scale, and it does not need to: most teams need only a handful of great hires a year from any one specialty.

How do you keep multi-channel sourcing from becoming chaos?

The hidden cost of sourcing across six channels is fragmentation: names in browser tabs, a spreadsheet of speakers, half a conversation in a Slack DM. People you found brilliantly in March are unfindable by June, and worse, you re-contact someone who already said no.

The fix is unglamorous: one system of record, no matter where the candidate came from. Every promising person gets a profile with the source, the context (which talk, which repo, which thread) and the state of the conversation, so the relationship survives the channel it started in. That consolidated pool is also where the compounding happens: the speaker who was not interested this year is a warm first call next year. We unpack that model in what is a talent pool, and if you want sourcing reach built into the tracking layer itself, see ATS with built-in candidate sourcing.

This is also where Recruitifly fits. The platform is built around a single assistant, Fly, that handles the unglamorous half of multi-channel sourcing: parse whatever you captured into a clean profile, search the talent pool before you re-contact anyone, score the community finds against the role next to the inbound applicants, and draft outreach that you edit and approve before anything sends. That last part is deliberate: community sourcing runs on trust, and every message Fly prepares waits for your explicit confirm, because a recruiter’s name is on it. We are in private beta; if you are sourcing beyond LinkedIn and want the bookkeeping handled, talk to us.