What is an applicant tracking system?

What is an applicant tracking system?

An applicant tracking system is software that holds a company’s open roles, the people who applied to them, what stage each person has reached, and the evidence gathered along the way. It exists to provide continuity: hiring runs over weeks and across several people, and the expensive failures are almost always lost context rather than bad judgement.

At minimum an ATS holds requisitions, candidates, stages and communication history. Beyond that, systems differ widely — some are close to a shared spreadsheet with permissions, others carry sourcing, assessment, interviewing and analytics.

Does an ATS automatically reject CVs?

Usually not, and the widespread belief that "robots reject your CV before a human sees it" is mostly wrong. Most systems rank or filter to order a recruiter’s queue, and a human still opens the list. Some can be configured to auto-reject on knockout questions — but that is a setting an employer chose, not something the software does inherently.

The candidate-facing advice industry built around "beating the ATS" is largely selling a solution to a misunderstood problem. What actually happens is more mundane and more fixable: a recruiter with 400 applications reads the top of a ranked list and runs out of time. Being ranked low is the harm, not being auto-deleted.

That said, auto-rejection is real where employers enable it, which is why it is worth asking a vendor directly whether it is possible. OpusHire is built so it is not: screening minimums raise advisory flags for human review, there is no setting that turns it into an automatic filter, and no timer moves an untouched candidate into a rejected state.

What should a CV look like for an ATS?

Plain structure, real words, no tables or text boxes for essential information, and a file the system can read — a normal PDF or Word document. There is no keyword trick worth knowing. Modern systems parse into a structured profile, so describing what you actually did in ordinary language works better than stuffing terms.

• Use a standard layout. Multi-column designs and information inside graphics parse unreliably.
• Name things the way the industry does. Not to game a filter, but because a parser and a recruiter both need to recognise the role.
• Include dates and durations. Tenure is one of the few facts almost every system extracts.
• Skip the keyword block. A wall of skills with no context scores poorly and reads worse.

Does your organisation need one?

If you hire more than a handful of people a year, or more than one person is involved in hiring, you already have an applicant tracking system — it is just made of inboxes and spreadsheets. The question is not whether to have one but whether the one you have loses candidates, and that usually becomes obvious the first time nobody can say who was following up with someone.

Below roughly a dozen hires a year with a single person running the process, dedicated software is often overhead. Above that, the failure modes compound: duplicate outreach to the same candidate, decisions nobody can reconstruct, and no way to see where in the process people are being lost.

Frequently asked questions