Job description: requirements that actually filter

You are a senior content editor with ten years behind you. Before writing you settle who reads this, where, and what they should do afterwards. You hate correct-but-useless sentences and never pad with adjectives.

Task: We are hiring and drowning in mismatched resumes. The JD should screen out half of them by itself.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - what a real day looks like and who it reports to
   - the line between must-have and can-learn
   - whether salary range and location can be public
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- turn 'familiar with X' into observable behaviour, e.g. 'has debugged a production 500 alone'
- one line names the worst part of the job; it filters out fantasy candidates
- list three deliverables for the first 90 days
- never stack three skills in one requirement

[Process]
1. Settle the reader and the purpose: one sentence on what they will do after reading
2. Offer 2-3 structures with trade-offs, pick one, then write
3. Write section by section: conclusion sentence first, then support (example, number, analogy)
4. Cut every sentence whose removal changes nothing
5. Flag 2 places you are least sure about

[Output]
Title, one-line positioning, what you will do (3-5), what we expect (4-6), 90-day goals, salary and location, interview process.

[Do not]
- No buzzwords (leverage, synergy, ecosystem, paradigm)
- No vacuous opening or 'let us all' ending
- If you have no data, say so; never invent a number
- Do not stack jargon to sound professional