Verified against Claude · 2026-08-04
Announce that you're job searching without it reading as a distress signal
Turn a layoff, contract ending, or intentional job change into a post that states the situation plainly and gives readers a specific, pattern-matchable role and constraint to act on, instead of a vague "open to opportunities" post that gives connections nothing to actually do.
The prompt
Ready to copy — highlighted parts are example details you can swap.
WHAT ACTUALLY HAPPENED
Laid off two weeks ago as part of a 15% company-wide reduction, nothing performance-related
ROLE AND TYPE OF WORK YOU'RE LOOKING FOR, SPECIFICALLY
Product manager roles at 20-80 person B2B SaaS companies, ideally usage-based pricing products
STRONGEST 1-2 PIECES OF CONCRETE EXPERIENCE
Led the pricing model redesign that took our expansion revenue from flat to 22% quarter-over-quarter growth
HOW MUCH YOU WANT TO SAY ABOUT WHY YOU'RE LOOKING
Brief — one clause naming the layoff, no further detail about the company or circumstances
CONSTRAINTS
Remote only, based in the US Central time zone, available to start immediately
WHY "OPEN TO OPPORTUNITIES" ASKS FOR HELP WITHOUT GIVING ANYONE SOMETHING TO DO
A job-search post's actual job is to give the reader — most of whom are not hiring managers but people who might know one — a specific enough picture of what you do and what you're looking for that they could plausibly think of a real person or opening within a few seconds of reading it. "Open to new opportunities, DM me!" gives a connection nothing concrete to match against their own network, so it gets a few reflexive likes and produces almost no actual referrals.
RULES
1. State Laid off two weeks ago as part of a 15% company-wide reduction, nothing performance-related in one honest sentence, calibrated to Brief — one clause naming the layoff, no further detail about the company or circumstances — a layoff can be stated plainly as a fact, not apologized for or hedged into vagueness; if Brief — one clause naming the layoff, no further detail about the company or circumstances says keep it brief, one clause is enough, but don't omit it entirely if it's true, since vagueness here reads as evasive rather than discreet.
2. Name Product manager roles at 20-80 person B2B SaaS companies, ideally usage-based pricing products specifically enough that a reader could actually pattern-match it against a role they've seen — "something in product" gives a connection nothing; "product manager roles at 20-80 person B2B SaaS companies" gives them something to hold in mind next time they hear of an opening.
3. Lead with Led the pricing model redesign that took our expansion revenue from flat to 22% quarter-over-quarter growth as evidence, not a resume-style list — one or two specific, verifiable things you actually did, not a compressed list of every skill.
4. State Remote only, based in the US Central time zone, available to start immediately plainly and early enough that a reader doesn't waste a referral on something that doesn't fit — remote-only, a location, a start date. Vagueness here wastes goodwill on mismatches.
5. Close with the single easiest action for a reader to take — not "reach out" in the abstract, but something concrete: forward this to someone specific, comment with a company name, or a direct link. A lower-effort ask gets more actual referrals than a broad one.
TONE CONSTRAINT
Do not include false confidence language ("excited for this next chapter!") if Brief — one clause naming the layoff, no further detail about the company or circumstances and Laid off two weeks ago as part of a 15% company-wide reduction, nothing performance-related suggest this wasn't voluntary — forced positivity reads as inauthentic to exactly the audience whose help you're asking for, and can cost more credibility than a plain, calm statement of fact.
OUTPUT
The post, then one line noting whether Product manager roles at 20-80 person B2B SaaS companies, ideally usage-based pricing products as given is specific enough for a reader to actually pattern-match against, or still too broad — and if too broad, what would need to be narrowed.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The overwhelming majority of the people who see this post are not hiring managers with an open req — they're people who might, days or weeks later, hear someone mention a role that fits. The entire value of the post is whether it left them with a specific enough mental tag to retrieve later, and "open to opportunities" creates no retrievable tag at all, which is the actual reason those posts generate likes but almost no real referrals.
Calibrating honesty about {{situation}} to {{disclosure_level}} instead of defaulting to forced positivity matters because LinkedIn audiences have grown specifically skeptical of upbeat layoff announcements — a post that performs enthusiasm about an involuntary situation reads as inauthentic to the same network being asked for help, while a plainly stated, unapologetic fact tends to generate more genuine responses because it doesn't ask the reader to perform belief in a framing they can see through.
The low-effort-action close targets a real behavioral pattern: most people who could help with a referral won't take an ambiguous, multi-step action ("reach out if you know anyone"), but will take a specific, near-zero-effort one — forward this, comment a company name. Narrowing the ask to the smallest unit of help someone could give is what converts passive sympathy into an actual lead days after the post has left the feed.
Requiring {{constraints}} to be stated plainly and early, rather than left to a comment-thread clarification later, protects the referral pipeline itself: a reader who thinks of a great-sounding opening but doesn't know it's on-site in a city you can't relocate to either wastes a referral making the introduction anyway, or — more commonly — decides it's probably not a fit and says nothing, when a two-second constraint check up front would have told them either way before they had to guess.
What you get back
Two weeks ago I was part of a 15% reduction — nothing about my role or performance, just a broader cut.
I'm looking for product manager roles at 20-80 person B2B SaaS companies, specifically ones working on usage-based pricing.
Most recently, I led a pricing model redesign that took our expansion revenue from flat to 22% quarter-over-quarter growth — the kind of problem I actually want to keep solving.
Remote only, US Central time zone, available to start immediately.
If a role like this crosses your feed in the next few weeks, a comment with the company name would mean more than you'd think.
Verified against
Claude Sonnet 5 · 2026-08-04
ChatGPT GPT-5.1 · 2026-08-05
Changelog
- 2026-08-05 — Initial publish for the rewritten linkedin category, verified against Claude (Sonnet 5) and ChatGPT (GPT-5.1).
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
