Job Description Drafting

Role-specific JDs assembled from your level framework, comp bands, skills taxonomy, and voice tokens - every clause sourced, every comp band parity-checked, and a draft that ships to ATS without a six-round wordsmithing loop.

What the managed workflow does

Pulls from your library

Reads your level framework, comp bands, skills taxonomy, and house voice tokens - drafts the JD from the same approved blocks every other req uses, not from scratch.

Picks the right blocks

From the open req: level + comp band auto-resolve. Skills are picked from your taxonomy with explicit weightings. Voice tokens enforce the house style.

Parity-checks the band

Every JD's comp range checked against the latest band approved by comp committee - drift surfaces before the JD goes to ATS, not at offer time.

Publishes to ATS

Approved drafts ship straight to your ATS with the right boost-feed targeting (LinkedIn, Hired, internal mobility) keyed off level and skill.

JD library → 4 picked snippets → assembled draft, parity-checked

16 TILES · 4 PICKED · L5 · $215–$310K · DRAFT v2

Library inputs

Level framework · IC + mgmtComp band · per levelSkills taxonomy · scopedVoice tokens · house style

What ships per req

Drafted JD · published-readyLevel + comp parity-checkedSkills · graded against scopeATS publish + boost feeds

Library inputs

Level framework. IC + management ladder definitions - what 'L5' means in context, with bar-raising criteria explicit per dimension.
Comp band. Per-level $-bands with floor / target / ceiling, refreshed against benchmark sources, parity-checked.
Skills taxonomy. Scoped skill list per role-type with weighting - what's required, what's nice-to-have, what's coachable.
Voice tokens. House-style style guide - direct, plain, specific, no buzzwords - enforced against every drafted block.

What ships per req

Drafted JD. Published-ready text with sections (mission, role, skills, comp, benefits) assembled from the library - no blank-page wordsmithing.
Parity check. Level + comp + skills validated against your latest approved frameworks before the JD leaves draft state.
Skills callouts. Required vs nice-to-have vs coachable - graded against scope so the panel and recruiter screen on the same bar.
ATS + boost feed. Approved drafts shipped to ATS with the right boost-feed segment per level and skill - internal mobility first, then external sources.

What you get, every week

Days back per req

Median time-to-publish drops from a 5-day wordsmithing loop to under 24 hours - recruiter time goes to candidate conversations, not template wrangling.

Bar parity across the org

Every L5 JD reads against the same level definition. No more 'this team's L5 is harder than that team's L5' calibration drift.

An auditable JD trail

Every drafted JD logs which library blocks it picked, which were overridden, and what the parity check returned - comp committee review and EEO audits read, not reassemble.

See this in your industry