Sourcing Developers From Communities

Why the channel is unusually good

Every other sourcing channel shows you a description of someone. A profile, a resume, a portfolio: all self-authored, all optimised, all claims.

Communities show you the person working.

Someone answering questions in a technical channel is demonstrating what they know, how they explain it, how they handle being wrong, and whether they are pleasant to deal with under mild friction. That is a substantial share of what an interview process tries and often fails to establish, available before you have spent anything.

The second advantage is self-selection. People active in a community around a technology are usually interested in it beyond employment, which correlates with the kind of engagement you want and is difficult to detect from an application.

The third is reach into people who are not looking. Most strong engineers are employed and not reading job boards. They are in these spaces because they use the tools, and an approach that arrives with evidence you have actually seen their work lands very differently from a template.

The catch is that all of this requires you to be present over time rather than arriving when you have a vacancy, which is precisely what most companies do.

The rules, which are strict and unwritten

Communities are not recruiting venues that happen to have conversation in them. They are conversations that will tolerate recruiting under conditions.

Belong before you recruit. Participate genuinely for a period. Answer things, ask things, be useful. Someone who joins and posts a vacancy within a week is visibly extracting, and it is read that way immediately.

Never broadcast unless the space explicitly allows it. Many communities have a designated jobs channel; use it and only it. Posting a role into a general channel is the fastest available way to lose access, and the loss is permanent in practice.

Approach privately and individually. Reference the specific thing you saw them do. Anything that reads as templated undoes the advantage of the channel entirely, because the whole point was that this was not a mass approach.

Accept no gracefully and once. People talk to each other, and a persistent recruiter becomes a shared complaint. A single respectful follow-up is the ceiling.

Contribute something back. Companies that sponsor, maintain tooling, answer questions or send engineers to participate earn standing that makes recruiting acceptable. Companies that only take are noticed quickly.

Breaking these does not cost you a candidate. It costs you the community, and communities overlap enough that the cost extends further than the one you were removed from.

Where it fits and where it does not

It fits sustained hiring. The channel compounds: standing accumulates, you learn who is good, and approaches get easier. A company hiring in a domain continuously should be present in its communities permanently.

It does not fit one urgent role. If you need someone in six weeks and have no existing presence, this is the wrong channel. Building standing takes months, and attempting to shortcut it produces the extractive behaviour that gets companies removed.

It fits specialised skills. Where the pool is small and conventional sourcing returns almost nobody, communities are often where the qualified people actually are.

It does not replace a process. Observing someone in a community tells you about their knowledge and their manner. It does not tell you whether they can own a system, work to a deadline, or handle the parts of a job nobody enjoys. Assess properly afterwards.

One practical note on the shift underneath all of this. What makes community sourcing work is that the evidence is public and continuous rather than asserted at application time. The same property is what makes verifiable work records useful more broadly: they let a hiring team evaluate before contact rather than after, which is the change that makes the whole process shorter and less speculative.

Participate first. Recruit second. The order is not negotiable and it is the part companies keep getting wrong.