The Secret to Successful Job Referrals

Lots of companies are entering the job referral space. It’s heating up like crazy. They’re looking at someone’s social graph and trying to figure out how to convince and incentivize that person to recommend friends for jobs. And from what I’ve seen, they don’t work. I don’t know of a single recruitment company or startup that’s significantly improved how we make job referrals. I’m not saying these companies don’t exist (or won’t in the future), I just haven’t seen them yet. I do believe in social recruiting and the movement in that direction, but referrals are a beast of a challenge.

Why is that the case? Why haven’t the job referral startups / companies succeeded?

I’m not entirely sure. I hope someone figures it out, because I’d love to see this nut cracked in a huge way. I do have some thoughts though…

Job referrals are done instantaneously, but a bunch of micro-decisions are made in that instant to decide whether or not to refer someone to a job.

People typically only make job referrals instantly; the minute they receive the request or shortly thereafter. If they have to think about it for a long time, they won’t do it. People are lazy and people are busy. Technology could presumably grease these wheels, if it could provide us with the right people to refer, instantly, to any job requirement. And there are a number of companies working on this. But does it work?

The data that a computer system / algorithm needs to make the right recommendations is wholly incomplete. It can’t possibly understand the human psychology and subtleties that go on in the instant that someone decides: (a) yes, I want to make a recommendation; and (b) I know the right person. Here’s an example thought process that someone goes through when asked for a referral:

  • Do I know someone?
  • How well do I know them?
  • How well do I know the employer?
  • Why should I do it?
  • What’s my responsibility here?
  • Do I owe the employer anything?
  • Will the employer recognize that by making this referral they owe me (you scratch my back, I scratch yours)?
  • Do I want to put my reputation on the line?
  • Will I get an increase in reputation (from the two parties involved and beyond) by making this referral?
  • Is the person I’m thinking about available?
  • Will the person like the new job?
  • Will the employer like the person?
  • Will I be “in trouble” (in some way) with the employer I’m “stealing” the prospect from?
  • Do I even want this referral to be public?
  • Even if the person isn’t hired, will the interaction be valuable enough to the two of them that my reputation will: (a) remain intact; and (b) increase?

All of this goes through a person’s head when asked to make a job referral. It’s complex, but happens almost instantaneously. And if something doesn’t compute through this thought process, a recommendation doesn’t happen. Note that, “Will I make money off the referral” doesn’t fit into this at all. Why? Because I don’t think (and others with a lot of experience in this space have told me) that it doesn’t matter. Referral bonuses that you earn for recommending people are nice, but they don’t seem to drive people to make more referrals. The social capital ramifications are too big and outweigh the monetary rewards. Many people know that their networks are one of their most valuable assets. Those networks can’t be and shouldn’t be accessed cheaply or easily.

Jobs are one of the most personal, complicated and important things in people’s lives. You’re not recommending a plumber to fix a clogged toilet. You’re messing with people’s lives and their livelihoods. People don’t make these kinds of recommendations lightly.

Accessing Employee Referrals

Employee referral programs have existed for a long time. I’m certain they work but not as well as you might think. Employees – although they have obvious internal motivation to impress their employer – aren’t chomping at the bit to make referrals. They don’t necessarily think about it more, work longer at it or act more aggressively because of monetary rewards. Employees are equally cautious about tapping into their networks, and in some cases the stakes are higher – they may be working with the person they refer and be closer to the feedback (positive or negative.)

Employee networks often have quite a bit of overlap as well, and this is especially true for tech startups. A small tech company with 10-50 employees is going to have a lot of people with similar networks. That limits the number of referrals any one person can and will make, and means that referrals have to go multiple degrees away.

You Can’t Kill Recruiters

A lot of startups in the recruitment space point themselves directly at recruiters. The basic logic is that recruiters charge too much to place people. And if you look at other markets like travel and home sales, the intermediaries (travel agents and real estate agents) have been displaced (at least to some degree). But in recruitment, very little if anything has displaced recruiters. In fact, job boards and even social sites like LinkedIn, make a lot of their revenue from recruiters.

Job referral startups target recruiters because they want to offer a less expensive way of recruiting. And job referrals (if they work) are less expensive. But most of these startups heavily discount what recruiters do and the importance of significant human intervention in a very human, delicate interaction (getting a job). So I tend to discount recruitment startups that are going to “take down recruiters.”

The Secret to Successful Job Referrals

So what’s the secret? For a job referral system to succeed it needs to grease the wheels and make referrals effortlessly while taking into account the social and psychological issues involved. To make referrals easy on someone, you have to tell them exactly who they should refer to a job and why. In order to do that you need the right kind of data – a lot of which is not easily accessible – and a lot of which is based on human behavior and judgement.

