How to post on LinkedIn after being laid off

To post on LinkedIn after being laid off, say three things: what happened, in one plain sentence; what you do, in one or two; and one small request a reader can finish in under a minute. Most layoff posts stop after the first sentence, which is why they collect condolences instead of introductions. Sympathy is produced by the news. Help is produced by the ask. A post will not make the search short, but a post with a real ask in it turns goodwill into something a stranger can actually do.

Why do most layoff posts get sympathy instead of help?

Because the news does the emotional work by itself, and the post gives the reader nothing else to do. Someone scrolling past sees that you lost your job, feels something, and reaches for the only control the post offered them, which is a reaction button. That is not an audience failing you. It is a post that asked for a reaction and got one.

The second reason is the size of the ask when there is one. “Open to new opportunities.” “Any leads appreciated.” Read those from the other side. A reader who wants to help has to work out what you do, guess which companies would suit, remember who they know there, and write an introduction. That is fifteen minutes of work performed by someone scrolling with one thumb at a bus stop. Almost nobody completes it. They write “so sorry to hear this, you will land somewhere great” instead, which is the honest response of a person who wanted to help and was not told how.

Be clear about what a post can do. It will not get you hired. It can produce a warm introduction inside a company on your list, your name forwarded into a hiring channel before a role is posted, and a few people watching out for you for six weeks. None of those arrive because a post was moving.

A third factor is not about you at all. LinkedIn tests a post on a slice of your network before widening it, and that slice sees only the fragment above the “see more” fold. A general statement about how hard the market is competes with every other general statement in the feed. A specific sentence does not. The guide to first lines has the mechanics.

What does an ask people can actually answer look like?

Four components. Miss one and the reader has to do the work you skipped.

• A named role.Not “marketing roles” but “senior lifecycle marketing, B2B SaaS, Series B to D”. People worry that narrowing shuts doors. In practice a wide ask does not open doors, it just fails to open any.
• A named set of companies.Five to fifteen, by name, in the post. This is the component most posts leave out and the one that does the most work, because it turns “do I know anyone who might help” into “do I know anyone at these names”, which a reader answers in three seconds by scanning the list. The list is a prompt, not a filter.
• A named type of introduction. A hiring manager in that function, anyone who works there, an in-house recruiter, a former employee who can tell you whether the team is real. Different asks, answered by different people.
• One thing a reader can do in under a minute. Reply with one name. Comment if you are hiring. Forward the post to one person. That is the whole ask, and it belongs in the last line.

The clearest example of this shape in our dataset is not a layoff post. It is a journalist asking a question.

Look at the ratio rather than the totals: 139 comments against 239 reactions, where most posts collect several reactions per comment. Reactions are what a post gets when a reader agrees. Comments are what it gets when a reader has something to contribute and knows what it is.

For contrast, a post about laid-off people rather than by one, shared as an article link.

One post is an illustration, not proof. But it illustrates two patterns the aggregate data does support. First-person openers appear in 19.6% of top-decile posts across our cohort against 10.1% of the bottom half. Shared article or link posts make up 32.7% of the bottom half against 22.1% of the top decile. Why link posts under-perform is a longer argument, but here the reason is simple. You are asking people to help you. Sending them somewhere else first is the wrong order.

What changes between a sympathy post and a help post?

The same facts, component by component. Left is the default version almost everybody writes. Right is the same post with the reader given something to do. Both are written by me as illustrations, not taken from the dataset.

Read the right column aloud and notice how little emotional performance it contains. That is deliberate. Understatement signals that the reader is not about to be asked to manage your feelings, and a person who is coping is much easier to introduce to somebody than a person who is performing coping.

What do 89 job-search posts from 27 authors show?

Less than we would like, and the honest version of that sentence matters more than any figure in it. Our cohort contains 89 posts tagged job-search, from 27 authors. That is a topic, not a study. It is enough to describe what job-search posts look like. It is not enough to tell you which ones win.

Across those 89 posts: a median of 105 reactions and 19 comments, first person in 11.2% of visible hooks, “you” somewhere in 46.1%, a question mark in 24.7%, and four or more hashtags in 44.9%.

