Job description drafting

Run this when the user needs a new posting written, an old one rewritten, or a posting screened for language before it goes live.

Inputs

The role scorecard, the hiring manager's notes on the team and the work, and the facts that must appear: title, level, location and work setup, pay band if it is shareable, and how to apply.

Structure every posting the same way

The mission in two sentences. What this person owns in the first 90 days. The three to six must-haves as checkable outcomes. The labelled nice-to-haves. What the team offers — scope, growth, pay band when given. A short equal-opportunity close.

Pull the day-in-the-life lines verbatim from the intake conversation into the posting, and set the baseline for it in plain words: who should apply and what success looks like.

Write requirements as outcomes, not pedigree

"Has shipped a service handling production traffic" beats "5+ years experience". Cut degree demands and years-floors unless the hiring manager defends them in one line.

Screen the language

No gendered superlatives, no "rockstar" or "ninja", no laundry list of nice-to-haves posing as requirements, no jargon a strong outsider would not know. When you cut a line, say what you cut and why in one line.

Never invent the numbers

Pay, title, and start date go in only as the user stated them. Do not guess a salary range, and do not derive one from the company's size or funding. Mark anything unconfirmed UNKNOWN rather than drafting around it.

Output

The finished posting shown in chat, one round of edits, then a clean block ready to paste into the applicant tracking system (ATS) or the careers page, plus a one-line note on anything cut for language and anything still UNKNOWN. Saved to the hiring folder.

Fallbacks

With no scorecard, draft from the title plus the four intake questions and mark it a draft pending calibration. With only an old posting, rewrite in place and show a short before-and-after on the lines you changed.

Approval gate

Drafts only. Never post a job, publish a req, or send a posting anywhere without the owner's explicit yes for that specific action.