Resume length check

Recruiters spend seconds on a first scan, and common guidance is blunt — one page for anyone under ten years of experience, two at most beyond that. Send a word count and a years-of-experience figure and you get back a clear verdict — too_short, appropriate or too_long — together with the recommended page and word limits, an estimated page count and a plain-language explanation. It is the same deterministic rule set recruiters quote, exposed as a single call you can drop into a job board, a CV builder or an applicant tracking system.

Why resume length still matters

Hiring research keeps repeating the same finding: recruiters give a resume a handful of seconds before deciding whether to read on. Length is the first filter they apply, often unconsciously. A two-page document from a candidate three years out of college signals poor judgement about what matters; a half-empty page from a senior engineer signals thin experience. The widely quoted rule of thumb is simple: one page if you have under ten years of professional experience, two pages maximum once you pass that mark, and never pad a resume just to fill space. Because a page of typical resume formatting holds roughly five hundred words, the rule translates cleanly into word counts — about five hundred and fifty words for junior and mid-level candidates, eleven hundred for senior ones, and a floor of around two hundred words below which any resume looks sparse. This resume length check encodes exactly that translation so you can apply it automatically, at scale, before a human ever sees the document.

How the verdict is computed

The check takes two numbers: the total word count of the resume and the candidate's years of professional experience. Years of experience must be zero or positive — a negative value is rejected as invalid input, since it can only come from a data-entry or parsing bug upstream. From there the logic is a deterministic lookup. Under ten years of experience the ceiling is one page, expressed as five hundred and fifty words to allow for denser formatting; at ten years or more the ceiling rises to two pages, or eleven hundred words. Independent of seniority, anything under two hundred words is flagged as too short. The response reports the verdict, the recommended minimum and maximum word counts, the recommended maximum pages, and the estimated page count of the submitted resume computed at five hundred words per page and rounded to two decimals. A human-readable advice string explains the verdict and, when the resume is too long, states exactly how many words to trim. Nothing is random and nothing calls a model: the same input always produces the same output.

Where to use it in a hiring pipeline

The most common integration is a CV builder or job board that wants to coach candidates before submission: run the check on save, show the verdict inline, and link to trimming guidance when the document runs long. Applicant tracking systems use it as a lightweight quality gate, tagging over-length resumes for review instead of rejecting them outright. Outplacement and career-coaching platforms batch it across their client base to prioritise who needs editing help first. Because the check is deterministic and stateless, it is safe to call on every keystroke-driven save and cheap enough to run across an entire talent pool nightly. The same code that answers the paid API runs free in the browser widget on this page, so candidates can test their own resumes without an account and you only pay when you automate the call. At $0.002 per request, screening ten thousand resumes costs about as much as a coffee — and the output is stable enough to store in an audit trail next to each application.