Getting Forty Applications and One Good One? Write the Posting So the Wrong People Stop Reading

Ask a hiring manager at a small company what went wrong with the last search and the answer is almost never that nobody applied. It is that forty people applied, six were interviewed, one was hired, and that person left in month three because the schedule turned out not to be the schedule they thought they had agreed to. A posting has one job before it has any other, which is to make the wrong people stop reading, and most postings are written to do the exact opposite. Honest filtering is cheaper than sorting, and in a growing number of places parts of it are no longer optional anyway.

The Four Lines That Do Most of the Screening

Most of the screening power in a posting sits in four sentences, and they belong near the top rather than underneath a paragraph about culture. The first is the range along with the basis for it, meaning not only the numbers but what moves a candidate within them, because a spread with a stated reason reads as considered rather than as an opening position. The second is the actual schedule: days, hours, and specifically whether evenings, weekends, an on call rotation or seasonal overtime are part of the work rather than an occasional exception.

The third is where the work happens. That means an address or at minimum a town, plus the honest version of any remote arrangement, since hybrid means nothing at all without the number of days and a statement of who decides them. The fourth is the physical and practical requirement, covering lifting, driving, a valid license, standing for a full shift, or working outdoors in July. Stating those accurately is a courtesy to applicants and also the correct way to handle them, since a requirement discovered in week one is a resignation and a requirement stated in the posting is a filter.

What the Posted Range Requirement Changed

Several states and a number of cities now require a salary or hourly range in the posting itself, and the details differ enough that an employer hiring across state lines cannot rely on a single template. Some rules attach to any posting for a role that could be performed in the state, some apply only above an employee count threshold, some require a good faith range together with a description of benefits, and some bite only when an applicant asks. The practical consequence for a small employer is that the local rule matters far more than the general direction of travel.

Nothing federal requires a posted range, and it is worth being precise about why: the wage and hour standards enforced by the Department of Labor put a floor under what an employer pays rather than a rule about what it advertises, so the question belongs to the state labor office and a short call there is faster than reading the statute. Employers who post ranges voluntarily where no rule requires it report the same two effects with some consistency. Application volume falls, and the share of applicants who accept an offer rises, because nobody reaches the offer stage carrying a number the employer was never going to meet.

Language That Screens Out the People You Wanted

Requirements do more filtering than employers intend, and most of it happens invisibly. A degree listed as required for a role where experience would serve removes a large share of qualified applicants, many of whom will not apply against a requirement they do not meet even where the employer would happily have flexed on it. Long lists of preferred qualifications work the same way and land unevenly across different groups of readers, so a posting can end up selecting for confidence rather than for competence without anyone having intended that outcome.

Some phrasing carries legal exposure alongside the cost. Descriptions implying a preferred age, phrases suggesting a particular background, and physical requirements that are not genuinely essential to the work all invite trouble that is easier to avoid than to answer. The working rule practitioners use is that a stated requirement should be defensible as necessary to perform the job, which is also how essential functions are meant to be described under the Americans with Disabilities Act. Requirements that are merely traditional cost money and protect nothing, and they are worth deleting on both counts.

Two Questions on the Form Do More Than a Long Application

The posting filters, and then the application form filters again, and two short free text questions do more work than a page of fields. The first asks the applicant to describe a piece of work of the kind this role involves and what they would do differently now, which separates people who have done the work from people who have been near it and is difficult to answer generically. The second asks whether the stated schedule works for them and, if there is a constraint, what it is. Asking directly produces honest answers and surfaces the conflict before an offer rather than in week three.

What a Short Posting Looks Like

The structure that performs is unglamorous: what the job is, what it pays, when and where it happens, what a person must be able to do, and how to apply, which fits comfortably inside four hundred words with the company narrative left on the careers page for anyone who wants it. One addition earns its space, and that is a sentence describing what the first ninety days look like, because it is concrete, hard to fake, and forces the hiring manager to decide what those ninety days are. Twelve applications from people who understood the job beats sixty from people who did not, and the sorting is the part that comes out of your own week.