The interesting figure is the format mix. Job-search posts are 40.4% plain text, against 30.3% image, 19.1% shared article and 7.9% video. Plain text is a minority format almost everywhere else: across the cohort it is 19.3% of the top decile and 16.6% of the bottom half.

I do not read that gap as a discovery about the algorithm. The likelier explanation is human: people write these posts fast, in one sitting, without stopping to find a graphic. The useful part is that the format they reach for by default is the right one anyway. A layoff post does not want a stock photograph of a sunrise.

Now the limitation. The job-search topic's own top decile is 8 posts from 6 authors, and its top quartile is 21 posts from 7 authors. Both fall below the eight-author floor we hold ourselves to, so we do not report them. We cannot characterise the winning tail.

The bottom half we can report: 45 posts from 19 authors, which clears the floor. Median 60 reactions and 7 comments. They put “you” in the hook 26.7% of the time against 46.1% across the whole topic, carry four or more hashtags 55.6% of the time, and 28.9% are shared article links. The weak end of job-search content is more tag-heavy, more link-shaped, and less interested in the reader. A failure mode rather than a recipe, which is still worth having.

For the winning pattern, career-growth is the nearest large topic: 1,389 posts from 50 authors, its own top decile of 138 posts from 19 authors against its own bottom half of 695 posts from 33 authors. Within-topic, career-growth against career-growth.

The median career-growth post in that top decile earned 111 comments. In the bottom half, 6. Reactions moved from 78 to 354, a wide gap, but the comment gap is far wider, and comments are what a layoff post needs, because a comment is where a name gets written down. The same shape holds cohort-wide: a top-decile median of 235 reactions and 72 comments against 80 and 5. Every writing rule here is really a rule about the comment box. More on that in the comments playbook.

Two things carry over cleanly. Address the reader: second person runs 64.5% in the winning career-growth posts against 34.4% in the weakest. And keep the tags down: four or more appear in 46.5% of the weakest against 34.1% of the strongest, the same direction the cohort shows at 41.9% versus 25.9%. Seven hashtags reads as a broadcast, which is the wrong register for a post asking for personal help.

Should you turn on the LinkedIn Open To Work banner?

There are three settings, and most of the argument online happens because people are comparing different ones. From LinkedIn's help page on letting recruiters know you are open to work, here is what each does.

That middle row deserves reading twice. LinkedIn says in its own documentation that it “can't guarantee complete privacy” from recruiters at your current employer. If you are still employed, treat recruiters-only as discreet rather than secret.

Does the #OpenToWork frame actually help or hurt?

The only numbers from anyone with real visibility come from LinkedIn, in a member blog post about the Open to Work feature. Their wording: members who add a public #OpenToWork photo frame “are, on average, 40% more likely to receive InMails from recruiters” and “20% more likely to receive messages from their community”. Elsewhere in the same post: “turning on Open to Work on your LinkedIn profile increases your likelihood of getting a recruiter message by 2X.”

Two caveats belong in the same breath, not in a footnote. The post dates from the COVID period, when the norms around announcing a layoff were unusually forgiving. And LinkedIn is not a neutral party about a LinkedIn feature. These are the numbers we have, they are directionally believable, and they were published by the company that benefits if you believe them.

The counter-argument you will hear is that the green frame makes you look desperate and that recruiters filter it out. I went looking for data behind that claim and found nothing comparable: no sample, no controlled comparison, no recruiter survey with a method attached. It circulates as strongly worded opinion, sometimes from people with real hiring experience, which is not nothing but is not evidence either. I am not going to settle it with an invented number. The claim is unsupported even at the thin level the pro-banner claim is supported.

A recommendation with the conditions attached, since you asked for one:

• Publicly laid off, searching openly: turn the frame on. You have already given up the confidentiality it would have cost you.
• Still employed, quiet search: recruiters only, with the caveat above about colleagues who use Recruiter.
• Senior, small industry, everyone knows everyone: skip the frame. Roles at that level move through introductions, and in a field of two hundred relevant people the signalling cost is real even though nobody has measured it.
• Early or mid career, large field: turn it on. More inbound is straightforwardly good, and you can decline messages.

