RecruitingHR techAI screeningIndia

Job specification: the half of the post your screen reads

HireQwik November 13, 2026 10 min read

On 13 November I pulled the results page for “preferred qualifications” in India. Google’s AI Overview tells job seekers that meeting roughly 60 to 80 percent of the core criteria is enough to apply, and that preferred qualifications mostly “act as tie-breakers”. Most of the organic results are candidates asking the same thing on forums: does “preferred” really mean optional?

So the people reading your job post have been told, in effect, to ignore part of it. That’s fine if your job specification was written knowing they would. It’s a problem if half your “requirements” were really wishes, because your screen will treat them as requirements while your applicants treat them as suggestions. This post is about writing the specification so both sides read it the same way, and so a résumé screen can score it. This is the second of five posts on job-matched résumé scoring; the candidate scoring model post ties them together.

What is a job specification?

A job specification is the part of a job post that describes who can do the job: the skills, experience, qualifications and working conditions a person needs to succeed in the role. The job description says what the work is; the specification says what a candidate must bring to it, and it is the half every résumé gets checked against.

In the UK the same document is often called a person specification, and public-sector posts there split it into “essential” and “desirable” criteria. The labels differ. The job is the same: turn a role into a list a stranger’s résumé can be compared with.

Most companies don’t write the specification as a separate document. It lives as a bulleted “Requirements” section under the duties. That’s fine. What matters is that someone sits down and decides, line by line, what each bullet is for.

Why most specifications fail the screen

A typical requirements section for an inside sales role reads something like this:

  • Bachelor’s degree in any discipline
  • 2-4 years of experience in sales
  • Excellent communication skills
  • Self-motivated and target-oriented
  • Experience with CRM tools preferred
  • Knowledge of the SaaS industry is a plus

Read it as a screen would. “Excellent communication skills” can’t be found in a résumé; everyone claims it. “Self-motivated” is an adjective, not a qualification. “2-4 years of experience in sales” counts years without saying what kind of selling, so a retail floor job and an enterprise field role score the same. The degree line shuts out capable applicants. And nothing says which of the six lines would actually stop the hiring manager from making an offer.

That last gap costs more than it looks. When every line reads as required, the screen has two bad options: treat all six as hard filters and turn away applicants who’d be good at it, or treat none of them as filters and pass people who can’t work the shift. Either way, the shortlist stops reflecting what the hiring manager would actually say yes to.

Sort every line into one of four lists

Before rewriting anything, sort each requirement into exactly one of these:

  1. Minimum qualifications. Without this, you cannot hire the person, however good they are. A licence the law requires. The ability to work at the site. A shift pattern that is not negotiable. Keep this list to three items or fewer.
  2. Scored skills and experience. The things that make someone good at this specific job. These go into the score with weights.
  3. Preferred qualifications. Genuinely nice to have. They add a few points; they never decide.
  4. Not needed. Everything that was copied from the last post, the template, or habit. Delete it.

Expect the fourth list to be longer than you’d like. Degrees nobody would actually enforce, personality adjectives and tool names nobody uses any more tend to end up there.

Here is how the inside sales example sorts:

Original lineListWhy
Bachelor’s degree in any disciplineNot neededThe hiring manager admits they would hire a strong seller without one
2-4 years of experience in salesScored, rewrittenYears tell you little; the kind of selling tells you a lot
Excellent communication skillsScored, rewrittenReal, but needs evidence a résumé or a call can show
Self-motivated and target-orientedScored, rewrittenBecomes “has worked to a stated monthly target”
Experience with CRM tools preferredPreferredTrue nice-to-have
Knowledge of the SaaS industry is a plusPreferredHelps ramp-up, not required
Can work 10 AM-7 PM from the Bengaluru officeMinimumWas missing from the original, but it’s the real deal-breaker

The last row is the one that matters most and the one most specifications forget. The real deal-breaker is often a working condition nobody wrote down, which is why so many interviews end at “oh, it’s not remote?”

How to write minimum qualifications

A minimum qualification has to pass one test: if a candidate is excellent in every other way but lacks this, will you still say no? If the answer is “probably”, it’s not a minimum. Move it to the scored list.

Write each minimum as a plain sentence that has a yes-or-no answer:

  • “Can work from the Bengaluru office five days a week.”
  • “Holds a valid two-wheeler licence.” (For a field role where riding is the job.)
  • “Can join within 30 days.”

Avoid minimums that stand in for something else. “Graduate” is often a stand-in for “can write a clear email”. If that’s what you mean, score writing instead. The Burning Glass Institute’s February 2022 study, The Emerging Degree Reset, tracked employers dropping degree requirements from many middle-skill roles and some higher-skill ones, and projected that 1.4 million more US jobs could open to people without degrees over five years. The roles didn’t get easier. The specifications got more honest about what the work needed.

Minimums also need to be checkable at the screening stage. “Will fit our culture” can’t be. “Can work weekends during the festive season” can, with one question.

How to write preferred qualifications

Preferred qualifications are where specifications get lazy, because there’s no cost to adding one. There is a cost. Every preferred line is read by some candidates as required, and they don’t apply. The ones who do apply get no clear signal about what helps.

Three rules:

  • Keep it to three. If you have eight preferred qualifications, you don’t have priorities.
  • Make each one specific. “Experience with CRM tools” becomes “has logged calls and pipeline in a CRM (any brand)”.
  • Say what it’s worth. In the score, a preferred qualification should add a small, fixed number of points, never enough to lift a weak candidate over a strong one.

