What this prompt does
This prompt turns a buried technical achievement into a finished, under-200-word LinkedIn post. It assigns the AI the role of a senior engineer who writes well, then forces a specific shape: a hook built on a surprising number, three to five scannable paragraphs, concrete metrics, one generalisable lesson, and a closing question. You feed it three things via [win_description], [audience], and [voice], and it returns a post you could paste straight into the composer.
The structure works because it separates the raw win from the storytelling. [win_description] carries the facts (the latency cut, the cost saved), [audience] aims the framing at the right readers, and [voice] keeps the tone from drifting into corporate speak. By insisting on a real number in the first line and capping the whole thing under 200 words, the prompt fights the two failure modes of engineering posts: vague "improved performance" claims and walls of unbroken text.
When to use it
- You shipped something measurable and want to share it without sounding like a press release.
- A win is sitting in a commit message or a Slack thread and you keep meaning to write it up.
- You are building a professional presence for recruiters and engineering peers at the same time.
- You want a consistent posting voice instead of reinventing the tone each time.
- You need a draft fast and would rather edit than stare at a blank box.
- You want a closing question that actually invites replies rather than a flat sign-off.
Example output
You get a single, ready-to-post block: one punchy first line carrying a real number, a few short paragraphs separated by line breaks, a lesson paragraph that lifts the insight beyond your specific case, and a question at the end. It stays under 200 words, uses at most one or two emojis, and avoids buzzwords. It is a finished post, not an outline or bullet notes.
Pro tips
- Put one concrete metric directly in
[win_description]— the hook is only as strong as the number behind it, so "1.2s to 240ms" beats "made it faster." - Tune
[audience]deliberately: a post for technical recruiters lands differently than one for senior peers, and the framing shifts with it. - Use
[voice]to stop the model from inflating things; values like "direct, humble, no buzzwords" keep it honest. - If the first hook feels generic, re-run with a more counter-intuitive angle on the same win rather than rewording the whole post.
- Keep the lesson paragraph general but earned — it should teach something even to readers who do not care about your specific stack.
- Trim ruthlessly toward the 200-word cap; the constraint is what makes it scannable, so resist re-adding detail the post does not need.
