Job Description Writer
The role
The posting
Title (title not set) Why this role (say what the role exists to do.) What you will do (list the responsibilities.) What you bring (list the requirements.) Nice to have (nothing separated as optional yet.) Pay and location Pay: (state a range.) Location: (state where the work happens.) How to apply (say what to send and where.)
Checks
No title; candidates search for the role by the name you give it.
No purpose statement; the first paragraph is where a candidate decides whether to read on.
0 responsibilities are too few to describe the role.
No pay stated; postings without a range receive fewer and slower applications.
No location or working arrangement stated.
No application instructions; say what to send and where.
Scope and limits
The checks apply published inclusive-hiring guidance: coded language narrows who applies, a long requirements list filters rather than invites, and salary, location and the application route are what a candidate looks for first.
The list of coded words is a published set, not a complete one, and context decides. Read every flagged line back to yourself before changing it.
The job description writer assembles a posting from your lines and applies the published inclusive-hiring checks: coded language, an over-long requirements list, hidden pay and missing application instructions.
What is Job Description Writer?
The job description writer assembles the posting in the order a candidate reads it: the title, why the role exists, what they will do, what they bring, what is optional, the pay and location, and how to apply. Each section is your text in a fixed place, and the checks are the published inclusive-hiring guidance applied to that text rather than policy invented by the tool.
Coded language is the first check because it has the most evidence behind it. Words such as rockstar, ninja, guru and dominant are documented to narrow the applicant pool without improving the hire, and phrases such as work hard play hard and fast-paced signal a culture rather than a job. The check lists the words it found by name, so the fix is a rewrite of one line rather than a rewrite of the posting.
The requirements list is the second. A list that runs past a dozen items reads as a filter, and a list where nothing is marked nice-to-have tells a strong candidate that there is no route in unless they match every line, including the ones the last holder learned on the job. The builder counts the items, flags the long list and asks for the optional pair of everything that is genuinely optional. Salary is checked because postings without a range receive fewer and slower applications, and location and application instructions are checked because they are the two facts a candidate looks for before reading the rest.
The bullet checks are about the sentences themselves. A responsibility that opens with responsible for hides its verb; the fix is to write the work rather than the duty. A bullet past twenty-five words stops being scannable. Neither check rewrites anything — the lines are yours, and the flags name the ones to revisit.
What the builder cannot do is know the job. It cannot tell which requirements are genuinely required, or whether the salary range is competitive, or whether the culture described by a phrase is accurate. Those are decisions for the person doing the hiring, and the page says so rather than implying that a clean set of checks is a good posting.
The purpose paragraph is the part candidates quote back in interviews, so write it as the outcome rather than the activity. The role exists to make something specific true: the monthly decisions have numbers behind them, the backlog stops growing, the service passes its audit. A purpose that restates the title adds nothing, and the check asks for the paragraph because its absence is the first thing an applicant notices.
Postings also fail on the date. State the closing date and the expected start, because candidates plan around both and a posting without them collects speculative applications rather than applications. The writer leaves those to the application instructions line, where the route and the date sit together; the check fires when the line is empty. A posting that says how to apply but not by when leaves the decision open until it is made elsewhere.
How to use Job Description Writer
- Write the title a candidate would search for and the reason the role exists.
- List the responsibilities, each opening with a verb.
- Split the requirements list and move everything optional into nice-to-have.
- State the salary or range, the location and the arrangement.
- Clear the coded-language and bullet checks before posting.
When to use Job Description Writer vs related tools
Use the job description writer when a role is being posted and the wording will decide who applies: a first hire, a role that has been hard to fill, a posting that has produced applicants who were all alike. The checks are the published consensus rather than house style, which makes them defensible in a hiring review. The candidate-facing pair is the Resume Writer for a plain-text resume and the Cover Letter Builder for the letter that answers the posting. When the role needs a formal brief rather than an advert, the Technical Report Template carries the detail.
Privacy & Security
This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.