I've written maybe forty job descriptions, and the ones that attracted the right candidates had something in common: they read like a spec, not a billboard. They said what the person would own, what they needed, and what "good" looked like β and they didn't quietly filter out half the applicants with words like "ninja" or "rockstar."
So when I built a generator for this, the goal wasn't "write faster." It was "write the same structure every time so nothing important falls out."
Structure first, words second
The generator asks for role, level, and must-haves, then produces responsibilities and requirements as two separate lists. That separation sounds trivial and is not. Requirements inflate β every manager adds "and also proficient in our internal tool no one has heard of" β and responsibilities shrink. Splitting them forces a check: is this line a thing they'll do , or a thing they must have ?β¦