What is an applicant tracking system (ATS)?

Strip away the marketing and an ATS does four things. It publishes a job to the places candidates look. It collects applications into one place instead of several inboxes. It moves each applicant through stages — screened, submitted, interviewing, offered — so the status of a search is visible without asking. And it keeps the history, which matters when a client asks why a candidate was rejected eight weeks ago.

Modern systems add resume parsing, which reads an uploaded CV and fills in the candidate's skills, employers and dates automatically, and some form of matching that scores applicants against the role. The useful ones also handle scheduling, because interview coordination is where recruiter hours quietly disappear.

This is the part candidates worry about, and the worry is justified but often misdirected. An ATS does not usually reject people automatically. What it does is make applicants searchable and sortable — and when a posting attracts four hundred applications, a recruiter searches rather than reads.

That search runs on the words in your resume. If the requirement says ETL and your resume says "built reporting pipelines", you describe the same work in language the search will not find. The fix is not keyword stuffing, which is obvious and counterproductive. It is describing the experience you genuinely have in the vocabulary the market uses for it.

Scoring and ranking features go further, weighing skills, recency, location and sometimes work authorisation. Those scores order a recruiter's queue; they rarely decide outcomes on their own.

A corporate recruiting team hires for one employer. A staffing agency places people with many clients, often on contract, and gets paid per hour worked rather than per hire. That difference runs deeper than it first appears.

An agency has to track bill rate and pay rate per placement, not just a salary. It has to collect timesheets from contractors it does not employ directly, approve them with the client, and turn them into invoices. It carries compliance obligations — I-9, work authorisation, certifications — for people spread across multiple sites. And it runs a sales pipeline alongside the recruiting one, because the requirement has to be won before it can be filled.

A corporate ATS handles none of that. Agencies that start with one typically end up bolting on a timesheet tool, a spreadsheet of rates and an accounting package, then spend their margin reconciling the three.

Pricing is usually per recruiter per month, and ranges from around $50 for a basic system to several hundred for enterprise platforms. The sticker price is rarely the real number.

The costs that hurt are the ones around it: implementation and data migration, integrations with your job boards and accounting system, and the time your team spends in two systems because the first one did not cover enough. When comparing, the question worth asking is not what the licence costs but how many other subscriptions it removes.

Start from what breaks today rather than from feature lists. If candidates go cold because submissions are slow, look hard at sourcing, parsing and matching. If month-end is painful, look at whether approved hours reach invoicing without re-keying. If audits make you nervous, look at document tracking and expiry alerts.

Then test with your own data. Every system demos well on a prepared dataset; the useful question is what happens when you load fifty of your own requirements and a messy resume from a real candidate.