JD checklist

Four things, because they are exactly what a candidate search reads: a job title, a location, a seniority or years-of-experience signal, and a must-have requirements list. Each one is either quoted back to you from your text or reported as missing with a hint on what to add.

No. Nothing is generated. Every line it shows you is an excerpt of the text you pasted, and an excerpt that cannot be found in your text is dropped rather than displayed. If you want a rewrite, this is not that tool.

A job description with no location or no must-have list still reads fine to a person, but it gives a search almost nothing to narrow on, so the resulting shortlist drifts. Fixing the missing field is usually faster than fixing the shortlist. The pay range is checked too, because a growing number of places require one in the posting.

No. The checklist re-reads your own text on this site. It does not run a candidate search, and it does not spend the five samples per network per UTC day used by JD shortlist, talent map, and who is hiring. This network can run the checklist 40 times per UTC day before it asks for a work email. There is no share link, so the posting is never written into a URL.

The server reads the text to produce the response and does not store it. This tab’s history keeps the completed result and edits for Back navigation. Email addresses and phone numbers found in the text are stripped before anything is returned, so a contact line pasted along with the job description is never echoed back.

Run the same text through the JD shortlist. That is the tool that turns the job description into a sample of public people, and it works much better once all four fields are actually present.