How to write a job post people can understand

Say what the job is

A candidate is trying to decide whether the work, level, location, schedule, pay, and requirements make sense for them. Put those answers near the top. A long company story will not fix a vague role.

Open with a plain sentence about what the person will own, who they will work with, and why the role exists. Then describe the work they are expected to handle early in the role.

Separate must-haves from nice-to-haves

For every requirement, ask which hiring decision it helps you make. If the team cannot answer, remove it or say what you actually mean.

1. The workDescribe the recurring responsibilities and decisions, not every task anyone on the team has ever done.
2. Must-havesInclude what is genuinely needed to do the job or meet a legal, safety, or licensing requirement.
3. Nice-to-havesList experience that would help but should not automatically remove an otherwise strong candidate.
4. What you provideExplain the training, tools, supervision, and onboarding the person will receive.

Describe essential functions clearly

EEOC guidance focuses on whether a person can perform the job's essential functions, with or without reasonable accommodation. Describe the function or result the role requires instead of assuming there is only one way to do it.

If the job truly requires a certain schedule, travel, lifting, environment, license, or on-site presence, explain why. Remove physical or availability language copied from another role when it does not apply here.

Include the details people need

• Location, remote or hybrid expectations, and expected travel
• Pay range and how placement is decided, where required by law or provided by your organization
• Schedule, shift, on-call, or seasonal expectations
• Who the role reports to and the team it joins
• Major tools, equipment, customers, or working conditions
• Interview stages and the timing you can reasonably explain
• How to request an accommodation for the application process

Read it like an applicant

If the answer to any of those questions is no, fix the post before publishing it. The details help people decide whether to apply and give interviewers a better starting point.

• Can someone explain the job after reading the post once?
• Does every requirement connect to work the person will actually do?
• Are you using a degree or title as a shortcut for skills that can be shown another way?
• Would the current team recognize this as their job?
• Will the interview evaluate what the post says matters?