The best resume format for software engineers
By Mubeen Jawed, founder of ResumeForDev · Updated
The best resume format for software engineers is reverse chronological, single column, on one page. Use this order: header with links, (optional summary), skills, experience, projects, education. New grads put education and projects before experience. Use a readable font such as Calibri, Arial, Garamond or Computer Modern at 10 to 11pt for body text, margins of 0.5 to 1 inch, and export a text-based PDF unless the application asks for Word.
Key points
- Reverse chronological, single column, one page.
- Body font 10 to 11pt, headings 12 to 14pt, name 18 to 24pt.
- Margins 0.5 to 1 inch; never shrink below about 0.5.
- Text-based PDF by default; DOCX only when asked.
Chronological, functional or hybrid?
Use reverse chronological: your most recent role first, with dates. It's what technical recruiters expect and what applicant tracking systems parse most reliably. Functional resumes, which group skills and hide the timeline, are read as an attempt to hide something. A hybrid (a strong skills section above a chronological history) is what most good developer resumes already are.
Section order for a developer resume
| Experienced engineer | New grad or intern | Career changer |
|---|---|---|
| Header and links | Header and links | Header and links |
| Summary (optional) | Education | Summary |
| Skills | Skills | Skills |
| Experience | Projects | Projects |
| Projects (optional) | Experience or internships | Experience (with tech-relevant bullets) |
| Education | Achievements | Education and training |
Some engineers put skills at the bottom; that's fine too. What matters is that a recruiter finds your stack and your most recent work within a few seconds.
Best font and font size for a resume
- Sans-serif: Calibri, Arial, Helvetica, Inter, Lato. Clean and safe everywhere.
- Serif: Garamond, Georgia, Cambria, Times New Roman, Computer Modern (Jake's template). Slightly more traditional and compact.
- Body text: 10 to 11pt. Below 10pt gets hard to read on paper and screens.
- Section headings: 12 to 14pt, bold or small caps.
- Your name: 18 to 24pt.
- Use one font family, two at most. Avoid novelty or script fonts.
Margins, spacing and layout
- Margins of 0.5 to 1 inch on all sides. Jake's template sits at about 0.5 to 0.6.
- Single column. Two-column layouts can be read out of order by parsers.
- Dates right-aligned with a tab stop, not a table or text box.
- No headers or footers for contact details; some parsers skip them.
- No photos, icons standing in for words, or skill-level bars.
PDF or Word?
Send a text-based PDF by default. It keeps the layout identical everywhere, and modern applicant tracking systems read it fine. Send DOCX only when the posting or recruiter asks. Avoid PDFs exported as images (common from some design tools): there's no text in them for an ATS to read. To check, open the PDF and try to select a line of text.
Format checklist
- One page (see how long a resume should be).
- Reverse chronological, every role and school dated.
- Standard headings: Experience, Projects, Education, Skills.
- Body text 10 to 11pt, margins at least 0.5in.
- Single column, no tables or text boxes for layout.
- Text-based PDF that copies out in reading order.
- File name like firstname-lastname-resume.pdf.
ResumeForDev handles all of this automatically: it uses one fixed engineering layout (a port of Jake's resume), auto-fits it to one Letter page and exports a text-based PDF.
Frequently asked questions
- What is the best font for a resume?
- Any clean, standard font: Calibri, Arial, Helvetica or Inter for sans-serif, Garamond, Georgia or Computer Modern for serif. Readability matters more than which one you pick.
- What size font should a resume be?
- 10 to 11pt for body text, 12 to 14pt for section headings, and 18 to 24pt for your name.
- What resume format do software engineers use?
- Reverse chronological, single column, one page, with a grouped skills section. Jake's LaTeX template is the most common example.
- Should my resume be a PDF or Word document?
- A text-based PDF unless the application asks for Word. Make sure the text can be selected and copied.
- What margins should a resume have?
- Between 0.5 and 1 inch. Going below 0.5 inches makes the page look crammed.
Keep reading
- GuidesHow many pages should a software engineer resume be?Should a resume be one page? A clear rule for software engineers by experience level, when a 2-page resume is fine, what to cut first, and how to fit it without tiny fonts.Read
- GuidesWhat makes a software engineer resume ATS-friendlyWhat an ATS resume is, how applicant tracking systems read developer resumes, the ATS-friendly resume format to use, and how keyword matching really works. No myths, no fake scores.Read
- GuidesJake's resume template, with or without LaTeXWhy Jake's resume template is the default for software engineers, how to use it in Overleaf, the Jake Ryan sample, and how to get the same layout without writing LaTeX.Read
- GuidesA Google Docs resume template for developers: Jake's layout in Docs or WordHow to make a resume in Google Docs or Word using Jake's single-column layout: the exact settings, why many built-in Google resume templates break ATS parsing, and how to keep it to one page.Read
