Free tool
In buildFix the brief before it costs you the shortlist
Paste a job description and see where it is vague, over-specified, quietly exclusionary, or missing the detail a candidate needs to decide whether to apply.
The Surhires job description analyzer will read a pasted description and report on five things: structural clarity, requirement inflation, exclusionary language, missing information a candidate needs to self-select, and whether must-haves are actually distinguishable from preferences. It returns observations for a human to act on, not a score to optimise against.
By Surhires Editorial · Published · Reviewed
In the product: in build for Wave 1 as a free public tool
The five things the analyzer will look at
Structure first. Whether the description says what the person will do, distinct from what the company does, whether responsibilities are concrete actions rather than abstractions, and whether the reader can tell within thirty seconds what this job actually is. Most descriptions bury the job under three paragraphs about the company.
Then the requirements: how many there are, how many are marked essential, whether years-of-experience figures are attached to specific skills or applied globally, and whether the list contains items that cannot all plausibly be held by one person. Then language, for phrasing that narrows the applicant pool without adding signal. Then completeness, for the detail a candidate needs to decide.
Finally the honesty check: whether the must-have list is genuinely a must-have list. That one takes its own section, because it is where most descriptions do the real damage.
A long must-have list changes who applies, not who is qualified
Adding requirements to a job description does not raise the quality of applicants. It changes the composition of the applicant pool, and it changes it in a direction most hiring managers do not intend. Candidates who read a fifteen-item essential list and hold twelve of the items behave differently depending on how confident they are, and confidence is not evenly distributed across the people you want to hear from. The applicants you lose are disproportionately the ones who assess themselves honestly, which is not the trait you were trying to filter for.
The list also has a second effect that is easier to measure. A long essential list makes the description slower to read, less specific overall because attention is spread thin, and harder for your own screening to use, since a screener weighting fifteen essentials weights none of them. Ten pass-marks and five failures looks the same as five and ten if everything is essential.
The analyzer counts the essential requirements and flags the list when it grows past the point where the word essential still means anything. It does not tell you which to cut, because that is a hiring decision. It tells you that the decision is being avoided.
- Counts stated essential requirements separately from desirable ones
- Flags years-of-experience figures applied globally rather than to a named skill
- Notes requirements that cannot plausibly coexist in one background
- Highlights degree requirements attached to roles where the description shows no need for one
- Marks certification and tool requirements that could reasonably be learned on the job
- Reports the ratio of essentials to desirables, which is usually the honest summary
How to separate a must-have from a preference honestly
The test that works is a hiring test, not a writing test. For each item on the essential list, ask whether you would reject an otherwise excellent candidate solely for lacking it. If the answer is no, or if it is yes but you know you would not actually do it, the item is a preference. Write it as one.
The second test is about the first ninety days. A must-have is something the person needs on day one because there is no time or route to acquire it: a licence they cannot practise without, a language the team works in, a legal right to work in the location. Almost everything else, including most tools and most frameworks, is something a capable person picks up, and calling it essential is a shortcut that costs you candidates.
Doing this properly usually cuts an essential list roughly in half and moves the rest into a preferences section that hiring managers still get to weigh. Nothing is lost. The description gets shorter, the screening gets sharper, and the people who would have self-rejected apply.
Exclusionary language is mostly accidental and still narrows the pool
Very little of this is deliberate. It is inherited phrasing, copied from a previous description, that carries a signal nobody intended. Terms that read as an age preference, recent graduate, digital native, or the reverse. Physical requirements attached to a role that does not need them. Culture language that describes a demographic rather than a way of working. Sports and military metaphors used as a proxy for drive. Requirements for continuous employment that penalise anybody who took a caring break.
The analyzer flags the phrase and says why it might narrow the pool, and then stops. It does not rewrite the description for you and it does not tell you the phrasing is unlawful, because whether a given phrase creates a legal problem depends on your jurisdiction, the role and the facts, and that is a question for your counsel rather than a text tool. It is an observation, and observations are what a human can act on.
What a candidate needs in order to self-select out
The most useful thing a job description can do is stop the wrong people applying, and the way it does that is by including the facts that people actually decide on. A salary range or band. The location and the genuine working pattern, including how many days on site and whether that is negotiable. The interview process, how many stages and roughly how long. Who the role reports to. Whether the role is new or a replacement. Contract type and duration for anything not permanent.
Descriptions that leave these out do not get more applicants of the kind they want. They get more applicants of every kind, plus a set of conversations that end at the first screen because the salary was never going to work. Every missing fact is a screening call somebody has to run to establish something that could have been one line in the ad.
The analyzer lists what is missing from that set. It is usually the fastest improvement available on any given description.
What happens to the description you paste in
The analyzer will process the text you paste to produce the feedback and will not retain it. Nothing is written to a Surhires account, no account is needed, and the text is not used to train a model or to build a data set of job descriptions.
A job description is normally your own content. Two things change that. If you are an agency working from a client's draft, the text may be commercially sensitive and covered by your terms with them, and pasting it into a free web tool is a decision to make deliberately rather than by habit. If the draft contains a hiring manager's name and contact details or internal band information, that is other people's data and internal information travelling with it. Strip both before pasting; the feedback is unaffected.
What the analyzer will not do
It will not score the description out of a hundred. A score invites optimisation against the scorer, and a description tuned to please a text tool is not a better description. The output is a list of observations with the reasoning attached, which you can disagree with individually.
It will not rewrite the description. It will not tell you whether a phrase is lawful in your jurisdiction. It will not predict how many applicants you will receive, because that depends on the market, the salary, the employer and the channel far more than on the wording. And it will not check the salary disclosure requirements that apply where you are publishing; that is a different tool on this site, and the two are worth running together.
What you get
Structural read
Checks whether the actual job is findable in the first thirty seconds of reading.
Essential requirement count
Counts stated must-haves and flags the point where the word stops meaning anything.
Global years flagging
Marks experience figures applied to the role overall rather than to a named skill.
Implausible combinations
Notes requirement sets that no single realistic background would satisfy.
Degree necessity check
Flags a degree requirement where nothing in the description depends on one.
Exclusionary phrasing
Highlights inherited language that narrows the pool without adding any signal.
Missing salary range
Reports the absence of a band, which is the single most common omission.
Working pattern clarity
Checks that days on site and negotiability are stated rather than implied.
Process transparency
Flags a missing interview process outline, stage count and rough duration.
Reporting line
Notes when the description never says who the person reports to.
Observations, not a score
Reasoned findings you can disagree with individually, with no number to game.
No retention
Pasted text is processed to produce the feedback and is not kept afterwards.
Questions recruiters ask
Does a long requirements list get me better applicants?
No. It changes who applies rather than who is qualified. Candidates holding most of a long essential list self-select out at different rates depending on confidence, and confidence is not evenly distributed. You lose the people who assess themselves honestly. A long list also blunts your own screening, because weighting fifteen essentials weights none of them.
How do I decide what is genuinely a must-have?
Two tests. Would you reject an otherwise excellent candidate solely for lacking it? If not, it is a preference. And is it needed on day one with no route to acquire it, like a licence, a working language or a right to work? Most tools and frameworks fail both tests. Doing this honestly usually halves the list.
Will it tell me if my wording is unlawful?
No. It flags language that may narrow your applicant pool and explains why, then stops. Whether a phrase creates a legal problem depends on your jurisdiction, the role and the facts, and that is a question for your counsel. A text tool that issued legal verdicts on pasted copy would be giving you false confidence.
Why is there no overall score?
Because a score invites optimisation against the scorer, and a description tuned to please a text tool is not a better description. The output is a set of observations with reasoning attached so you can accept some and reject others. That is how a human editor works, and it produces better descriptions than chasing a number.
What single change improves most descriptions?
Adding the facts candidates decide on: a salary band, the real working pattern including days on site, the interview process and stage count, and who the role reports to. Descriptions missing these do not attract fewer wrong applicants; they attract more of everything, plus screening calls that end on a salary that was never going to work.
Do you keep the description I paste in?
No. The text is processed to produce the feedback and is not retained, nothing is written to an account, and it is not used to train a model. If you are an agency working from a client's draft, treat that text as commercially sensitive and strip hiring manager details and internal bands before pasting. That call is yours.
Can I use it yet?
No. It is in build for the Wave 1 release as a free public tool and no launch date has been published. This page sets out what it will report on. If you want the description improved rather than assessed, the job description generator inside the product drafts from a structured requisition rather than from a blank page.
Keep reading
- Job descriptions built from the requisition you already filled in
- Flag a posting before it goes out without a range
- Collect equal-opportunity data without letting it touch the decision
- See which of ten resumes actually fits the brief
- Job posting with the board states written down
- Give every interviewer the same brief
See it against your own reqs
Bring one live role and three resumes. In twenty minutes you will see the match scores, the shortlist and the placement invoice that comes out the other end.