Every hiring funnel has one stage that is not measured: the gap between someone arriving on your careers page and starting an application. Nobody counts it, because no candidate record exists yet.
It is frequently the largest drop in the whole funnel. Twelve things cause most of it.
Finding and reaching the roles
1. Job pages are not individually indexable
If every role lives at the same URL behind a filter, search engines cannot index them, and candidates cannot share a link to one. Each role needs its own crawlable URL with JobPosting structured data.
2. Search and filtering are missing or broken
Above roughly twenty open roles, a flat list stops working. Location, department and contract type are the filters people actually use. Below twenty roles, filters add friction and a plain list is better.
3. The page is slow
Careers pages are often built on a heavier template than the rest of the site and then loaded with images. Every second of load time costs applicants, and the effect is worst on mobile connections — which is most of your traffic.
The application itself
4. It is not usable on a phone
A large share of candidates apply on a phone, and in high-volume categories it is the clear majority. Test the whole flow on an actual device: form fields, file upload, date pickers, and the submit button.
5. Account creation is required
Forcing registration before applying is the single largest source of abandonment on most careers sites. Let people apply, then offer an account afterwards if you need one.
6. The form re-asks what the CV already says
Parsing a CV and then requiring the candidate to retype their employment history is the most reliable way to lose the candidates with the most options. Parse it, show what you extracted, let them correct it.
7. Too many questions
Every additional field costs completions, and it costs them unevenly — the strongest candidates abandon first. Three to five questions, hard requirements first: how to choose them.
8. File upload is restrictive or fails silently
Accept common formats, accept large files, and if an upload fails, say so clearly. Silent upload failures produce applications with no CV attached, which then get rejected as incomplete.
What the page says
9. No salary information
Increasingly required by law and always useful. Roles without a range attract a mismatched pool and lose candidates who will not invest time in an unknown.
10. No description of the process
Three lines — the stages, the expected duration, and whether you respond to everyone — reduce anxiety and later withdrawal. See writing the posting.
11. Generic company content
"We are a dynamic, fast-growing company" appears on every careers page in existence. Specific, concrete content about the work, the team and how decisions get made is what candidates are actually trying to find.
12. No confirmation after submitting
An application that vanishes into silence is the first impression of your process. Immediate confirmation, with what happens next and by when — and then honour it.
Measuring the invisible stage
Four numbers make this drop-off visible:
- Careers page visits to application starts. The stage nobody measures.
- Application starts to submissions. The form abandonment rate. Above thirty per cent, the form is the problem.
- Mobile versus desktop completion. A large gap points straight at the mobile experience.
- Time to complete. Over ten minutes for a standard role is too long.
These require analytics on the careers page, not just ATS reporting, because the interesting part happens before a candidate record exists.
Where to start
In order of return: remove forced account creation, fix the mobile flow, cut the form to five fields, publish salary ranges, and add the process description. The first two typically move completion rate more than everything else combined.
For hosted careers pages that handle indexing, structured data and mobile application flow, see careers pages.