How to write a LinkedIn hiring post that gets applicants

A LinkedIn hiring post that gets applicants does four things: it names the role and the location inside the first 200 characters, it says what the person will actually do rather than what your company believes, it asks for referrals instead of applications, and it keeps the job link out of the opening lines. We ranked 543 hiring posts from 46 creators against each other. Shared links account for 41.2% of the topic's weakest half and 16.7% of its strongest decile. The single most common way to post a job is also the worst.

What do 543 hiring posts say about what gets applicants?

We isolated the hiring topic inside our 12,988-post cohort: 543 posts from 46 creators. Then we ranked those posts against each other and compared the topic's own top decile (54 posts, 12 authors) with its own bottom half (272 posts, 27 authors). That within-topic comparison is the useful one. It removes the possibility that hiring content simply performs differently from leadership or startup content, and asks the narrower question: among people posting about hiring, what do the ones who get traction do differently?

One row does nothing, and it is the one most people would bet on. First-person openers run 14.8% at the top and 14.3% at the bottom of the hiring topic, a difference of half a point. Across the whole cohort, first person is one of our strongest signals, roughly 2x. In hiring it vanishes. That makes sense once you say it out loud: a job post is not about you. Nobody applies because the hiring manager had a moment of reflection.

The performance gap those choices sit on top of is large. The median top-decile hiring post drew 306 reactions and 42 comments. The median bottom-half hiring post drew 69 reactions and 4 comments. For the whole topic, the median is 102 reactions and 10 comments at an engagement rate of 0.56 per 1,000 followers, slightly above the cohort median of 0.40.

Why do “we're hiring, apply here” posts fail?

Because they are not posts. They are a redirect with a caption. The link-share pattern makes up 41.2% of the hiring topic's bottom half, by far the most common failure shape in the category, and it fails for three separate reasons at once.

• The preview eats the hook.When you paste a job URL, LinkedIn renders the listing card, and your own words shrink to a line above it. You have handed your best real estate to an applicant tracking system's page title.
• The reader cannot act yet. Nobody clicks apply on the strength of a job title. They click when they believe the role is real and the manager is competent, and neither of those things is in a link.
• It asks the wrong person. A link post is addressed to candidates, who are a small slice of your feed. A well-written hiring post is addressed to everyone who knows a candidate, which is most of your feed.

This is not an argument that links are cursed. Our full look at what happens to outbound links, including the cases where they hold up, is in the external links analysis. It is an argument that a hiring post should be a complete piece of writing that happens to end in a link, rather than a link that happens to have writing near it.

Here is a hiring post from our top set that carried its link and still worked, because the text does the whole job first.

What should go above the fold in a hiring post?

You get roughly 210 characters on desktop and fewer on mobile before LinkedIn cuts to “see more”. Within the hiring topic the median visible hook is 206 characters at the top of the ranking and 206 at the bottom, so length is not the variable. Content is. In that space, in this order:

1. The role, named the way a candidate would name it.“Senior backend engineer”, not “a builder to join our rocket ship”.
2. The location and the arrangement. Remote, hybrid, or a city. This is the first filter every reader applies and hiding it wastes their time and yours.
3. One specific detail about the work. The system they will own, the customer they will talk to, the thing that is currently broken. This is the line that makes it feel like a real job at a real company.
4. A reason to keep reading. A number, a constraint, or an admission. What is hard about the role is more interesting than what is good about it.

What does not belong above the fold: your company's founding story, the word “passionate”, a list of benefits, or the sentence “we are growing fast”. Those are not wrong, they are just not worth 206 characters. The mechanics of writing to that cut, including how line breaks eat the preview, are in the hooks study.

What is a hiring post template that actually works?

A structure, not a fill-in-the-blank script. The lines below are illustrative examples, not posts from the dataset. Our data only captures the visible hook, so the ordering below the fold is a judgment call informed by what the top posts do above it.

The pay band line is doing more work than it looks. It is the single fastest way to signal that a hiring post is serious, it filters out mismatches before they cost anyone an hour, and very few posts include it, which makes yours memorable for a reason that has nothing to do with writing. If you cannot publish a number, publish the process instead: how many stages, how long, who decides.

