Job Description Rewriter
Rewrites bloated corporate job descriptions into something a real candidate would read and reply to. Cuts filler, keeps requirements, adds specifics.
The prompt
I'll paste a job description. Rewrite it so a strong candidate would actually finish reading and want to apply.
Structure the rewrite as:
**One-line pitch** — what the person will build/do/own, in one sentence.
**About us** (2-3 sentences max) — what the company does, what stage/scale, why this role exists now. Cut the "we're a fast-paced, mission-driven..." fluff.
**What you'll do** (5-7 bullets) — actual responsibilities, phrased as verbs. "Ship the first version of X" not "contribute to the development of X."
**What we're looking for** (5-7 bullets) — real requirements, ranked most-important first. Distinguish "must have" from "nice to have."
**How we work** (3-4 bullets) — the specific stuff that's unusual about working here: remote/office, meeting cadence, decision style, tools, unusual perks that are actually true.
**Compensation** — range if I gave one, "competitive + equity" only if I explicitly told you to skip specifics.
**How to apply** — one line, clear path.
Rules:
- Kill on sight: "rockstar," "ninja," "wear many hats," "fast-paced environment," "self-starter," "passionate."
- Cut duplicated requirements. One "must have strong communication skills" is one too many.
- If a requirement isn't verifiable in an interview, question whether it belongs.
- No generic benefits ("health insurance, PTO"). Only unusual ones ("4-day week trial through 2027").
- Total length: aim for 300-400 words. If the original was 800+, that's a feature.
## How to use it
Paste this prompt, paste your existing JD, get a leaner version. Tell Claude in one line what's specific about the role that isn't obvious from the current JD (e.g., "the last person left after 6 months," or "this role reports directly to the founder").
## Why it works
Bloated JDs signal a bloated company. Rewriting for specificity makes the role sound like a real thing a real person would do, which is what strong candidates need to see before they'll apply. How to use it
I’ll paste a job description. Rewrite it so a strong candidate would actually finish reading and want to apply.
Structure the rewrite as:
One-line pitch — what the person will build/do/own, in one sentence.
About us (2-3 sentences max) — what the company does, what stage/scale, why this role exists now. Cut the “we’re a fast-paced, mission-driven…” fluff.
What you’ll do (5-7 bullets) — actual responsibilities, phrased as verbs. “Ship the first version of X” not “contribute to the development of X.”
What we’re looking for (5-7 bullets) — real requirements, ranked most-important first. Distinguish “must have” from “nice to have.”
How we work (3-4 bullets) — the specific stuff that’s unusual about working here: remote/office, meeting cadence, decision style, tools, unusual perks that are actually true.
Compensation — range if I gave one, “competitive + equity” only if I explicitly told you to skip specifics.
How to apply — one line, clear path.
Rules:
- Kill on sight: “rockstar,” “ninja,” “wear many hats,” “fast-paced environment,” “self-starter,” “passionate.”
- Cut duplicated requirements. One “must have strong communication skills” is one too many.
- If a requirement isn’t verifiable in an interview, question whether it belongs.
- No generic benefits (“health insurance, PTO”). Only unusual ones (“4-day week trial through 2027”).
- Total length: aim for 300-400 words. If the original was 800+, that’s a feature.
How to use it
Paste this prompt, paste your existing JD, get a leaner version. Tell Claude in one line what’s specific about the role that isn’t obvious from the current JD (e.g., “the last person left after 6 months,” or “this role reports directly to the founder”).
Why it works
Bloated JDs signal a bloated company. Rewriting for specificity makes the role sound like a real thing a real person would do, which is what strong candidates need to see before they’ll apply.
✦ More like this
Related prompts
Book Recommender (Honest)
Recommends 3-5 books based on what you actually liked before. No 'Sapiens for the 400th time.' Includes honest reasons and what NOT to expect.
Chart Type Chooser
Given the data you have and the question you're answering, picks the right chart type and explains what to avoid. No dual-axis, no pie chart traps.
Code Refactor Helper
Refactors a function or file without changing behavior. Explains what changed and why, and flags any behavior it wasn't sure about.