Your tech CV has two audiences, and they read in opposite ways. First, an applicant tracking system parses it, searches it for keywords, and ranks it against the job description. Then, if it survives that filter, a human recruiter skims it in seconds. A CV that pleases only one audience fails. The fix is not a trick or a template hack. It is a clean, single column document that states the right skills in the right places, with proof attached to every claim.
The scale of the first audience is hard to overstate. In 2026, Jobscan detected an applicant tracking system at 97.4 percent of Fortune 500 companies, 487 out of 500, by reviewing each company's career pages. Workday alone was used by over 40 percent of those companies for talent acquisition, and 76.4 percent of recruiters surveyed said they search and rank candidates by skills taken from the job description. If you apply to large employers, assume your CV meets software first.
Key Takeaways
ATS software is near universal at large employers: 97.4 percent of Fortune 500 companies used one in 2026, according to Jobscan.
Recruiters skim a CV for an average of 7.4 seconds on first screen, so clear sections and bold headings matter as much as keywords.
Use a single column, text based format with standard headings, and never hide key details in headers, footers, tables, or columns.
Mirror the job description's exact skill keywords, then prove each one inside a work or project bullet, not just in a skills list.
88 percent of employers in a Harvard Business School and Accenture study said qualified, high skilled candidates were rejected for not matching the hiring criteria exactly, so tailoring is not optional.
The two gates your CV must clear
Think of hiring as two gates in sequence. Gate one is parsing and ranking. The system extracts your text, looks for the skills and titles in the posting, and scores the match. Gate two is the human skim. A recruiter, facing a stack of surviving CVs, decides in seconds whether yours deserves a closer read.
The human gate is brutally fast. An eye tracking study by Ladders Inc., reported by HR Dive, found recruiters skimmed a resume for an average of 7.4 seconds on initial screen in 2018, up from 6 seconds in 2012. The resumes that held attention had simple layouts with clear sections and heading titles, bold titles, and bulleted accomplishments. Cluttered layouts, multiple columns, long sentences, and missing section or job headers did worst.
That finding shapes everything below. Every formatting choice should help both a parser and a fast human eye. If a design choice helps one and hurts the other, drop it.
Format first: build for the parser
The safest format is boring on purpose. Jobscan recommends a clean single column layout, no multi column layouts, tables, or text boxes, and no critical information such as your name, email, or phone number in the document header or footer, because parsers can miss or misread those areas. Use web safe fonts such as Arial, Calibri, Georgia, or Times New Roman, 10 to 12 points for body text and 14 to 16 points for headings, and submit a .docx file or a text based PDF unless the posting specifies otherwise.
Career guidance from UC Berkeley School of Information gives the same rules in short form: do not use tables or columns, do not use headers or footers, and use standard section headings such as Professional Experience. A developer focused guide on DEV Community agrees: a single column, text based resume in PDF or DOCX, with standard headings (Summary, Experience, Projects, Skills, Education) and consistent dates.
Aspect | Do this | Avoid this |
|---|---|---|
Layout | Single column, generous margins | Two columns, tables, text boxes |
Headings | Standard names: Summary, Experience, Projects, Skills, Education | Creative headings a parser cannot recognize |
Contact details | In the body text at the top | In a header or footer |
Fonts | Arial, Calibri, Georgia, or Times New Roman | Decorative or unusual fonts |
File type | Text based PDF or .docx, as the posting asks | Scanned images, graphics heavy PDFs |
Dates | One consistent format everywhere | Mixed formats, missing dates |
One warning worth repeating: do not stuff keywords in white text, and do not paste the whole job description into your CV. The DEV guide flags both as tricks that backfire, and a human reader who spots them will trust nothing else on the page.
Keywords: mirror the posting, then prove them
Since 76.4 percent of recruiters search and rank by skills from the job description, keyword matching is the core of gate one. But matching is not copying a list. It is a two step move: use the posting's exact wording, then show the skill in action.
Start by reading the posting closely and listing its must have skills, tools, and concepts. Use the same keywords as the job description, and use both the long form and the acronym version where both exist, for example "product manager" and "PM", or in developer terms "Kubernetes" and "K8s" only where the posting itself uses both. Berkeley's guidance makes exactly this point about long form plus acronym.
Then place each important keyword inside a bullet that proves it, not only in the skills section. A skills list alone is weak evidence, as the DEV guide notes. The same keyword inside a project or job bullet shows it has been used. Compare these two approaches:
Weak: Skills: React, PostgreSQL, Docker.
Strong: "Shipped a React dashboard backed by PostgreSQL, containerized with Docker, cutting report generation time from 20 minutes to under 2 minutes."
The second version matches the keyword, names a real outcome, and gives the human reader a reason to keep reading. Do that for your three to five most relevant skills per application, and keep the rest in a short skills section.
Tailoring matters because exact matching cuts both ways. A Harvard Business School and Accenture study, reported by HR Dive, found that 88 percent of employers surveyed said qualified, high skilled candidates were rejected because they did not exactly match the hiring criteria, and 94 percent said the same about middle skilled candidates. That does not mean you should claim skills you lack. It means you should describe the skills you do have in the posting's own vocabulary, so a legitimate match is not lost to wording.
Write for the 7.4 second skim
Once the parser passes you through, a human decides fast. Design the top third of your CV as if it is all anyone reads, because often it is.
Start with a two or three line summary that names your role, your strongest stack, and one measurable result. Follow it with your most relevant experience, not your full history. Use bold job titles, clear company and date lines, and bullets that start with a strong verb and end with a result where possible. Keep bullets to one or two lines. Long paragraphs are where skimmers give up, and the Ladders study confirms that cluttered, dense layouts performed worst.
Order matters too. Put the experience most relevant to this role first, even if it is a project rather than a job. For early career developers, a projects section with real, deployed work can carry more weight than a thin employment history. If you need proof of work to talk about in the first place, How Open Source Contributions Can Land You Your First Tech Job explains how to build it. And once the CV gets you the interview, How to Pass Technical Interviews: A Practical Guide for Developers covers what happens next.
A checklist before you hit submit
Run through this list for every application, not just once per CV version:
One column, text based. No tables, columns, text boxes, headers, or footers holding key details.
Standard headings. Summary, Experience, Projects, Skills, Education, in that order or close to it.
Keywords mirrored. The posting's exact skill terms appear in your CV, in both long form and acronym where relevant.
Proof in bullets. Each key skill appears inside at least one work or project bullet with a result.
Readable in seconds. Bold titles, short bullets, consistent dates, no dense paragraphs.
File as requested. Text based PDF or .docx, exactly what the posting asks for.
No tricks. No white text, no pasted job description, no skills you cannot defend in an interview.
If you tailor the keywords and the top bullets for each role, you have done the highest value work. A generic CV sent to fifty postings will lose to a tailored CV sent to ten, because the tailored one clears both gates: the parser finds its match, and the human finds a story worth reading.
Read this article in Indonesian: Baca artikel ini dalam Bahasa Indonesia.
FAQ
Do I really need to tailor my CV for every job?
Yes, at least the keywords and the top bullets. With 97.4 percent of Fortune 500 companies using ATS software and most recruiters ranking by skills from the posting, a generic CV risks missing the exact match that gets you through gate one.
Should I use a fancy designed CV template?
No, not for online applications. Multi column layouts, tables, text boxes, and graphics can confuse parsers and clutter the human skim. Save designed versions for portfolios or in person handouts, and send the clean single column version through application systems.
Is a PDF or a Word document better?
Either works if it is text based, but follow the posting. Jobscan recommends .docx or a text based PDF unless the posting specifies otherwise. Never send a scanned image or a graphics heavy file through an ATS.
How long should a tech CV be?
One page for early career developers, two pages at most for experienced developers with substantial results to show. If it runs longer, cut older or less relevant bullets first, and keep the strongest, most recent proof.
What if I lack a keyword the posting asks for?
Do not claim it. Instead, highlight the closest genuine skill, name adjacent tools you have used, and show learning in progress through a project. A keyword you cannot defend in an interview hurts more than a missing keyword.
Does ATS software reject most resumes automatically?
That popular claim is often repeated without a source behind it, and one of the sources consulted for this article explicitly warns that no study behind the famous percentage has ever been produced. What is verified is narrower and still important: ATS use is near universal at large employers, and exact keyword matching does cause qualified candidates to be filtered out. Focus on matching honestly and clearly, not on beating a mythical rejection rate.