Required vs preferred: how to read a requirements list

A requirements list is a hiring team's attempt to describe a person they have not met yet. It is written by several people, usually in a hurry, and it is often longer than the job needs. Learning to read it is a practical skill, not a mind-reading exercise.

Required means the shortlist filter

Required items are the ones a reviewer checks before deciding whether to read the rest of your application carefully. They are usually a small set: a credential, a licence, a specific tool, a minimum amount of experience with a particular kind of work, or the legal right to work in a place.

If a required item is genuinely missing from your background, the application is unlikely to progress and the reviewer will not consider that unfair. If you have it but it is not visible in your materials, that is a different problem — and it is the one most candidates actually have.

Preferred means the tiebreaker

Preferred items decide between people who already cleared the required list. Missing several of them is normal. Meeting all of them and none of the required items is not a strong application, even though it can feel like one.

The three states a requirement can be in

• Demonstrated — the reviewer can point at a sentence in your materials that shows it.
• Not demonstrated — nothing in your materials speaks to it.
• Unclear — the word appears, but with no context that shows you used it in the way the role needs.

'Unclear' is where good candidates lose roles they would have won. A skills row listing a tool proves familiarity with the word. One sentence in a role description — what you used it for, at what scale, and what changed — proves the skill.

Turning a list into an application

Before you write anything, copy the required list into a note. Next to each item, write the single best piece of evidence you have. If a line is empty, decide honestly whether to address the gap or to skip the role. If a line has evidence that is not currently visible in your résumé or profile, put it there.

On Rice & Bean, applications ask you to respond to each stated requirement directly, and reviewers see your response beside the requirement it answers. The exercise above is the preparation for that step, and it is worth doing even where an employer never asks for it.

When a list looks unreasonable

Long required lists are often the result of several people adding wishes to one document. If a posting requires twelve things for a mid-level role, read it as a signal about how well the role has been defined, factor that into question three of your decision, and ask about scope early.