More reusable post shapes, including non-hiring ones, are in the post templates collection.

Should you ask for applicants or referrals?

Referrals. It is the highest-return change in this whole article and it costs one sentence. Questions appear in 22.2% of top-decile hiring hooks against 13.6% of bottom-half ones, and the questions that show up in the top set are mostly asks: do you know someone, who have you worked with, can you point me at.

Look at that ratio: 186 reactions to 93 comments. A typical bottom-half hiring post in our data draws 69 reactions and 4 comments. Asking a direct, answerable question is what moves the comment number, and comments are the scarcer signal in every cut of our data.

The mechanism is simple. Most people reading your feed are employed and not looking. Ask them to apply and you have addressed maybe two percent of them. Ask them who they would recommend and you have addressed all of them, including the ones who will forward it privately and never appear in your engagement numbers at all. If you want the wider version of this, the comments strategy guide covers how to keep that thread alive once it starts.

What do good hiring posts sound like?

The examples below are real hooks from the hiring topic's highest-rate posts. None of them is a job advert, and that is the point: the hiring content that travels is usually content about hiring, which then earns the right to mention a role.

More hooks from this topic, with the numbers attached, sit on the hiring examples page.

How do you write a hiring post for a role nobody wants?

Hard roles are where the generic post fails hardest, because the reader has seen the same listing from six companies. Three approaches that do not require lying:

• Name the difficulty first.“This role has a legacy system in it and the person before you left” will out-recruit “exciting opportunity” every time, because the small number of people who like that work self-identify instantly.
• Narrow the audience on purpose.A post aimed at one kind of person will out-perform a post aimed at anyone. Second person appears in 42.6% of top-decile hiring hooks and 23.9% of bottom-half ones, and the useful version of “you” is a description specific enough that most readers correctly conclude it is not them.
• Post the team, not the job. A short video of the person the hire will sit next to, talking about what they need, does something a bulleted requirements list cannot. Native video runs 22.2% at the top of the hiring topic against 13.6% at the bottom, and the video breakdown covers the format generally.

Should the recruiter or the hiring manager write the post?

The hiring manager, and it is not close. We cannot put a number on this one: our role buckets do not include enough recruiter accounts to publish a figure, and we would rather say that than invent one. But the direction is visible in the topic data. The hiring posts that reach the top decile are written in the first person by someone with a stake, and 27.8% of them are plain text posts against 14.0% at the bottom. Plain text is what a person writes. Formatted listings are what a system produces.

Practically, that means the strongest version of a hiring post is the manager saying what they need and why, and the recruiter amplifying it rather than originating it. A recruiter reposting a manager's post carries the manager's specifics. A manager reposting a recruiter's listing carries nothing.

If you are a recruiter writing for yourself, the material that works is the same material that works for anyone: what you are seeing in the market, what candidates tell you, what your clients get wrong. The two hooks above about ghosting and about job hunting were both written by someone in the hiring business, and neither of them is a job advert. That is what makes the eventual job post land.

How often can you post the same role?

As often as you have something new to say about it, which is more often than most people think. A single hiring post has a working life of about 48 hours. Roles take weeks. The mistake is treating the first post as the announcement and every subsequent one as a repeat.

• Week 1: the role. The structure in the table above.
• Week 2: the process. What the interview actually involves, stage by stage. Candidates who did not act the first time act on this one, because it removes the main reason people do not apply.
• Week 3: the state of the search. How many applications, what you have learned, what you are still missing. This one gets comments because it is genuinely news.
• Week 4: a person, not the role. Something the team shipped, or what the last person hired into this team is doing now. It recruits without asking.

Four posts, one job, zero repetition. Reposting the identical post is a different move and a weaker one, because the second impression of the same words asks the reader for attention it has already spent.

What should you post when you are not hiring?

This is the part most hiring content skips, and it is why the first post of every search underperforms. If your feed only mentions your team when you need something from it, you are cold-starting every time.

The top hiring posts in our set are mostly not job adverts. They are posts about the hiring process by people who run it: how candidates get ghosted, how job hunting has changed, how a referral turned into a business partnership. That content earns the audience that makes the eventual job post work, and it earns it from people who are not currently looking, which is the audience that supplies referrals.

