How to Write a Tech CV That Gets Past ATS and Recruiters

Most tech CVs are rejected before a human ever reads them — filtered out by an applicant tracking system (ATS) for missing the right keywords, or skimmed past by a recruiter in six seconds. Here is how to clear both hurdles.

Match the language of the job

ATS software ranks your CV on how well it matches the job description. That does not mean keyword-stuffing — it means using the same terms the role uses. If the job says "PostgreSQL", do not only write "SQL databases". Mirror the stack, the seniority, and the responsibilities. This is exactly what HuntCampaign automates when it generates a CV tailored to each specific role.

Lead with impact, not tasks

Recruiters skim. Every bullet should show a result, not a duty. Compare:

• Weak: "Responsible for maintaining data pipelines."
• Strong: "Rebuilt the ETL pipeline, cutting nightly load time from 6 hours to 40 minutes."

Numbers, deltas, and outcomes are what make a bullet stop the eye.

Keep the structure clean and machine-readable

ATS parsers choke on columns, tables, text boxes, and graphics. Use a simple single-column layout, standard section headings (Experience, Skills, Education), and a normal font. Save as PDF unless the application asks for Word.

Put a skills section near the top

A concise, honest skills list near the top helps both the ATS and the human find your core stack fast. List the tools you would be comfortable being interviewed on — not everything you have ever touched.

Tailor per role — every time

A generic CV is a weak CV. The single highest-return habit is tailoring your CV to each role, emphasising the experience that matches. It is tedious by hand, which is why most people skip it — and why doing it (or automating it) is such an edge. See our cover letter guide for the companion document.

Create a free account and generate a tailored CV for any role in one click.