An honest job posting is less a writing problem than a filing problem. The wording that screens people out fairly is the wording you can defend later, and that means deciding the pay range, the real requirements and the screening criteria before the posting goes up, then keeping a copy of what you published. The complication is that several of those decisions are set by state or city rule rather than by you, and the rule that applies is often the one where the work can be performed, not the one where your office sits.
Here are five things to check, in the order they usually matter.
1. Whether you are required to publish a pay range, and which state decides
A growing number of states and cities require employers to include a pay range, and sometimes a description of benefits, in the posting itself. The thresholds differ. Some apply to employers of any size, some only above a headcount. Some cover any role that could be performed in the state, which is the clause that catches remote and hybrid postings written by an employer with no office there.
Two practical consequences. First, if you advertise a role as remote without geographic limits, assume the strictest applicable rule rather than your home state's. Second, a range published in good faith should be one you can explain: what moves a candidate to the top of it, and what the number is based on. A range so wide it carries no information tends to produce applications from people at both ends, which is the opposite of filtering.
The tool here is small. Keep a one-page sheet listing every state and city where you have employees or will accept them, with a line for each on pay range disclosure, and the date you last checked it. Revisit it when you open a role, not quarterly.
2. The requirements list, split into two columns before anyone applies
Write the requirements as two columns: what a person must be able to do unsupervised in week one, and what you will teach. Then publish both, labeled. This does more honest filtering than any phrasing trick, because it tells a candidate who is strong but incomplete that they are not disqualified, and tells a candidate who cannot do column one that they are.
The paperwork that makes this stick is a scoring rubric written at the same time as the posting. Three to six criteria, each with a short description of what a weak, adequate and strong answer looks like. Decide the weighting before the first resume arrives. If two people review applications, the rubric is what keeps them filtering on the same thing.
It also matters in a dispute. A rubric dated before the posting went live is evidence that your criteria were set by the job rather than by the applicants.
3. Schedule and location language, which some cities regulate directly
"Flexible hours" and "hybrid" are the two phrases most likely to mean something different to the reader than to you. Write the actual shape: days on site, core hours, whether evenings or weekends are in the rotation, and how far in advance the schedule is posted.
That last point is not only courtesy. Several cities and at least one state have predictable scheduling ordinances covering particular industries, typically retail, food service and hospitality above a size threshold. Those rules govern advance notice of schedules and, in some places, premium pay for changes. If you operate in one of those jurisdictions, the posting should describe a schedule practice you can actually run.
For multi-site employers, the cleanest approach is a short location block at the top of the posting that names the city and state and the on-site expectation. It lets a candidate self-select in one line, and it establishes which local rules you were writing under.
4. The questions you are not permitted to ask, and when you may ask them
Three categories come up repeatedly and vary by jurisdiction. Salary history: many states and cities prohibit asking, and some prohibit relying on it even if volunteered. Criminal history: "ban the box" rules commonly bar the question on an initial application and push any background check to after a conditional offer, with a required individualized assessment and notice before withdrawal. Automated screening: New York City requires employers using automated employment decision tools to have a bias audit and to give candidates notice, and other jurisdictions have taken up similar questions.
Check your application form, not just the posting. The form is usually where a prohibited question survives, because it was built once and never reviewed. The Department of Labor oversees federal wage, hour and recordkeeping obligations for employers, and state labor agencies publish their own posting and application requirements, so the source of truth is typically two documents, not one.
5. The record of what you actually published
Save a PDF or screenshot of the live posting, with the date, every board it ran on, and the closing date. Keep the rubric, the interview notes and the list of applicants with the stage each reached. Retention periods for application records are set by federal rule and, in some states, by longer state rules, so keep to the longer one.
This is unglamorous and takes about ten minutes per role. It is also the only thing that makes a filtering decision explainable six months later, whether the question comes from an agency, an attorney, or a hiring manager who wants to know why the shortlist looked the way it did.
A posting built this way reads plainer than most. It names the pay, the schedule, the location and the two or three things that genuinely decide the hire, and it is backed by a folder that says what you did and when. Fewer applications arrive. More of them are from people you would interview.