If you find a preferred item that the hiring manager keeps mentioning in every debrief, it isn’t preferred. Promote it to the scored list and give it a real weight.

Turn each line into a rule a screen can score

The scored list is the heart of the specification. Each line needs two things: a description of the work, and the evidence that would prove it. Here’s the inside sales rewrite:

Scored criterionEvidence that earns full points
Outbound or inside sales as the main jobA role where calls, demos or pipeline were the stated work
Worked to a stated targetA target, quota or conversion number named in the résumé
Clear written communicationSpecific, outcome-led bullet points rather than duty lists
Sold to businesses, not consumersNamed B2B customers, segments or deal types

Notice that “2-4 years” has gone. Experience still counts, but through what the candidate did, not how long they were employed. Someone who carried an inside sales quota for a year and a half should now outrank someone with four years at a retail counter, and with this specification they will.

This is where the specification and the scoring model meet. In HireQwik, each résumé gets scored against the requirements written for that job, and every score shows the résumé line it came from, so a vague specification produces vague scores and a sharp one produces scores a hiring manager can check. Your minimums go in as plain sentences too, for example “can work from the Bengaluru office”, and act as pass-or-fail checks kept apart from the score. We covered tagging must-haves and nice-to-haves inside the description itself in how to write a job description for better AI matching; the specification is the step before that, deciding what belongs on each list at all.

Job specification examples for three volume roles

The same four lists look very different across roles. Here are three common high-volume roles, sorted the same way. Treat them as starting points to argue with your hiring manager, not as finished specifications.

Customer support associate (voice and chat)

  • Minimum: can work rotating shifts including weekends; can work from the stated office.
  • Scored: spent most of a previous job talking to customers; worked to a stated metric such as tickets per day, handle time or CSAT; writes clearly, judging by the résumé itself; used any ticketing tool daily.
  • Preferred: experience in the same product category; a second Indian language the customer base uses.
  • Removed on purpose: “graduate in any discipline”, “pleasant personality”, “good typing speed” (it gets tested in a short task later, not guessed from a résumé).

Field sales executive

  • Minimum: holds a valid two-wheeler licence and can ride daily; can cover the stated territory.
  • Scored: has met a monthly sales or visit target and says so; sold to shops, distributors or small businesses rather than online; built or kept a beat or route of accounts; named the products or categories they sold.
  • Preferred: knows the local market of the territory; has used a sales app to log visits.
  • Removed on purpose: “MBA preferred”, “excellent negotiation skills” (scored through the target line instead), “own vehicle” (the licence and willingness to ride is the real need).

Warehouse or fulfilment supervisor

  • Minimum: can work the night shift; can join within 30 days.
  • Scored: has supervised a shift team and states its size; worked to throughput or accuracy numbers such as orders per hour or pick accuracy; handled inventory counts or inbound receiving; has used any warehouse system.
  • Preferred: e-commerce or quick-commerce fulfilment specifically; safety training.
  • Removed on purpose: “diploma or degree in logistics”, “5+ years experience” (replaced by the supervision and throughput lines, which show what the years were meant to stand for).

Notice the pattern in the “removed” lines. Each one was a proxy for something real, and each was replaced by the real thing written as evidence. That swap is the whole method.

A job specification template you can copy

Paste this under your duties section and fill it in with the hiring manager in one sitting:

Minimum qualifications (no more than three; each a yes-or-no sentence)

  1. …
  2. …

What we score (four to six; each the work plus the evidence)

  1. Work: … Evidence: …
  2. Work: … Evidence: …

Preferred (no more than three; each specific)

  1. …

Working conditions (location, shift, travel, joining window)

  • …

Removed on purpose (lines you deleted and why: keep this for the next time the role opens)

  • …

The last section is the one people skip. Keep it. The next time this role is advertised and someone suggests adding “MBA preferred” back, the reason it came out is written down.

What changes when the spec is right

When the specification is sorted this way, three things happen downstream. The minimums can be checked automatically and fairly, because they’re yes-or-no. The scored criteria produce a ranked list where the order means something. And the preferred items stop doing damage, because they can only nudge.

That ranked list is what lets the step from résumé to interview become short. Once the top band is clear, approving them takes a single bulk action, each candidate picks an interview time from an emailed link, and then sits an AI voice interview of 10-20 minutes whose questions come out of this specification and their own résumé. The next post in the series looks at how to screen applicants in before you screen them out, which is where minimums and scores meet a real applicant pile.

Pick one open role this week and run its requirements through the four lists. If the “not needed” list is shorter than three lines, look again. If you’d like to see your rewritten specification scored against real résumés, book a demo and bring the job post.

Frequently asked questions

What is the difference between a job description and a job specification?

A job description says what the job involves: duties, responsibilities, who the role reports to. A job specification says who can do it: the skills, experience, qualifications and working conditions a person needs. Most job posts combine both, but the specification is the half a résumé is checked against.

What should a job specification include?

A short list of minimum qualifications that are true deal-breakers, the scored skills and experience the role depends on, a separate list of preferred qualifications, and practical conditions such as location, shifts or travel. Each item should describe something a résumé or a short answer can show, not a personality adjective.

What is the difference between minimum and preferred qualifications?

Minimum qualifications are the conditions without which a candidate cannot be hired, such as a licence the law requires or the ability to work at a site. Preferred qualifications make a candidate stronger but are not required. In screening, minimums work as yes-or-no checks and preferred qualifications add points to a score.

See your own candidates screened

Book a 30-minute demo. Bring a live JD and we'll screen against it, then start with a pilot on your own candidates before committing to anything.