A job requirement can discriminate when it screens out people based on a protected trait, such as national origin or disability. The requirements section tells applicants what they must have to be considered, and it also decides who reads the ad and applies. Federal law, including Title VII of the Civil Rights Act, prohibits national origin discrimination in employment, and many states add their own rules on top of it. Some of those state rules are stricter than the federal ones.
Key takeaways
- Tie each requirement to a duty in the job.
- Mark as required only what the work needs on day one, and label the rest as preferred.
- Describe any language requirement as a real communication task.
- Drop any requirement that exists only because of someone else's preference.
- Describe physical, health, and vision lines as tasks, and check state rules for each location.
This post gives you six steps to use before any job ad goes live. Each step is a check you can run on every line of the requirements section. The examples come from federal guidance and from state statutes, and the quoted text links to its source so you can read the full text. This post is general information, not legal advice. For a specific role, ask your HR team or an employment lawyer to review the final ad.
Step 1: Write down what the job actually requires
Start with the work, not the old posting. Pull the duties from the current job description if one exists, from a fresh review with the manager, and from a conversation with someone who has done the job well. For each duty, ask what it takes to do it. The answer might be a skill, a license, a physical task, a schedule, or a body of knowledge. Only those things belong in the requirements section.
Many ads fail this step because they were copied from a previous posting or from a competitor's listing. Over time, lines pile up: a degree that was once required, a number of years that someone thought sounded senior, a personality word that nobody can define. A list like that may have no link to what the role does day to day.
Keep a simple record. Next to each requirement, write the duty it supports. If an applicant or a regulator later asks why a line is in the ad, you should be able to answer in one sentence. The record also helps your team review the ad with a clear head. It turns a debate about preferences into a question about the job.
Try this exercise with your team. Ask each person to name the three things a new hire must do in the first month. Then compare that list to the requirements. Most gaps show up quickly. If the requirements ask for skills nobody uses in those first weeks, check whether they are truly necessary or just habit.
Step 2: Ask whether each requirement is necessary
Separate "must have on day one" from "nice to have." Many ads mix the two, so a qualified person who lacks one extra item never applies. Anything that is not needed to perform the core work should be marked as preferred or dropped. A requirement that is not necessary can screen out capable people for no good reason, and that pattern is exactly what draws scrutiny.
For each item, ask a direct question: if a strong applicant lacked this, could they learn it on the job or do the core tasks well anyway? If the answer is yes, it is probably not a hard requirement. Degrees are a common example. Some roles truly need a specific credential. Many others could be served equally well by documented experience, a skills test, or a portfolio. If you keep a degree requirement, be ready to explain it.
Certifications work the same way. A license that the law requires for the work is a real requirement. A certificate the team likes to see on a resume is a preference. Write the difference into the ad so a reader can tell the two apart.
Years of experience deserve the same scrutiny. A fixed count of years is still a specific number, so ask where it came from. If the honest answer is that it sounded senior, the number is not a requirement. Describe the skill level you need and let applicants show they have it. For example, "Can manage a monthly budget of the size our team handles, and has done so before" tells a reader more than a set number of years of experience.
Finally, watch for lists that are too long. An ad with a long list of must-haves usually has a handful of real requirements and many wishes. Cutting the list makes the ad easier to read and helps you draw from a wider group of people, which is good for the team as well as for compliance.
Illustrative example: trimming a requirement list
A team drafts an ad with 10 requirements for a support role. Checking each line against the day-to-day duties, it keeps 4 as must-haves, marks 3 as preferred, and drops 3 that match no task. The shorter list still covers everything a new hire must do in the first month, and it no longer screens out capable people for reasons the work does not need.
Step 3: Review language requirements closely
Language requirements are one of the most common places where requirement wording goes wrong. Federal guidance on national origin discrimination addresses them directly. The EEOC states that "Generally, an English fluency or English proficiency requirement is permissible only if required for the effective performance of the position for which it is imposed." The same guidance adds that "An individual's lack of fluency in English may interfere with job performance in some circumstances, but not in others."
Put simply, the question is not whether a language is useful. The question is whether the job can be done without it at the level required. A role that involves writing detailed reports in English for an English-speaking team has a clearer case than a role where the core work is physical and the team communicates in another language. The same logic applies to any language. If a job requires a second language, such as a customer-facing role serving clients who speak it, say so and tie it to that work.
Write the requirement to match the actual need. "Writes clear work emails and reports in English" describes a task and can be checked. "Fluent English" is vague. A vague line gives a reviewer room to screen people out for reasons unrelated to the work, and that is the risk you want to remove.
Watch for wording that stands in for language skill. "Clear speaking voice" may be a fair ask for a radio host, but for most jobs it is a proxy for something else. Ask what the phrase actually measures. If the answer is that the person must be understood on the phone by customers, say that instead.
If the language skill is helpful but not essential, list it as preferred. Then let applicants show what they can do. Consider whether you can assess the skill directly, for example with a short writing sample or a conversation with the team, scored on an interview scorecard, rather than guessing from how someone speaks or where they grew up.
Step 4: Don't let other people's preferences shape the requirements
Hiring managers sometimes hear requests like "Customers will be more comfortable with someone who looks like them," or "Our coworkers don't want to work with someone like that." Comments like these tend to show up in a hiring meeting as informal requirements. Federal guidance is clear that they cannot carry legal weight. The EEOC says that "Employers may not rely on the discriminatory preferences of coworkers, customers, or clients as the basis for adverse employment actions in violation of Title VII." It adds that "An employment decision based on the discriminatory preferences of others is itself discriminatory."
That means a requirement that exists only because a customer, client, or coworker would prefer a certain background, accent, or appearance has no place in the ad. The fact that someone else asked for it does not change the analysis. The decision is still yours, and it is still the employer's responsibility.
When a client asks for a particular kind of worker, bring the request to HR or counsel before you respond. Explain what the job actually requires and offer to screen for those things. A client's need can often be translated into a job duty. "Must be able to take phone calls from clients who speak a second language" is a real need tied to the work. A preference based on who the person is should not be translated into the ad at all.
Teams also need to hear the rule in plain words. Share the principle at the start of each hiring kickoff: requirements come from the job, and personal preferences from anyone are not job requirements. This prevents informal comments from turning into formal screens during resume review, where they are harder to spot and easier to repeat.
Step 5: Check disability and health-related requirements
Physical, medical, and vision requirements are another area where small wording choices matter. State definitions of disability vary, so check the one that applies to your location. One state example is useful here: the Kansas statute on disability definitions lists major life activities that "include, but are not limited to, caring for oneself, performing manual tasks, seeing, hearing, eating, sleeping, walking, standing, lifting, bending, speaking, breathing, learning, reading, concentrating, thinking, communicating, and working." The same Kansas statute covers people who are "regarded as having such an impairment," although it also says that this part "shall not apply to impairments that are transitory or minor."
What does this mean for a job ad? Look at any line that describes a physical or mental ability. "Must be able to stand," "must lift heavy boxes," or "must be physically fit" may sound like reasonable descriptions, but they can be written more loosely than the job requires. Describe the task and how often it happens instead. "Stands for most of a shift at the packing station" tells an applicant what the job involves. "Must be physically fit" does not.
The same care applies to mental and learning-related lines. "Must be highly detail-oriented" is a vague trait that a reviewer can read in many ways. "Checks a day's worth of invoices against purchase orders for errors" is a task, and it can be explained to an applicant and assessed in an interview or a short exercise.
A vision requirement is a good case to study. The Kansas statute's annotations summarize a case: "Myopia corrected to 20/20 vision not substantial disability; no violation in failing to hire as police officer." That summary shows that a condition corrected to 20/20 vision was not treated as a substantial disability in that case. It does not mean every vision requirement is lawful. Each one depends on the job and the facts. The lesson for an ad writer is to be specific about the real visual task, such as reading small print on equipment, and to avoid a blanket line about perfect vision that nobody has checked.
The same statute also says that, in employment, "disability" does not include an individual who is currently engaging in the illegal use of drugs, where possession or distribution of such drugs is unlawful under the federal controlled substance act, when the covered entity acts on the basis of such use. That rule is narrow and specific. It is one more reason to have counsel review any line about drugs, medication, or testing before it goes into an ad.
If an applicant later says they need an accommodation to do a task, route that request to the process your organization uses rather than deciding it during screening. The ad's job is to describe the work clearly. It is not the place to settle questions about individual needs.
Step 6: Check state rules before you post
Federal law sets a floor. States can add protections or limits, and some are specific about what employers may require. A clear example comes from New Hampshire. Its statute says that "No employer shall require as a condition of employment that any employee or applicant for employment abstain from using tobacco products outside the course of employment, as long as the employee complies with any workplace policy" and then points to other sections of state law. Read that carefully. An ad that says "must be tobacco-free" as a condition of employment could run into this rule, even when the employer's goal is a healthier workplace. The statute still allows workplace policies that apply on the job, so the line between conduct at work and conduct outside work is the point to check.
This is why one ad wording rarely works everywhere. Check the law where the job is located. If you hire remote workers, check the rules where the person will actually work, and ask counsel which states your ad can reach. Keep a short list of the state rules that matter most for your hiring, and update it when a law changes what you can require.
A practical habit helps here. Maintain a shared library of approved requirement phrases that HR or counsel has reviewed. When a manager wants a new line, they start from the library, and any new wording goes through review before it is used. That reduces the chance that a line copied from another state's form or an old posting ends up in a live ad.
Putting the six steps together
The goal is an ad that says exactly what the job needs and nothing more. Applicants benefit because they can judge their own fit, and the team benefits because the people who apply are more likely to match the work. A requirement with a clear reason is easier to defend, easier to explain to an applicant, and easier to keep fair over time.
Next step today
Pick one job ad you plan to post and check each requirement line against its duty. Remove, or mark as preferred, any line with no matching task.
Frequently asked questions
Where should I start?
Start with the duties of the job, then test each requirement against them, as Step 1 explains.
Can someone else's preference justify a requirement?
No. Step 4 explains why the preferences of coworkers, customers, or clients do not make a line a job requirement.