How to write a LinkedIn post after a layoff (3 full examples)
Published May 21, 2026 · 8 min read
What this guide covers
If you’re trying to figure out how to write a LinkedIn post after a layoff, you’ve probably already seen a dozen of them in your feed this month. Most follow the same shape: “Today is a hard day to write about,” a paragraph of gratitude, a row of broken-heart emoji, and a closing line asking for “any opportunities.” Those posts collect sympathy reactions and very few actual introductions. This guide is about writing the other kind: the post that activates your network and produces real leads.
Below are 3 full before-and-after rewrites of layoff announcement posts in 2026, one for a senior IC, one for a manager, and one for a junior person 18 months into their career. Each shows the emotional version most people publish and the confident version that does the job better. All examples are illustrative; company names appear because specificity reads as credible.
For the wider context (everything else to update on your profile, and in what order), see the pillar guide and what to put on LinkedIn when unemployed.
Should you post at all?
The honest answer: a layoff post is optional, and skipping it is a perfectly good choice. Plenty of senior people never post about being laid off, and their search goes fine, because recruiters find them through the profile and through warm intros, not through the feed.
But a layoff post does one thing nothing else does. It activates your entire network in a single moment. Every former colleague, every old manager, every loose connection sees it at once, and a good post gives them a concrete way to help. If you have a network worth activating, and most tech workers do, the post is worth writing.
The one real precondition: write it from clarity, not from fresh shock. A post published the afternoon of the layoff tends to carry the emotion of that afternoon. A post published a few days later, after the severance paperwork is sorted and the initial panic has passed, reads as composed. We’ll come back to timing near the end.
What a strong layoff post does
A strong layoff announcement does three things, in this order:
- Establishes credibility fast. Opens with what you built, where, and recently enough to matter. Not the news.
- States the layoff matter-of-factly. One sentence. No apology, no 'sad to share,' no framing it as a personal failure.
- Ends with a specific ask. Concrete enough that a reader immediately thinks of a particular company or person.
The order matters. Leading with the news (“I was laid off”) frames the entire post around loss. Leading with the work frames it around what you can do for the next team, and the layoff becomes a single fact in the middle rather than the headline. The closing ask is what converts attention into action: a vague ask gets vague help, a specific ask gets warm introductions.
Want to rewrite yours? Facet is a free tool that rewrites LinkedIn layoff posts, headlines, About sections, and resume bullets. Paste what you have, get three rewrites in different angles, copy the one that fits. No signup, no email, nothing stored.
Try Facet →3 full post rewrites
Each “before” below is written in the pattern we see most often: emotional opening, gratitude paragraph, vague ask. Each “after” is the same person’s situation, rewritten to lead with the work and close with something a reader can act on.
Today is one of the hardest days of my career to write about. 💔 After 5 incredible years at Datadog, I learned this week that my role has been eliminated as part of the latest round of layoffs. I'm so grateful for the journey, the brilliant people I got to work alongside, and everything this chapter taught me. Saying goodbye to this team is heartbreaking. I'm now open to new opportunities and would be grateful for any leads, referrals, or kind words. Please reach out if you know of anything!
For the last 5 years I was a senior engineer on Datadog's observability platform. I owned the logs ingestion pipeline, took it from 2M to 14M events per second, and cut on-call pages for the team by roughly 60% along the way. This week my role was eliminated as part of Datadog's restructuring. What's next: a senior or staff backend role at an infrastructure or developer-tools company, ideally Series C or later, where reliability is a first-class concern and the team is small enough that I still own real surface area. I write Go and Rust. US-remote or NYC. If you're hiring for something like that, or know a team that is, reply here or DM me.
Heartbroken to share that after 4 amazing years at Shopify, I've been impacted by this week's layoffs. 😞 Leading this team has been the honor of my career. I'm so proud of every single person I got to manage and mentor, and I'm grateful beyond words for the opportunity. I'm now looking for my next leadership opportunity. Open to engineering management roles anywhere. If you have any leads or would be willing to make an introduction, I would be endlessly grateful. 🙏
For the last 4 years I led an engineering team on Shopify's merchant platform. I grew the team from 6 to 19 engineers, shipped the checkout-extensibility platform now used by thousands of apps, and built 3 engineers from mid-level to senior in that window. This week my role was eliminated in Shopify's latest restructuring. What's next: an engineering management or director role at a B2B SaaS or commerce company, Series B to D, somewhere between 80 and 400 engineers. I'm best on teams shipping platform or infrastructure work where the management job is as much about technical judgment as it is about people. US-remote or Toronto. If your team is hiring at that level, or you know one that is, reply or DM.
I'm honestly devastated. 💔 I was just starting to find my footing and only 18 months into my career when I found out my role has been cut. This was my first real job in tech and I gave it everything. I'm so grateful to everyone who took a chance on me and helped me grow. I'm now looking for anything I can find. Truly open to any design role, any company, any location. Please, if you know of anything at all or can make an intro, I would be so grateful. I'll take whatever I can get. 🙏
The last 18 months were my first job in tech, as a product designer at Brightline, a Series B health startup. In that time I shipped the onboarding redesign that lifted week-1 activation 22%, owned the design system component library, and ran usability testing for the mobile app rebuild. This week my role was cut as part of a company-wide reduction. What's next: a product design role at a startup or mid-size company where I'll work alongside a senior or staff designer I can keep learning from. I'm strongest on consumer and B2B product work, comfortable in Figma and prototyping in code. Open to remote or anywhere in the Boston area. If your team is hiring a designer at that level, I'd value the conversation. Reply or DM.
Notice the junior example doesn’t pretend to be senior. It names real, concrete work (an activation metric, a component library, usability testing) and makes an ask calibrated to the level: a role alongside a senior designer to learn from. Confidence at the junior level isn’t about claiming scope you don’t have. It’s about stating the scope you do have without apology, and dropping “I’ll take whatever I can get,” which reads as desperate and, counterintuitively, makes people less likely to help.
What to strip out, no matter how genuine the feeling
None of the phrases below are wrong to feel. They’re wrong to publish, because they mark the post as written by someone newly laid off and still raw, which lowers the odds it gets shared and lowers the odds it lands a role.
- "Today is one of the hardest days of my career."
- "I'm sad / heartbroken / devastated to share..."
- "I'm so grateful for the journey and all my incredible colleagues."
- "Open to any opportunities, please reach out if you know of anything."
- "I'll take whatever I can get" / "anything at all."
- Heavy emoji, especially broken hearts and folded hands.
The goal of the post is not to process the layoff. That’s what your group chats, your friends, and your own time are for. The goal of the post is to activate your network. In that specific job, on that specific platform, confidence travels further than vulnerability. A reader who sees a composed, specific post thinks “I should help this person.” A reader who sees an emotional one thinks “that’s sad” and scrolls on.
Timing, and what to do after you post
Two timing rules. First, update your profile before you post. The post drives traffic to your profile, and a recruiter who clicks through to a headline that still says your old job, with no current-role line and an unchanged About section, sees a mismatch. Fix the headline, the current role line, and the About section first. The order for that lives in what to put on LinkedIn when unemployed, and for the About section specifically, see the LinkedIn About section examples after a layoff.
Second, wait 3 to 7 days after the layoff before posting. Long enough that the writing reads as composed rather than reactive. Short enough that the news is still current and your network is still paying attention.
After the post goes up:
- Reply to every substantive comment. The post's reach grows with engagement, and a thoughtful reply often turns a comment into a real intro.
- When someone offers to help, give them something concrete to act on. 'Do you know anyone at a Series C devtools company?' beats 'thanks, I appreciate it.'
- Don't delete the post when you land a role. Update it with a short note. The thread is a record of who showed up, and that's worth keeping.
Common mistakes
The recurring ones, in order of how much they cost you:
- Leading with the news instead of the work. Frames the whole post around loss.
- A vague closing ask. 'Open to opportunities' gives readers nothing to act on.
- Posting before the profile is updated. The post sends traffic to a profile that isn't ready.
- Writing it the day of the layoff. The emotion of that day ends up in the post.
- Listing everything you're open to. A post that says 'any design role, any company, any location' reads as unfocused, even when the flexibility is real.
- Over-claiming at the junior level. Confidence is stating real scope plainly, not inventing seniority.
Frequently asked questions
Want to rewrite yours? Facet is a free tool that rewrites LinkedIn layoff posts, headlines, About sections, and resume bullets. Paste what you have, get three rewrites in different angles, copy the one that fits. No signup, no email, nothing stored.
Try Facet →