How to get employee referrals

Start with the payoff, since it justifies the asking. Ashby analyzed 38 million applications across 93,000 jobs and found that 40% of referred candidates go from application to interview, against 3% of inbound applicants (published May 2025). No other step in hiring moves a number that far.

The cost is where most referral asks go wrong. An employee giving you a name spends two things. First, standing: they are telling somebody they respect that this company is worth their time, and if the process treats that person badly the employee wears it. Second, the effort of remembering who they know.

Recall is the part nobody budgets for. Asked whether they know any backend engineers, most people come back with two names, usually whoever they spoke to most recently. The other forty are not being withheld. Nobody can produce them on demand in a Slack thread between meetings.

Both costs point the same way. Ask narrowly, so recall has something to work with. Say what you will and will not do with the name, so the social capital feels protected. Then close the loop, because the second referral from the same person depends entirely on how the first one was handled.

What an employee can recall decides how many names you get, and left alone it depends entirely on what people can remember while reading a message. Happenstance moves that work off the employee. Each person connects the accounts their working life already runs through, seven sources between them, and a group pools those networks so the whole team can be searched at once. Ask “who do we know who has worked at a payments company in the last three years?” and you get a list of people with the evidence for each relationship attached.

Then the conversation changes shape. Instead of “do you know anyone”, you're sitting down with a page of names from one company and asking which of them somebody would vouch for, which is a question a busy person can answer between meetings.

Happenstance is free. The free plan is the whole product, with usage limits on chat and web searches beyond your network. Pro raises the limits: unlimited web searches and results, higher chat limits, and CSV export. A group has no cap on members, and one can hold the whole company. The step-by-step version is on Happenstance for recruiting, and the general idea sits under relationship mapping. Referrals are also the strongest of the channels in how to source candidates for free.

This goes to a small group who have worked near the role, in Slack or by email. The forwardable block is what gets you the referral, so it sits at the bottom where it can be copied cleanly.

Three things make it land. The question names companies rather than job titles, so memory has somewhere to start. The forwardable block describes the work and the money, so nobody has to compose anything. And the promises are specific enough to be checked, which is what makes them worth making.

Send it once per role, to the people nearest that role, and don't repeat it weekly. The second copy of an ask teaches people that the first one didn't need answering, and a company that asks every Monday gets treated like a mailing list by the end of the month. When the role is filled, say so in the same thread. That closes the loop for everyone who thought about it and didn't reply, which is most of them.