Verified against Claude · 2026-07-31
Write a LinkedIn hiring post that gets read, not scrolled past
Turn a job opening into a post-native hiring announcement that leads with the real problem the hire will own and names one genuinely hard part of the role, distinct from a pasted job description with a company logo attached.
The prompt
Ready to copy — highlighted parts are example details you can swap.
ROLE
Senior Backend Engineer
WHAT THIS PERSON WILL ACTUALLY SPEND TIME DOING
Rebuild our billing pipeline off a legacy system that breaks under load spikes
TEAM AND COMPANY CONTEXT
Team of 4 engineers, no dedicated DevOps, we ship every Friday
WHAT'S GENUINELY DIFFERENT ABOUT THIS ROLE, IF ANYTHING
You would be the first backend hire with real ownership over architecture
HOW TO APPLY
DM me directly or apply at example.com/careers/backend-engineer
WHY A PASTED JOB DESCRIPTION GETS SCROLLED PAST
A candidate actively looking sees dozens of nearly identical hiring posts in a single feed session, most of which are a job description with a company logo attached. The post's only real job is to give the right candidate a reason to recognize themselves in the first line — leading with the actual problem this hire will own does that; leading with the title or "We're hiring!" does not, because both of those are true of every other post in the same feed session.
STRUCTURE
1. HOOK — lead with the real problem this hire will own or solve, specific enough that the right candidate recognizes it immediately, never "We're hiring a Senior Backend Engineer!" or any framing that announces the post's category before delivering its content.
2. A TYPICAL WEEK — 2-3 concrete things this person will actually do, drawn from Rebuild our billing pipeline off a legacy system that breaks under load spikes, not a list of responsibilities that reads like it was lifted from a generic job-description template for this title.
3. ONE HONEST DIFFICULTY — state one genuinely hard part of the role, not a fake weakness dressed up as a positive ("you'll work with passionate people" is not a difficulty, it's a compliment wearing a difficulty's clothes). Name an actual constraint, gap, or hard tradeoff a candidate should walk in knowing about.
4. ONE TRUE, SPECIFIC DETAIL about the team or company, grounded in something real from Team of 4 engineers, no dedicated DevOps, we ship every Friday — never a generic "fast-paced, dynamic environment" that could describe any company posting any job.
5. A SINGLE CLEAR NEXT ACTION — exactly what's given in DM me directly or apply at example.com/careers/backend-engineer, stated once, clearly, at the end.
BANNED PHRASES
Do not use "rockstar," "ninja," "wear many hats," "work hard play hard," "fast-paced environment," or any close variant of these — they function as a documented candidate-repellent signal precisely because every other recruiting post on the platform uses the same handful of phrases, so a post using them reads as generated from the same template as everything the candidate is already scrolling past.
SELF-CHECK
After drafting, review the post specifically against the banned-phrase list above and flag if any snuck in under a slightly different wording (a synonym for "wears many hats," for instance) rather than the exact phrase — the intent behind the ban matters more than the literal string match.
OUTPUT
The finished post, followed by a confirmation that the self-check ran and found nothing from the banned list, or a note on what was caught and fixed.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
A hiring post competing against dozens of visually near-identical job-description-with-a-logo posts in the same feed session has to win in the first line specifically, because that's the only part of the post most candidates will see before deciding whether to keep reading. Leading with the actual problem the hire will own, instead of the job title, is what lets the right candidate self-select in based on content rather than a title match alone, which is a stronger and faster filter than any title could provide by itself. Including one genuinely hard part of the role is counterintuitive but mechanically important: omitting the honest difficulty doesn't make the role look more attractive, it makes the entire post read as less trustworthy, because every experienced candidate already assumes every role has real difficulties, and a post with none listed reads as either naive or dishonest about what the job actually involves — naming one difficulty plainly is what signals the rest of the post's claims are probably honest too. Banning specific corporate hiring clichés and requiring an explicit self-check against them targets a real, documented pattern: phrases like "wears many hats" and "fast-paced environment" have become recognizable candidate-repellent signals precisely because they're used interchangeably across thousands of otherwise-different job posts, which means using them costs credibility regardless of how good the actual role is — the self-check step exists because these phrases are common enough that they slip in as filler even when the rest of the draft is genuinely specific. Requiring the specific team or company detail to be grounded in {{team_or_company_context}}, rather than allowed to default to generic descriptive language, matters because a specific true detail — "4 engineers, no dedicated DevOps, ship every Friday" — gives a candidate something concrete to evaluate fit against, while "fast-paced, dynamic environment" gives them nothing to actually assess. The second phrase is compatible with almost any company, which is precisely why it communicates nothing.
What you get back
Our billing pipeline breaks every time we get a traffic spike, and right now that's a 2am page for whoever's on call. We're hiring a senior backend engineer to rebuild it properly — not patch it again. A typical week: redesigning the queue architecture, pairing with our one other backend engineer on load testing, and making the call on what gets rebuilt first versus what can wait. Honest part: there's no dedicated DevOps here yet, so you'll own more infrastructure decisions than a senior role at a bigger company usually would. We're 4 engineers, ship every Friday, and you'd be the first person with real architectural ownership on this system. DM me or apply at example.com/careers/backend-engineer.
Verified against
Claude Sonnet 5 · 2026-07-31
ChatGPT GPT-5.1 · 2026-08-01
Changelog
- 2026-08-01 — 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
