ATS for developers: what it is, which ones exist and how to get through

Almost every application you send lands in an ATS, not in a recruiter's inbox. There are so many scare stories around the word that people write their CV for a robot instead of a person. This hub explains what an ATS actually does and what to do about it so that you get found and read.

For how to write the CV itself, see the developer CV guide; for ready-made ATS-safe versions, the CV templates; for tools like Jobscan, part 4 of the tools series. Here we put the whole picture together and don't repeat the details from there.

What an ATS is

An ATS (applicant tracking system) is where a company runs its hiring: it posts jobs, collects applications, moves candidates through stages from "new" to "offer", stores interviewer notes and scores, and sends emails. For a recruiter it is the desk. For you it is the place where your CV lives while someone is using it.

What it does with your file:

Parses. It pulls your name, contacts, jobs, dates, skills and education out of the CV and builds a candidate profile.
Stores and indexes. The profile becomes searchable: a recruiter can search by keywords and filters, even among old applications.
Moves through the pipeline. Candidates go from stage to stage and the team sees who decided what.
Sometimes scores or ranks. It depends on the system and on what the company switched on.

Which ATS employers use

You don't choose the system, the company does. But it helps to recognise it: the application URL tells you where you landed (boards.greenhouse.io, jobs.lever.co, jobs.ashbyhq.com, myworkdayjobs.com).

System	Where you meet it
Greenhouse	Product and tech companies, startups and scale-ups, often in the US and Europe
Lever	A similar segment: product companies and startups
Ashby	Younger tech companies that like structured candidate scorecards
Workday	Large corporations, banks, big outsourcing and product companies. Forms are long and you often need to check autofilled data
SmartRecruiters	Mid-size and large companies, several countries
BambooHR	Small and mid-size companies where the ATS is part of an HR suite
Teamtailor	European companies, especially the Nordics, with a focus on the careers page
iCIMS	Large corporate segment, mostly US
Taleo (Oracle)	An older corporate system. Still seen in large companies; Oracle's plans for it (unverified)
Recruitee	European small and mid-size companies

The "where you meet it" column is a general impression from vendor documentation and reviews, not a measured market share.

In Ukraine

Djinni and DOU. Many companies don't ask you to "apply through an ATS" at all: they work with responses on Djinni and DOU and move candidates into their own system afterwards. Your Djinni profile is your CV. See the CV guide, Ukrainian market section.
PeopleForce. A Kyiv-based HR platform with a recruiting module, the first to integrate with Djinni. Ukrainian companies often use it, but we found no public market share data.
Recruitee, Teamtailor, Greenhouse. Used by Ukrainian product and outsourcing companies that hire in several countries.
Huntflow. A recruitment automation system (huntflow.ai). Ukrainian HR communities mention it, but we did not check how widely it is used in Ukraine (unverified).
Home-made spreadsheets and CRMs. At small companies the "ATS" is often Google Sheets, Notion or Trello. Then there is no parsing at all and a human reads the CV.

How an ATS really works: myths and facts

Myth: "75% of CVs are rejected by a robot before a human sees them"

This number has been repeated for years. We found no primary source with a methodology. By some accounts it comes from a marketing presentation rather than a study (unverified). Don't build a strategy on it.

Fact: most modern ATS do not auto-reject people for a "weak CV"

Greenhouse states on its own support pages that it does not use AI to rate candidates or auto-reject them. That is the vendor's position, not an independent check. A recruiter survey reported in the trade press (92% say their ATS does not auto-reject) we only found secondhand (unverified). So we keep a qualitative statement, not a number.

Fact: auto-rejection exists, but the company configures it, and it works through questions

These are knockout questions. In Greenhouse a recruiter can set a rule so that answering "No" to "Do you have the right to work in the EU?" auto-rejects the application. Such rules work only on yes/no and single or multiple choice questions. Other systems have similar settings. So it is not a CV score that rejects you, it is your answer to a specific form question.

Fact: keywords matter, but for search

A recruiter with hundreds of applications searches the database: React TypeScript Kyiv, Python Django Poland. If the job and the search say TypeScript and you only wrote TS, you may not be found. This is not a filter that "kills" your CV, it is plain search. But if nobody finds you, the result is the same.

Fact: ranking exists in places, but a human still decides

