Yes, a developer resume can get past applicant tracking systems without looking like a plain form. The working recipe has three parts: a layout the parser reads from top to bottom, section names it recognises, and a file whose text can be selected and copied. The rest is content: the exact terms from the job post, measurable results, and technologies named the way the employer names them.
An ATS is not an automatic hiring manager scoring your personality. It extracts text from your file, splits it into sections, stores fields in a database, and lets a recruiter filter by keywords. Jobscan's 2025 survey of 384 recruiters reports that 99.7% use an ATS to filter candidates. A resume that parses badly can be excellent and still stay invisible.
This tutorial builds a developer resume as YAML with RenderCV, renders it to PDF, and checks the extracted text with pdftotext. You end up with a versionable source, a clean render, and proof that the sections are readable. Budget 35 minutes for the first version, then 10 to 15 minutes per application to adjust keywords. Prices and versions were checked in November 2026.
What the ATS actually does with your resume#
The parser works in four steps. It extracts text from the file, finds sections, identifies fields (name, company, title, dates, degree) and stores everything in a searchable database. The most common failure happens at step one: a scanned PDF, an export from a design tool, or a document full of frames can deliver no usable text.
Accepted formats vary by vendor, but a core set repeats. Bullhorn accepts PDF, DOC, DOCX, RTF, TXT and HTML; its parser updated in October 2026 also handles scanned documents. Oracle Taleo lists PDF, DOC, DOCX, ODT, RTF, TXT, HTML and WordPerfect. A text-based PDF and a DOCX remain the two safe choices. The scanned PDF and the image exported from a graphic tool are the two traps.
| Format | ATS readability | When to use it |
|---|---|---|
| Text-based PDF | Yes, if the text can be selected | Default submission, unless the job says otherwise |
| DOCX | Yes, broad compatibility | When the job post or form requires it |
| DOC / RTF / TXT | Yes on most ATS platforms | Fallback, less faithful layout |
| Scanned PDF or image | No text to extract | Never for an online application |
The manual check is simple: open the PDF, select a sentence, and paste it into a text editor. If you cannot select the text, the ATS cannot read it either. The rest of this tutorial automates that check.
The five formatting rules that matter most#
One column. Parsers often read left to right, line by line. A two-column layout can merge the left and right columns into one scrambled sentence. Jobscan documents this “text-layer scrambling” and recommends a single column for anything the ATS must read. A decorative divider rarely breaks a parse; a three-column skills grid often does.
Standard section headings. Use “Work Experience”, “Education” and “Skills”. Creative labels such as “My Journey” or “The Toolkit” give the parser less to work with. If you apply in France, the local equivalents are “Expérience professionnelle”, “Formation” and “Compétences”; keep one language per document.
Complete, consistent dates. Write March 2022 – Present or 03/2022 – 03/2026, with both month and year. Forms such as 2022 – 2026 without months, Mar '22 or '22 make it harder for the software to calculate years of experience. Pick one format and keep it across the document.
A standard font and readable sizes. Arial, Calibri, Georgia, Helvetica or Source Sans 3. Jobscan recommends 10 to 12 points for body text and 14 to 16 points for headings. A decorative font or a phone icon instead of the word “Phone” can come out as [NULL] or an unreadable glyph.
No table for skills. A comma-separated list, vertical bars or bullets parse correctly. A two-column table that lines up “Java” and “expert” asks the parser to understand a grid; some do, many do not. The risk is not worth it.
For developers, add two rules. Put your GitHub, portfolio and LinkedIn links in the body of the document, not in the header or footer, which many parsers ignore. And name technologies the way the employer names them: “TypeScript”, “PostgreSQL”, “Kubernetes”, not “modern JS ecosystem”.
The tutorial: a YAML resume, versioned and verifiable#
RenderCV builds a resume from a YAML file and produces a PDF through Typst. The appeal for a developer is twofold: the content stays as versionable text in Git, and the PDF keeps a clean text layer. RenderCV's ATS report tested 20 PDFs from 4 resumes and 5 themes with two text extractors and three commercial parsers; all 20 PDFs were read correctly, with an average accuracy of 99.1% for pdftotext and PyMuPDF. The small gap came from typography (curly quotes), not missing content.
Step 1: install RenderCV#
RenderCV requires Python 3.12 or newer. Work in a virtual environment so its dependencies do not mix with your system packages.
python3 --version
python3 -m venv .venv
source .venv/bin/activate
pip install "rendercv[full]"
rendercv --versionOn Windows, activate the environment with .venv\Scripts\activate. The rendercv new command creates a sample file; --locale english keeps the internal labels in English.
mkdir resume && cd resume
rendercv new "Alex Durand"
lsYou get Alex_Durand_CV.yaml. Open it in VS Code: RenderCV's JSON Schema enables autocomplete and field validation.
Step 2: write the content, not the layout#
Replace the sample with your information. The file below shows the useful structure: a short summary, experience with measured results, education, and skills as simple lines. The section keys become the PDF headings; keep them standard.
cv:
name: Alex Durand
headline: Senior Backend Engineer
email: [email protected]
phone: "+1 415 555 0142"
website: https://alexdurand.dev
social_networks:
- network: GitHub
username: alexdurand
- network: LinkedIn
username: alexdurand
sections:
Summary:
- Backend engineer with 7 years of experience building high-traffic APIs.
Focused on TypeScript, Python and PostgreSQL.
Work Experience:
- company: Acme
position: Senior Backend Engineer
start_date: 2022-03
end_date: present
highlights:
- Cut p95 response time from 420 ms to 180 ms by rewriting the
slowest PostgreSQL queries.
- Migrated 14 services to Kubernetes with 99.95% availability
measured over 12 months.
- Mentored 3 engineers and reviewed 400+ pull requests.
- company: Studio North
position: Full Stack Engineer
start_date: 2019-09
end_date: 2022-02
highlights:
- Built a CI pipeline that reduced deployment time from
45 minutes to 6 minutes.
- Developed a GraphQL API used by 120,000 accounts.
Education:
- institution: University of Technology
area: Computer Science
degree: Master's
start_date: 2017-09
end_date: 2019-06
Skills:
- label: Languages
details: TypeScript, Python, Go, SQL
- label: Data
details: PostgreSQL, Redis, Kafka
- label: Infrastructure
details: Docker, Kubernetes, Terraform, AWSThree content choices matter more than the format. The job title in the resume matches the posting when it is honest. Each bullet starts with a verb and ends with a measurable result. Skills named in the posting appear at least once inside an experience entry, not only in the final list.
Step 3: render a single-column PDF#
The engineeringresumes theme produces a sober, single-column layout suited to a technical profile. The design block sets the page size and 0.7-inch margins, inside Jobscan's recommended 0.5-to-1-inch range.
design:
theme: engineeringresumes
page:
size: us-letter
top_margin: 0.7in
bottom_margin: 0.7in
left_margin: 0.7in
right_margin: 0.7in
show_footer: false
typography:
font_family: Source Sans 3
font_size:
body: 10ptUse size: a4 for Europe and most of the rest of the world; us-letter is the default for the United States and Canada. Render only the PDF: the Markdown, HTML and PNG files are not needed here.
rendercv render Alex_Durand_CV.yaml -nomd -nohtml -nopng
ls rendercv_outputThe PDF appears in rendercv_output/. Open it, check that it fits on one page if your experience allows, and that no line is cut off. A second page is not disqualifying; an orphaned skills block at the top of page two already is.
Step 4: prove the text can be extracted#
This is the step most tutorials skip. pdftotext, shipped with Poppler, extracts text the way a parser would. Install it, convert the PDF, then search for your section headings and technologies.
sudo apt install poppler-utils
pdftotext -layout rendercv_output/Alex_Durand_CV.pdf resume.txt
grep -nE "Work Experience|Education|Skills" resume.txt
grep -c "TypeScript" resume.txt
sed -n '1,40p' resume.txtThe first grep should print the three headings. The second should return at least 1. If headings are missing, the cause is often a table, frame or image; if accents come out as é, the PDF font or encoding is at fault. Fix either before sending.
Running pdftotext without -layout gives another view: it follows the text stream rather than the visual position. If the no-layout output is unreadable while the preview looks fine, your layout is probably too complex.
Step 5: tailor keywords to the job#
Read the posting and pull out 10 to 15 terms by hand: job title, languages, databases, cloud, methods. Place them in this order of priority:
- The title under your name, if it matches your real experience.
- The two- or three-line summary.
- One experience bullet per important skill, with a result.
- The “Skills” section, for tools mentioned only once.
Do not copy the whole posting. A recruiter spots a list of words without context, and a technical interview takes it apart in ten minutes. The useful rule: every keyword you add must be backed by a project, a role or a number.
For an international application, translate section headings and job titles to the local language. Keep company names and technologies as they are. Dates can stay in 2022-03 form in YAML: RenderCV displays them according to the document locale.
Step 6: name the file and choose the right export#
Name the file with your name, the role and the year: Alex-Durand-senior-backend-engineer-2026.pdf. Avoid Resume_final_v3.pdf, spaces and accents in the filename. Some forms rewrite the name, but a readable file helps the recruiter downloading 80 attachments.
If the job asks for .docx, RenderCV does not produce it: it generates PDF, Markdown, HTML and PNG. Keep the same content in a single-column Word document, or use a tool that exports both formats. Never send an image PDF to work around a Word request.
Check with JSON Resume and parser tools#
JSON Resume is an open schema, version 1.7.0, with 14 sections, all optional. It does not replace RenderCV: it serves as a portable data format that themes and tools can read. If you want to keep a resume.json alongside the YAML, the resume-cli tool requires Node.js 18 or newer.
npm install -g resume-cli
resume init
resume validate
resume audit resume.json
resume export resume.txt --format textresume audit scores how well a theme's output reads in applicant tracking systems and prints failed checks. The score is advisory: it depends on the theme and the tool's own rules, not on a universal standard. resume export resume.txt produces a text version useful for checking that nothing is missing.
One more test costs nothing: copy all the PDF text and paste it into a plain-text editor. If sections merge or bullets turn into odd characters, render again with a simpler theme. The content must remain readable without the styling.
Traps that cost an interview#
The misplaced photo. In France, a photo is common and an ATS will not automatically reject a resume because of it. The risk lies elsewhere: a photo inside a frame or header can be ignored, and in the UK, US and Canada it is discouraged. If you include one, keep it in the body, small and sharp.
The PDF exported from a design tool. Canva and graphic editors produce beautiful PDFs, sometimes with layered or rasterised text. The pdftotext test settles it. If no text comes out, rebuild the document in a tool that writes text, not pixels.
Tables and columns. A skills grid, a “soft skills” box on the right, a timeline: each can shift the reading order. Keep tables for interviews and your portfolio, not for the application.
Approximate dates. 2020 – 2023 without months prevents an accurate calculation of years of experience. Mar '21 with an apostrophe can be misread. Write March 2021 – March 2023.
Icons instead of words. An envelope icon next to your email looks tidy. If the parser does not recognise the icon font, it can output an empty glyph. Write Email: and Phone:.
Keyword stuffing. Repeating “React” twelve times does not double your chances. Recruiters see the list, and interviews test the level. Three contextual mentions beat twelve repetitions.
Invented numbers. “+300% performance” without context collapses in an interview. Prefer a number you can explain: “p95 cut from 420 ms to 180 ms”, “deployment from 45 to 6 minutes”, “120,000 accounts served”.
JSON Resume and CVMalin: two other paths#
RenderCV fits if you like the terminal, Git and text files. JSON Resume fits if you want a data format independent of rendering and interchangeable themes. CVMalin fits if you prefer a graphical interface and an immediate export.
CVMalin, from the same publisher as this blog, offers 71 templates, a live A4 preview and a free ATS checker. Building the resume and running the check are free; downloading a PDF or Word file requires a $5, $10 or $20 pass depending on duration, with no renewing subscription. It is one option among others, useful when an application must go out today and you do not want to install Python. Its interface and template set lean French, so check the output against the conventions of the country you are applying in.
None of these tools knows the exact rules of a given company's ATS. The only reliable test remains text extraction plus reading the posting. A clean, targeted resume is still a human document: the ATS only decides whether it reaches the right queue.
If you want a portfolio to go with the resume, our tutorial on building a landing page in 10 minutes with shadcn/ui blocks gives you a clean presentation page. To put it online, the step-by-step Next.js deployment with Coolify covers the domain and HTTPS.
How long it takes, and what it buys you#
The first version takes 35 to 45 minutes: install, content, render, check. Later applications take 10 to 15 minutes: copy the YAML, adjust the title, summary and three bullets, rerun rendercv render, repeat pdftotext.
The result is not a guarantee of an interview. An ATS-readable resume prevents information from being lost before a human reads it. It does not compensate for a mismatched profile, a misaligned salary or a generic cover letter. It gets you through the first door, the one that silently removes unreadable files.
Frequently asked questions#
Frequently asked questions
Should I send a PDF or a Word file?
A text-based PDF is the default: the layout stays stable and the text can be extracted. Send a .docx when the job post or form requires it. Never send a scanned PDF or an image: the parser finds no text in it.
Do ATS platforms read resumes with a photo?
An ATS reads text, not the photo. A photo in the body does not necessarily block extraction, but it can be ignored, and it is discouraged in some markets. In France it remains accepted; for an international application, check local practice.
How many pages should a developer resume have?
One page is enough up to about seven years of experience; two pages are accepted beyond that. The useful constraint is not the page count but density: every line should carry a result, a technology or a responsibility. A half-empty second page should become one full page.
Should I copy every keyword from the job post?
No. Use the exact terms that describe your real experience, then place them in the title, summary, bullets and skills section. A list of 40 words without context stands out and collapses in an interview. Aim for 10 to 15 defensible terms.
Is RenderCV free?
Yes. RenderCV is an open-source project, installed with pip install "rendercv[full]". It generates a PDF through Typst, which is also open source. RenderCV's ATS report documents its tests with pdftotext, PyMuPDF and three commercial parsers; the test code is published in the repository.
Does an ATS-friendly resume guarantee an interview?
No. It guarantees that your content reaches the recruiter's database in readable form. The interview still depends on actual skill, fit for the role, salary and timing. A 75% ATS score shown by a tool is an indicator internal to that tool, not a market standard.
Sources#
Official pages, documentation and pricing pages checked on November 6, 2026. Prices are in US dollars where stated.
- Jobscan — How to Write an ATS Resume
- Jobscan — ATS formatting mistakes
- Jobscan — ATS tables and columns
- Bullhorn — Resume Parsing in Bullhorn ATS
- Oracle Taleo — Attachment file formats
- RenderCV — documentation
- RenderCV — ATS Compatibility Report
- RenderCV — CLI reference
- RenderCV — cv field
- RenderCV — design field
- JSON Resume — schema 1.7.0
- JSON Resume — CLI
- Typst — version 0.14 and tagged PDFs
- CVMalin — pricing
- Logoforge — SVG logos



Comments
Loading comments…