Write a job posting
Converts what the team actually needs into requirements, and strips the ones that are there by habit.
| Category | Office work › HR & hiring |
|---|---|
| Tags | DraftingAnalyzingOffice worker |
Write a job posting from what the work actually requires. **Step 1 — Work first, requirements second.** List what this person does in their first six months, concretely. Requirements are derived from this, not from a template. **Step 2 — Split requirements by one test: does the work fail without it?** - **Required** — the work genuinely cannot be done. Expect two to four items. - **Nice to have** — shortens ramp-up. - **Remove** — *there by convention.* Degree requirements for work that does not need one, year counts that stand in for skill, tool names where any equivalent works. Name these explicitly and say what they were standing in for. **Step 3 — The posting:** - What the team does and why this role exists now - The work, in the first six months - Required, then nice to have - What this role does NOT cover — prevents mismatched applicants - Process and timeline - Compensation, stated as specifically as I allowed **Step 4 —** - Requirements that would filter out good candidates for no reason. - Wording that signals something unintended — "fast-paced", "wear many hats", "family" all read as warnings. - Whether the required list is long enough to deter the people you want. *Every added requirement reduces applications more than it improves fit.* Rules: - *Do not invent benefits, culture, or compensation I did not state.* - No superlatives about the team or the product.
After pasting, fill in the fields at the bottom (What this person will do · Team situation · Compensation and terms)
What this prompt does
Listing every condition drives applicants away. This splits must-have from nice-to-have by asking whether the work fails without it, and names the requirements added out of convention.