Employee advocacy for recruiting and employer branding

Recruiting is the most dependable use of employee advocacy. Candidates want to know what it’s actually like to work somewhere, and a careers page can’t answer that convincingly. A steady stream of posts from the people who do the work can. Employer branding built on employee advocacy isn’t a separate program; it’s the same people talking about the same work, pointed at a question candidates are already asking.

This post covers why it works, how to shape a hiring push, what employees should post, what to avoid, and how to tell if it’s working.

Why candidates trust employee posts

A careers page is written by the company about the company, and every candidate knows it. It’s useful for logistics: benefits, locations, the interview process. It’s weak on the question that matters most: would I enjoy working with these people?

Employee posts answer that question indirectly, which is why they’re believed. When an engineer writes about a hard problem the team solved, a candidate learns what the work is like, how the team talks about it, and whether people seem to like their jobs, without anyone claiming any of it. Evidence beats assertion.

There’s a network effect too. Employees’ connections skew towards people with similar jobs. An engineer’s network is full of engineers; a recruiter’s is full of recruiters and hiring managers. The people who see an employee’s post about an open role are disproportionately the people who could fill it, or who know someone who could.

The hiring-push campaign

When you have several roles to fill at once — a new team, a new office, a growth quarter — it’s worth running a dedicated campaign rather than relying on scattered job posts. A shape that works:

Week 1: the why. A leader posts about why the team is growing: the problem, the bet, what the new people will own. Not the job description; the reason the job exists. See executive advocacy on LinkedIn for how to get leaders posting in their own voice.

Weeks 1–3: the team. People who’d work alongside the new hires post about their own work: a recent project, something they learned, what a normal week looks like. Most of these posts don’t mention hiring at all, or mention it in one line at the end. That’s deliberate.

Weeks 2–4: the roles. Hiring managers and team members post about specific open roles, each in their own words (more on this below).

Throughout: the replies. Whoever posts answers questions in the comments and DMs. A candidate who gets a real answer from a future colleague is far more likely to apply than one who’s pointed at a form.

The raw material for the campaign is the same as any good advocacy campaign: specific facts, not finished copy. What the team is building, what the interview process looks like, one honest thing about what’s hard. Each person writes their own version.

Team members posting about open roles

The single most effective recruiting post is usually not from a recruiter. It’s from someone on the team, saying why they’d want to work with whoever gets the job.

What makes these posts work:

• Specifics about the work. “You’d own the data pipeline we’ve been patching for a year” beats “exciting opportunity in a fast-growing team”.
• Who you’d work with. Name the team, describe how it works, mention what the person posting actually does.
• One honest caveat. “We’re small, so you’ll do some things that aren’t in the job description.” Candidates trust a post more when it isn’t uniformly positive.
• A direct invitation. “Message me if you want to know what it’s really like.” This is the line that turns a post into conversations.

If three people on a team each post their own version, you get three different angles on the same role, which tells a candidate far more than one polished job ad. For more post types, see employee advocacy examples.

New-hire posts

New hires are an underused source of employer-branding material. They’re the only people who can describe the joining experience while it’s fresh, and the people reading are often candidates at exactly the stage the new hire just went through.

A good new-hire post, written a month or so in, covers what surprised them, what the onboarding was like, and what they’d tell the next person. Invite it; don’t require it. A new hire who feels obliged to post a glowing review in their first week isn’t giving you anything a candidate will believe.

What not to do

Fake enthusiasm. Posts that are relentlessly positive read as compulsory. “Best team ever! So blessed!” tells a candidate nothing and slightly suggests someone asked for it. Let people be specific instead of effusive.

Over-polished video. A professionally produced “day in the life” with a music bed and colour grading looks like an ad, because it is one. A phone video of an engineer explaining something at a whiteboard is less impressive and far more believable. If you do produce video, keep it rough enough that it still looks like a person, not a production.

Identical posts. Ten employees sharing the same job graphic with the same caption tells candidates nothing except that someone sent a reminder.

Making it mandatory. Recruiting posts from people who were told to write them are easy to spot, and they cost the employee credibility with exactly the peers you’re trying to reach. The broader version of this problem is in why employee advocacy programs fail.

Overselling. If a post promises a culture the new hire doesn’t find, you’ve bought a bad hire and probably an early resignation. Accuracy is a recruiting strategy.

Measuring it

Recruiting attribution is messy, and anyone who gives you a precise “cost-per-hire saved by advocacy” figure is guessing. What you can measure honestly:

• Applicants who mention a post. Add one question to your application or first screening call: “How did you hear about us?” with a free-text answer. Count how many mention a specific person or post. It’s crude and it’s real.
• Referral volume. If employees are posting about roles, their networks should start sending referrals. Compare referral counts during a campaign with the quarter before.
• Conversations started. Ask the people who posted how many DMs or comments they got from potential candidates. Small numbers here are still meaningful; each one is a warm lead.
• Post-level numbers, in context. Impressions, clicks and comments per post tell you which angles landed. They don’t tell you who you hired, so don’t report them as if they do.

There’s more on choosing metrics that predict a healthy program, rather than ones that look good in a deck, in employee advocacy metrics.

Starting a recruiting campaign

You don’t need a big launch. Pick the team with the most urgent hiring need, ask three or four people on it whether they’d be willing to post, and give them the raw material: what the role owns, why it exists, what’s genuinely good about the team and one thing that’s hard. Then let each of them write it their way. The employee advocacy program guide covers how this fits into a longer-running program.

If you’d rather coordinate it in one place, Blabigo lets you put the hiring team in an advocacy team, send them a campaign with the raw material, and see per person how the posts performed, while everyone publishes from their own LinkedIn account in their own words.