A workable ratio is one hiring post for every four or five posts about the work. If that sounds like a content plan rather than a recruiting tactic, it is, and the content strategy guide covers the wider version.

How many hashtags should a hiring post use?

The hiring topic has the sharpest hashtag split we measured. Four or more tags appear on 50.7% of the topic's bottom-half posts and 22.2% of its top-decile posts. Meanwhile, having at least one tag is normal at both ends: 74.1% at the top, 66.2% at the bottom.

So the rule is not “avoid hashtags”. It is that a wall of them looks like a recruiter blast, and recruiter blasts get read as spam by exactly the audience you want. Pick one topical tag and one role tag. Put them at the end. The full hashtag distribution has the cohort-wide picture.

Should you post the job from your company page or your profile?

Your profile. Every finding in this article describes posts written by people, and the mechanics of the feed favour them: a person can address a reader in the second person, admit that a role is difficult, and ask a network for a favour. A company page can do none of those things without sounding strange.

The pattern worth copying is that the manager posts, colleagues comment rather than repost, and the company page shares the manager's post afterwards. Comments from teammates in the first hour do more for a hiring post than a page share does, because they add specifics the original post did not have room for: what the team is like, what the last hire found hard, who to talk to.

There is one exception. If the role is genuinely high-volume, say a retail or support intake where you need hundreds of applicants rather than five good ones, the page post plus paid distribution is the right tool and none of this article applies. The advice here is aimed at roles where one right person matters more than a large pipeline.

How should you measure a hiring post?

Not by likes. A hiring post has one job and it is countable. Track these instead:

1. Qualified applications attributable to the post. Add a source field to your form. Without it you are guessing.
2. Referral messages in your inbox. These never show up in engagement metrics and are usually the highest-quality channel a hiring post produces.
3. Comments that name a person. A tag is a warm introduction happening in public. Reply to every one of them within the hour.
4. Profile views in the 48 hours after. Candidates research the hiring manager before they apply, so this moves before applications do.

A post with 40 reactions that produced three referrals beat a post with 400 that produced none. This is the one category on LinkedIn where the vanity metric and the real metric come apart cleanly, so it is worth setting your expectations before you publish. Decide before you publish which of those four numbers would make the post a success, and write it down, because afterwards the reaction count will try to answer the question for you.

How do you write a hiring post yourself, step by step?

1. Write the first line as role plus location plus one detail. Cut it at 200 characters and check that all three survive.
2. Delete every adjective about your company. Then read it again. What is left is usually the honest version.
3. Add the thing that is hard. One sentence. It buys more credibility than a paragraph of benefits.
4. Publish the band or the process. One of the two, always.
5. End with a referral question, not an application instruction. More on closing lines in how to end a LinkedIn post.
6. Put the link in the first comment. Then pin that comment.
7. Reply to everyone for the first hour. Especially the people tagging friends, because that is the mechanism spreading the post.
8. Repost it once, a week later, with the update.“Nine applications, still looking for X” is a new post, not a repeat.

Two habits to drop while you are at it. Do not open with “I am excited to announce”, which spends the first eleven characters of a 206-character budget on a feeling nobody is reading for. And do not tag fifteen people hoping for reach; tagging works when the person tagged has a genuine reason to reply, and reads as spam in every other case. The version that does work is naming one person in the body because they are relevant, then letting the referral question do the distribution.

What this data cannot tell you

These are correlations, not causes. We can say that link shares are two and a half times more common among the weakest hiring posts than the strongest ones. We cannot prove the format caused it, and the hiring top decile is 54 posts from 12 authors, which is a small enough group that a couple of prolific writers shape the profile. The cohort skews toward established creators with at least 1,000 followers, so read every figure as directional if you are starting out. Engagement counts are lifetime totals at collection time and post ages vary. And all text findings describe the visible hook rather than the full post body, because that is what our source captures. Method, filters, and caveats in full are in the 34,000-post engagement study.

Writing about a different subject?

Each subject behaves differently, and we compared every topic against its own top decile rather than against the whole cohort: leadership, AI, DEI, burnout and mental health.