Your resume has to pass two judges in order: a machine, then a human. Most software engineers optimize for neither — they make a pretty resume the ATS (applicant tracking system) can't parse, or a parseable one that bores the recruiter who skims it for six seconds. This guide gets you past both: beat the bots, then win the read.
Part 1: Beat the ATS
An ATS parses your resume into structured fields and ranks it against the job description. To survive it:
- Use a simple, single-column layout. No tables, text boxes, columns, headers/footers, or graphics — they scramble parsing.
- Standard section headings — "Experience", "Education", "Skills". Don't get creative.
- Submit as .docx or a text-based PDF (not an image/exported-as-picture PDF).
- Mirror keywords from the job description — if it says "REST APIs" and "PostgreSQL", use those exact terms (truthfully).
- Standard fonts, no fancy icons for contact info.
Part 2: Win the human
Once you're parsed and ranked, a recruiter skims you for a few seconds. Make those seconds count:
- Quantify every bullet. "Improved performance" → "Cut API p99 latency 40%, serving 2M requests/day." Numbers are what stop the skim.
- Lead with impact, not duties. Start bullets with a strong verb and a result, not "Responsible for…".
- Put the strongest, most relevant work first. Recruiters read top-down and rarely reach the bottom.
- One page for early career; two only with real senior experience.
The quantified-bullet formula
Action verb + what you did + measurable result. "Built", "Led", "Reduced", "Shipped" + the work + a number. If you can't measure it directly, use proxies: time saved, % improved, scale handled, people affected.
Mistakes that get auto-rejected
- Fancy two-column templates that the ATS reads as gibberish.
- No keywords from the job description → low relevance rank.
- Duty-based bullets with zero numbers.
- Typos and inconsistent formatting — humans reject on these.
- A skills section stuffed with everything (dilutes the real signal).
After the resume gets you the interview
A great resume's only job is to earn the conversation — and then your spoken answers decide the offer. The moment you list a project on your resume, you've promised you can explain it well out loud. Greenroom runs real voice interviews so you can rehearse explaining your resume and projects clearly. Pair it with our guides on explaining your project and "tell me about yourself".
Frequently asked questions
How do I make my resume pass the ATS?
Use a simple single-column layout with no tables, text boxes, columns, headers/footers or graphics, since these scramble parsing. Use standard section headings like Experience, Education and Skills, submit a text-based PDF or .docx, use standard fonts, and mirror the exact keywords from the job description truthfully so the system ranks you as relevant.
What format should a software engineer resume be in?
Submit a text-based PDF or a .docx file — not an image-based PDF or one exported as a picture, which an ATS can't read. Use a clean single-column layout, standard fonts, and standard section headings. Avoid fancy two-column templates and graphics, which often get parsed as gibberish and tank your ranking.
How do I write good resume bullet points?
Use the formula action verb + what you did + measurable result, for example 'Cut API p99 latency 40%, serving 2M requests per day.' Lead with impact rather than duties, quantify every bullet (using proxies like time saved or scale if needed), and put your strongest, most relevant work first since recruiters skim top-down.
What gets a resume auto-rejected?
Common auto-rejection causes include fancy multi-column templates the ATS can't parse, missing keywords from the job description, duty-based bullets with no numbers, typos and inconsistent formatting, and a bloated skills section that dilutes your real strengths. Fixing format and adding quantified, keyword-aligned bullets resolves most of these.