How to Write a Developer CV That Survives ATS and Still Reads Like a Human Wrote It

Crafting a developer CV that successfully passes through applicant tracking systems and also appeals to human recruiters requires a delicate balance. The most common approach in developer CV advice often prioritizes either maximizing the ATS optimization or creating content that a human would enjoy reading. However, both are necessary because each reader exists—first, an automated bot scans your file, followed by a human who determines whether to proceed with an interview.

The ATS primarily breaks down your document into standardized sections—professional experience, education, and skills—and matches keywords against the job description. As a result, it's best to stick with conventional section headers like "Professional Experience," "Education," and "Skills." Using creative titles such as "My Journey" or "What I Bring" can disrupt the parser's assumptions.

It is also advisable to avoid complex layouts, such as tables, text boxes, or multi-column designs that may contain content the ATS needs to extract. Most parsers read left-to-right and top-to-bottom, and multi-column layouts can scramble your work history, making it incomprehensible to the system.

To ensure the bot identifies your qualifications, match the language used in the job posting. If the posting specifies "Node.js," avoid substituting "backend JavaScript" as you risk not aligning with the keyword filter, even if your skills clearly qualify. Save your CV as a .docx or a text-based PDF. Avoid image-based files or heavily designed PDFs since you may not be able to select and copy the text, which the parser is incapable of doing either.

Once past the automated filter, the CV should serve a different purpose: convincing a human recruiter that you are worth their time. At this stage, focus on quantifying your impact. Phrases like "reduced page load time by 40%" are more compelling than simply stating "improved performance." If you lack specific numbers, describe the situation before and after your contribution in concrete terms.

Begin each bullet point with an action or change you implemented, such as "Migrated the checkout flow to a queued job to eliminate timeout errors." This approach tells a richer story compared to merely stating your responsibility.

Eliminate any bullet points that lack verifiability or specificity. Soft skill bullet points like "great communicator" or "team player" provide minimal value on their own. Instead, illustrate your soft skills through the accomplishments you achieved with others. Keep the length of your CV proportional to your experience. For those early in their careers, aim for a single-page document.

As you progress in your career, two pages is acceptable, provided it is tightly edited and avoids a full chronological diary. A common mistake is to over-optimise the CV for the ATS at the expense of readability for human reviewers. Avoid cramming every possible keyword, as this can come across as noisy to a human reader. The solution lies in accurately portraying your experience using the terminology used in the industry and the specific job posting.

Before submitting your CV for each application, read the job posting thoroughly and underline the specific technologies and responsibilities mentioned. Then, compare your CV against this list rather than trying to fabricate experience you don’t possess to match the keywords. By ensuring your real experience is articulated using the language of the industry, you significantly increase your chances of passing through the ATS and capturing the attention of human recruiters.