Either way the frame will not carry your profile on its own. Your headline and the top of your experience do more work than the badge does, which is separate housekeeping covered in the profile optimization guide. Do it before the post, because the post is what sends people to the profile.

How much should you say about why you were let go?

Enough to close the question, then stop. A reader who is not told why will supply a reason, and the default reason people supply is the unflattering one. One clause prevents that: the role was eliminated, the team was cut, the round did not happen. You are not defending yourself. You are removing an ambiguity that would otherwise sit in the reader's head while they decide whether to recommend you.

Say it once, in ordinary words, and do not return to it. A redundancy is a decision about a budget line, not a performance event, and the most useful sentence you can write is the one that says so without sounding like it is protesting. “The role was cut, not the person” does the job in seven words. Three paragraphs of context do not, because length reads as defensiveness whatever the words say.

Specificity buys credibility and it has a cost. Details make you placeable, and they also become a permanent, searchable record attached to your name, written in the worst week you have had in a while. The test: would you be comfortable with this sentence read aloud in a final-round interview eighteen months from now?

As for naming the employer, name it. It is already on your profile, so leaving it out reads as stranger than saying it, and recruiters use it to match you against similar roles. Criticising how the layoff was handled is a separate and permanent decision. The strongest unemployment posts in our dataset are specific about facts rather than feelings.

“Over a hundred jobs without a single call back” says more in nine words than a paragraph of adjectives would. Note what is absent: no hashtag block, no image, no link.

What if you cannot say much for legal reasons?

Say that, once. A separation agreement or a non-disparagement clause is an ordinary thing to have and readers understand it immediately. The error is going quiet in a way that looks evasive, or hinting. Hinting is worse than silence, because it invites the speculation you were trying to avoid.

Exact sentences for the awkward parts. These are mine, not from the dataset.

• The redundancy:“My role was eliminated on the 14th, along with most of my team. It was a budget decision, not a performance one.”
• Shorter:“The role went, not the person.”
• When you cannot say more:“There is more to the story and I am not able to go into it here. Happy to talk about the work itself any time.”
• Asking for an introduction:“If you know someone at any of these, an introduction would help more than anything else I can think of.”
• Asking without begging:“One name is a real favour. No name is completely fine and I will not follow up.”
• Closing the sympathy loop early:“I am all right. Bruised, but all right. What I could use is names.”

That last one earns its place. Readers hesitate to go straight to practical help because it can seem cold. Saying it is what you want gives them permission to skip the condolences.

Should you add a career break to your profile?

Yes, and it is a real profile field rather than a workaround. LinkedIn introduced Career Break as a profile entry in March 2022, with 13 options including layoff, caregiving, health and well-being, and parental leave. In the same announcement LinkedIn reported from its own research that “51% of hirers say they are more likely to contact a candidate that provides context about their career break”.

The practical value is that it turns a gap into a labelled entry, and an unexplained six-month hole is the kind of thing a reviewer notices and quietly resolves against you. Add it when the gap starts, because the field does its work during the months you are still looking.

It is a profile change, not a post, and the two decisions are independent. When you land, the new-role entry is what triggers the congratulations flood, a different set of choices covered in the new job announcement guide.

What actually happens after you publish?

The post is one event. The search is months. It helps to know what the next two days look like so you are not reading them wrong.

First comes a wave of short supportive comments. They feel hollow when you are the one reading them, and they are also the most useful raw material the post produces, because every reply you write is a second impression in front of that person's network. Reply to each one individually and make the reply do something. “Thank you” closes the conversation. “Thanks Priya, do you still know anyone at Form3?” opens one.

Second, the numbers will not correlate with the outcome. A post with 900 reactions can produce nothing and a post with 40 can produce two introductions and a job. The value comes from about five people: the former colleague who now runs a team, the acquaintance who forwards it internally, the recruiter who saves your profile, the stranger who knows the hiring manager. Five hundred reactions is a nice feeling on a bad week. Five people is a search.