I’m not saying it’s not possible, and I’m not saying there isn’t a startup working on this problem right now that won’t hit a home run in this space, but the problems in the recruitment space are much more complex and challenging than most people realize.


How Many Hours Should a Startup Employee Work?

Melted Clock

Every so often I get drawn into the debate about startup employees and how much they should work. Should you hire workaholics? Is it expected that startup employees work 100+ hours per week? Should they be online all the time, constantly available and ready to go?

It depends. And it’s up to you. If you expect employees to work 20 hours / day that’s your choice. If you find people willing to accept those jobs that’s great. I don’t have any issues with that, because when you recruit someone it’s a relationship between two people. If two people mutually agree on something that’s good enough for me. There’s rarely any arm twisting during an employee offer. If they don’t agree, the employee quits or they’re fired. Such is life.

But it got me thinking…

One of the big problems I’m seeing with a startup’s expectations for “hours worked” is that they use it as a metric of employee quality and success. Likely because it’s one of the easiest metrics to track. If someone works 80+ hours in a week they must be kicking ass! Whoever works the most is the best! But clearly that’s not always going to be the case. “Hours worked” is a poor measurement of almost everything, except for “hours worked.” I’m not even sure it’s a great measurement of passion (which is an essential quality you need to look for in startup employees.) It could just be that the guy is slow, so he works more hours.

We need to think about other measurable indicators of an employee’s quality and value. Just like “years of experience” on a resume is a shoddy measure of expertise and quality, the same holds true for “hours worked”.

I’m not arguing against a startup’s need to move insanely fast. Startup jobs aren’t (and never will be) “9 to 5 gigs.” And I agree that oftentimes startups do feel out of control and insane, and that’s part of the appeal. Startups are roller coasters. Don’t think of them any other way. But at the same time if you look at how you evaluate the quality and value of an employee and you’re saying, “Well, he’s not putting in 20 hours per day…”, just stop and ask yourself whether that’s a true measure of value or not.

image courtesy of shutterstock


9 Ways to Successfully Edit Job Postings

Job postings suck. We all know it. It’s been said many, many times. And it doesn’t seem like complaining about it is helping. I’m experimenting on NextMontreal with a job board hack, but I’ve also been thinking about practical advice I can provide on how to improve job postings. Instead of getting people to completely change how they write job postings from scratch, I thought it would be more effective to focus on how people edit them. So after you’ve written a job posting, walk through these steps, and let’s see if it comes out better!

  1. Read out loud what you’ve written. Make note of anywhere that it sounds funny, awkward or sentences run-on forever. Attempt to fix those things.
  2. Count the bullet points. If there are more than 5 in any list, take some out. Force yourself to prioritize. Find a way of replacing bullet points with paragraphs (but don’t go crazy with long paragraphs either!)
  3. Take out anything that’s absurdly obvious. The worst offenders are usually in the “Skills” area. For example: Must be an excellent communicator (both verbal and written.) Duh! Other common offenders: Great attitude, like to work in teams, ability to work in a fast-paced environment, a quick learner, works well without supervision, ability to work in a high-pressure environment, detail oriented, goal oriented, proficient computer skills.
  4. Pretend you’re looking for a job and read it. Does it speak to you at all? Does it interest you? Does it encourage you? Does it answer the questions you might have?
  5. On that note, write down a list of questions you think a potential candidate would have about the job opportunity. Now go back and read the job posting again. Are the answers in there? Do you know what matters to potential candidates?
  6. Count how many times the word “we” is there. Compare that to the word “you”. Hhhm…
  7. The company description should be short. And it should be centered around why someone would want to work there, not around all the awesome awards you’ve won, or how much money the company makes. What matters to job seekers? Focus on those things.
  8. Look at the number of years experience you’ve listed for various skills. Usually these are written as hard and fast rules: “Must have X years experience in Y.” Really? Are you sure? Why? Have you looked at other team members to see what number of years experience they have, and how successful they’ve been? What happens if someone has 4 years experience instead of 5? And does the number of years experience matter as much as the number of projects worked on? Think about ways to gauge experience differently. For example, you could say, “You know the difference between A and B.” A and B could be very specific things that typically would only be understood by a senior person. When someone applies, they should make note of the difference between A and B in their cover letter so they stand out. If they don’t, ask ‘em about it.
  9. Take out your company name and replace it with a competitor’s. Can you tell the difference? Does it matter? If not, imagine how a job seeker feels.

The road to high-quality, meaningful and useful job postings is a long, painful one. Perhaps too painful. But we’ll keep trying anyway…


Ben Yoskovitz
I'm VP Product at GoInstant.

I'm also a Founding Partner at Year One Labs, an early stage accelerator in Montreal. Previously I founded Standout Jobs (and sold it). MY BIO >>

Follow this blog via email

Advertisement
Startup Resources
A collection of posts I've written over time on key subjects:

Find Stuff
My Photos