Writing job descriptions that parse well and read well

A job description has two audiences that rarely get considered together. The first is a person on a phone deciding in about eight seconds whether to keep reading. The second is software: the job board search index that decides who sees the post, and the ATS that scores applicants against it. The good news is that both audiences want the same thing. Clear structure, plain language, and requirements stated as requirements. This guide shows how to write a posting that works for both.

Structure the machines and the people both like

Parsers and readers both look for headings. A posting that is one long paragraph is hard to skim and hard to extract from. Use the same five sections every time, in the same order:

1. 01Title and location, using the words a candidate would search for. "Diesel Technician, Reno NV" beats "Fleet Maintenance Specialist II."
2. 02Two or three sentences on what the job actually is, day to day.
3. 03Requirements, as a bulleted list. One requirement per line.
4. 04Nice to have, as a separate bulleted list. Never mix these with requirements.
5. 05Pay, schedule, benefits and how to apply. Put the pay range in. Postings with a visible range consistently draw more applicants, and in many states it is required anyway.

That last point about lists deserves emphasis. When requirements live in a list, Apex ATS can attach each line to a scored requirement in about a minute. When they are buried in prose like "the ideal candidate will bring several years of experience along with familiarity with modern diagnostic tools," someone has to untangle what is actually required, and applicants have to guess too.

Name the requirement, not the adjective

Adjectives do not parse and do not screen. "Strong communicator" cannot be matched against a resume and cannot be honestly self-assessed by an applicant. Replace each adjective with the observable thing behind it:

• "Experienced" becomes "3+ years in a customer-facing retail role."
• "Tech savvy" becomes "Comfortable using a handheld scanner and a warehouse management system."
• "Detail oriented" becomes "Has completed daily cycle counts or similar accuracy-checked work."
• "Certified" becomes the actual certification name: "OSHA 10," "ServSafe Manager," "CompTIA A+."

Spell out acronyms once, then use the short form. "Certified Nursing Assistant (CNA)" gives the parser and the search index both variants, which means a resume that says either one will match.

Cut the internal jargon

Your company calls the role a "Guest Experience Ambassador Level 2." Nobody searches for that. Every job board and every ATS ranks on the words applicants actually use. Use your internal title in the HRIS if you must, but post with the market title. The same goes for department names, internal system names and grade levels. If a phrase would not make sense to someone who has never worked for you, it should not be in the posting.

The best job description I ever wrote was the one I read aloud to a driver in the break room. Every sentence he frowned at, I cut.

Fleet recruiting manager, illustrative

A before and after

Before: "We are seeking a dynamic, self-motivated warehouse professional to join our growing team. The ideal candidate will have relevant experience, a strong work ethic, and the ability to thrive in a fast-paced environment. Forklift experience preferred. Competitive pay."

After: "Warehouse Associate, Night Shift, Columbus OH. You will pick and pack orders, load trailers, and keep your zone counted and clean. Requirements: 1+ year in a warehouse or distribution role; able to lift 50 lbs repeatedly; available Sunday to Thursday, 9pm to 5:30am. Nice to have: sit-down forklift certification. Pay: $19.50 to $21.00 per hour plus $1.50 night differential, paid weekly. Apply in under 3 minutes from your phone."

The second version is shorter, tells the applicant what they need to know, and hands the ATS three clean requirements and one weighted skill. It also stops wasting the time of people who cannot work nights, which is a kindness to them and to you.

A quick checklist before you post

• Title uses the words a candidate would type into a search box.
• Location is a real city, not "multiple locations."
• Requirements and nice-to-haves are separate bulleted lists.
• Every requirement is a noun or a number, not an adjective.
• Acronyms are expanded once.
• Pay range and schedule are stated.
• No sentence would confuse someone who does not work for you.
• The whole thing reads in under 60 seconds on a phone.

Write it once this way and it becomes the template for the next hundred postings. Multi-posting sends the same clean text to every board and social page in one click, so the effort you spend on the words pays off everywhere the job appears. Good writing and good parsing are not in tension. They are the same discipline.