Almost every startup and scale-up hiring developers manages its applications in an ATS, an applicant tracking system. Plenty of myths circulate around these tools: a robot that automatically rejects most resumes, keywords hidden in white text that push a profile up, compatibility scores that decide in the recruiter’s place. The reality is more mundane, and more useful to know. This article explains what an ATS actually does with a developer resume, the layouts that cause problems, how to write technology names, and how to check your resume before sending it.
What an ATS really does with a resume
An ATS is first and foremost an organisational tool. When you apply through a scale-up’s careers site, on a job board or via a form, your application lands in a database where the recruiter finds it, sorts it by stage (new, shortlisted, interview, offer) and shares it with managers.
To make this database usable, most ATS perform three operations on your resume.
- Text extraction: the software reads the PDF or document and pulls out the raw text.
- Parsing into fields: it tries to recognise your name, your contact details, your jobs with their dates and titles, your degrees and your skills, to fill in a candidate record.
- Indexing: the text becomes searchable. The recruiter can then search for "TypeScript" or "Kubernetes" across all the applications received.
What an ATS rarely does on its own is reject a resume. Automatic eliminations most often rely on screening questions asked in the form: right to work, location, availability, salary expectations, years of experience. An answer that does not match the criterion set by the company can rule the application out before anyone reads it. So answer these questions carefully, and honestly.
Some ATS also offer sorting or profile suggestion features. They help the recruiter prioritise, but the decision remains human in the vast majority of processes. In Europe, the GDPR also regulates decisions based solely on automated processing (article 22 🔗), and the French data protection authority CNIL publishes recommendations on recruitment 🔗 and candidates’ rights.
The real risk, then, is not a robot judging you. It is a failed extraction that makes part of your resume disappear from the candidate record, or a keyword search that does not find you because you wrote the technology differently.
Layouts that break extraction
A resume can look beautiful on screen and be unreadable for software. The most common causes:
- multiple columns: the extractor often reads line by line, from left to right, and mixes the skills column with the experience column;
- text inside images: a banner of technology logos, a name written in an image, a graphic skills bar. None of it is read;
- text boxes and complex tables produced by some layout software, which are extracted out of order or not at all;
- icons instead of words: an envelope for the email, a logo for GitHub, without the matching text;
- headers and footers: some extractors ignore them, and your contact details vanish;
- decorative or poorly embedded fonts in the PDF, which produce unreadable characters;
- PDFs exported as images, for example after a screenshot or going through a scanner.
The resulting rule is simple: one column, standard section titles (Experience, Education, Skills), real text for everything that matters, dates in a consistent format. These are also the rules that make human reading easier.
Technology names: variants, acronyms and versions
This is the point most specific to developer resumes. A technology can be written in several ways, and the recruiter’s search does not know them all.
A few reflexes:
- write the official name, with its usual capitalisation: PostgreSQL, JavaScript, TypeScript, Node.js, Kubernetes, GitHub Actions;
- add the acronym or the long form when both are in use: "Amazon Web Services (AWS)", "continuous integration and delivery (CI/CD)", "Google Cloud (GCP)". Once is enough, in the skills section or at the first mention;
- avoid personal abbreviations: "Postgre", "JS/TS", "k8s" are understood by a lead, not necessarily by a recruiter’s search;
- specify a version only if it matters: "Java 17" or "Angular 2+" distinguishes a modern profile from maintenance of an old version; for most technologies, the name is enough;
- reuse the ad’s spelling when it differs from yours: if the ad writes "React.js", mention React.js at least once.
The backend developer resume template illustrates these choices: official names, common acronyms, technologies grouped by use in two lines that a human and a piece of software can both read. Our article on presenting your tech stack details this organisation.
Using an ad’s keywords without copy-pasting
Tailoring your resume to an ad does not mean pasting in the list of required technologies. A recruiter who reads a skills section identical to the ad notices immediately, and a tech lead will check every word.
A four-step method:
- Note from the ad the technologies, practices and exact job title. Separate the essential (cited in the duties or requirements) from the desirable ("a plus").
- Look in your background for a real experience for each essential item. If you find one, name the technology in the matching bullet, using the ad’s exact word.
- Adjust the summary to reuse the job title and the two or three main technologies. Our article on the first developer job shows how this summary also helps in direct messages to teams.
- Leave out what you have never practised. If it is central to the ad, say so honestly in the summary ("currently ramping up on Go").
Keywords are not just for software. They let the recruiter, who is often non-technical, quickly tick off the criteria the manager gave them.
Testing your resume before sending it
A few simple checks avoid most unpleasant surprises.
- The copy-paste test: open your PDF, select all the text and paste it into a plain text editor. If the order is preserved and your dates, titles and skills appear legibly, an ATS will read them too. If the text is jumbled or missing, the layout is the problem.
- Searching the PDF: search for the main technologies in the ad with your PDF reader’s search function. If a search fails while the word is visible, it is probably inside an image.
- The application form: when a careers site offers to pre-fill the form from your resume, look at the result. Badly filled fields show what the ATS understood of your document.
- Links: check that the URL of your GitHub or portfolio is written out in full, not just hidden behind an icon. Our article on the GitHub link details this point.
- The file name: "firstname-lastname-backend-developer-resume.pdf" is more professional than "cv_final_v3.pdf", and is easier to find in an inbox.
If your current resume fails the copy-paste test, it is often quicker to rebuild it in a tool designed for this problem than to fix a graphic template. The TechCV editor produces a one-column page, with real text and standard sections, whose extraction by ATS stays faithful to what you wrote. You can import your resume and check it straight away.
Frequently asked questions
Do ATS automatically reject most resumes?
No, not in the sense often meant. Automatic rejections mostly go through the form’s knockout questions. The rest of the screening is done by recruiters, who rely on the records and searches in the ATS. A failed extraction, however, can make you invisible in those searches.
Should I add keywords hidden in white text on my resume?
No. Hidden text shows up in candidate records and in copy-pastes; a recruiter who discovers it rejects the application. It is also pointless: a keyword placed in a real experience carries far more weight.
Is a PDF resume always better than a Word file?
A PDF exported from a word processor or a resume editor, with real text, is read without difficulty by common ATS and preserves the layout. Provide a Word file only if the ad explicitly asks for one.
Do job boards use an ATS too?
A platform such as Welcome to the Jungle or LinkedIn often forwards your application to the company’s ATS, or offers its own tracking tool. Either way, your resume is extracted and indexed: the same layout rules apply.