Third, sometimes, is scale you did not expect. Posts about unemployment and burnout travel further than most professional content, because so many people have lived it.

One comment for every five reactions is a very high ratio at that size, and it tells you what readers do with this subject: they reply with their own experience. So the conversation will be about the experience rather than your next role, which is exactly why the ask has to be in the post rather than in the replies. Replies also keep a post alive while the feed is deciding how far to distribute it, so being available for the first hour matters more than anything you could have changed in the draft. More on closing a post so that it produces replies in the guide to ending a post.

What should you post two weeks later?

Something new, and preferably not about the layoff. The follow-up exists because the first post reached a fraction of your network, and because a search that goes quiet stops occurring to people. Two weeks is long enough that you are not repeating yourself and short enough that the first post is still in living memory.

• The narrower ask.“I have spoken to four of the seven companies I listed. Still nothing at Wise or Griffin. Anyone?” The progress report makes a repeat ask feel like an update.
• What you have learned about the market. Twenty interviews gives you real observations about how hiring is being done in your function right now, and it does not require you to be the subject.
• The work itself. A teardown, an opinion, a small analysis. Being visibly good at the job is more persuasive than any description of being good at it.
• The shared grievance. Use sparingly, and only when true.

Use that last kind sparingly, because it builds an audience for a position rather than for you. Four in a row makes you the person who complains about recruiters, which is not the association you want when someone is deciding whether to pass your name along. If most of what you want to say falls there, the real post is often about the change you are making, covered in the guide to career change posts. More posts of this kind, with the engagement each earned, are on the job-search examples page.

How to write yours today

Twenty minutes, one sitting, plain text. Here is a five-line skeleton I wrote for this article. It is not a dataset post. It is a shape to start from, then break wherever your own facts are more interesting.

1. The fact.What happened, when, in one sentence. No preamble, no “I have been putting off writing this”.
2. The closure. One clause that removes the ambiguity. Role eliminated, not performance. Then move on.
3. The evidence. What you do, with one specific result attached.
4. The target. The role, the kind of company, the location constraint, and five to fifteen names.
5. The ask. One action, under a minute, as the last line.

If you do not want to write much, and plenty of people reasonably do not, the short version is three sentences and it works. Also mine:

My role at [company] was eliminated on Friday, along with most of the team. I am a [role] with [n] years in [domain], and I am looking for the same thing at somewhere like [company], [company] or [company]. If a name comes to mind, reply with it, and thank you.

Under sixty words, with every component that matters. If writing more feels impossible this week, write that and publish it.

A short check before you post:

• Is there a specific request in the last line that takes under a minute to fulfil?
• Have you named at least five companies?
• Does the first line contain a fact rather than a feeling?
• Is the layoff explained in one clause and never revisited?
• Plain text, no link, one or two hashtags at most?
• Is your headline updated, so people who click through find the right thing?

Then publish, and send ten direct messages to specific people carrying the same ask. The direct messages will outperform the post. The post exists so that they are not the only thing working.

What this data can and cannot tell you

Everything here is correlational. Posts that address the reader do better, but we cannot prove the addressing caused the engagement rather than both being symptoms of a person who writes well. The cohort skews toward established creators, all above 1,000 followers, across 65 accounts. Engagement counts are lifetime totals at the moment of collection and posts differ in age. Every text finding describes the visible fragment above the fold rather than the full post body.

The specific limit here bears repeating. Our job-search topic is 89 posts from 27 authors, and its own winning decile is 8 posts from 6 authors, too few to describe honestly, so we did not describe it. Where this article needed the winning pattern it borrowed from career-growth (1,389 posts, 50 authors) and from the full cohort, and said so each time. If you find a page reporting exactly what the best layoff posts do differently, ask how many authors that is.

The last thing is not about data. A good post is a small advantage in a situation that is mostly about volume, timing, and who happens to be hiring in your function this quarter. Writing a better one will not fix the week you are having. It makes it marginally more likely that the right person sees your name and knows what to do with it, which is the entire and quite limited job of the post. Full methodology is in our study of 12,988 ranked posts.