Some systems show a match score with the job or suggest a candidate order. Sources disagree: some say Workday, SmartRecruiters, Lever and Workable have it, others that Ashby doesn't. A survey cited by blogs says many recruiters turn these scores off or ignore them (unverified). Practical conclusion: a score is a hint, not a verdict, but a strong match with the job near the top of your CV helps both the human and the algorithm.

The real problem: not rejection but the pile

Popular jobs get hundreds of applications. Companies on DOU write that some jobs get over 200 to 300 responses, and on Djinni some replies are automatic when experience is clearly irrelevant. So the loser is the person who wasn't found or noticed within seconds, not the one a "robot rejected".

How to get through an ATS

File format

Details and templates are in the CV guide; below is what concerns parsing specifically.

One column. Two columns, tables, text boxes and headers or footers turn into a mess, especially in Workday and older systems.
Standard headings: Summary, Experience, Skills, Education, Projects, Languages. Not "My Story" or "Professional Journey". Some systems match headings against a dictionary.
No tables, icons, skill bars or graphics for key information. Contacts, jobs, dates and stack must be plain text.
PDF or DOCX. Greenhouse accepts both (doc, docx, pdf, rtf, txt according to its help pages, check the current list). Our advice: if the job asks for a specific format, give that. If not, a text PDF (you can select the text) for most systems, DOCX for corporate ones like Workday or Taleo where dates are parsed strictly (sources disagree (unverified)). Scans and image exports can't be read anywhere.
File size. Stay under 2.5 MB. Third-party guides attribute that figure to Greenhouse, but we did not open the primary source (unverified). A light file does no harm anyway.
File name: Firstname-Lastname-Frontend-CV.pdf. No final_v3.
One minute check: open the PDF, select all, paste into a plain text editor. Same order and completeness as in the document? Then the parser will cope too.

Keywords from the vacancy

Pick out the required technologies, role and domain from the job.
Check that every technology you really used appears in your CV word for word as in the job: TypeScript, Next.js, PostgreSQL, not only TS, NextJS, Postgres. Writing both is fine: TypeScript (TS).
Place them not only in Skills but also in experience bullets where it is clear how you used them. A bare list looks like an attempt to fool a filter, and a human will notice.
Don't list what you can't do. It will end in a question at the interview.

Titles and dates

Your job title should match a real title the market understands: Frontend Developer, Software Engineer. If the company called you something exotic (Wizard of UI), add the standard title in brackets.
The headline under your name: role and level, as in the job.
Dates in one format: Jan 2023 to Present. Parsers and recruiters count experience from dates, unexplained gaps raise questions, and mixed formats break the calculation.
Freelance, contracts and sole proprietor (FOP) work go in as a separate job with real dates.

Location, visa, salary

These are the fields where an ATS really does filter, because they are easy to formalise.

Location and time zone: Kyiv, Ukraine (UTC+2). For remote jobs add the overlap with the team.
Work authorisation, visa, relocation. If the form asks "Do you need visa sponsorship?" or "Do you have the right to work in the EU?", answer honestly. A "No" on a knockout question rejects the application. So first find out whether the company works with Ukrainian contractors through a FOP, then answer precisely. Read the context of questions that default to "yes".
Salary. If the field is required, put a realistic figure with currency and net or gross. Too low looks unserious, too high may drop you at a filter. Benchmarks and net/gross details for Djinni and DOU are in the CV guide.

Knockout questions

Read every question before you submit, don't click through.
Answer truthfully, but don't treat every question as a verdict. If the job says "5+ years" and you have 4 strong ones, an honest answer plus a good note to the recruiter works better than staying silent. What counts as a hard requirement is the company's call.
If a "No" throws you out and you think you are a fit, write to the recruiter directly (LinkedIn, email) instead of reapplying with the "right" answer.
Don't change an answer just to "slip through". What you promised in the form gets checked on the first call.

A referral bypasses the ATS

A referral is the strongest move. A candidate from an employee reaches the recruiter separately, often with a tag, and is reviewed first. Formally you still pass through the ATS, but you are not "found among hundreds", you are looked for. How to ask for a referral and how to write to someone you barely know is in part 5 on LinkedIn and in the LinkedIn guide. A message straight to the recruiter works much the same: submit the form and send a short LinkedIn message at the same time. For how to write that message and whether you need a letter, see the cover letters hub.

Checklist before you send

Before and after

Job: Middle Frontend Developer, React, TypeScript, Next.js, REST, Jest. Below, an experience fragment.

Before (problems: two-column template with icons, non-standard headings, abbreviations, bullets with no result):

code

After: