A software engineer resume gets read twice, by two very different readers: an ATS looking for specific technical keywords, and (if you pass that filter) an engineer or hiring manager who can tell within about ten seconds whether you actually understand what you claim to have built. Here's how to write for both.
Lead with impact, not just a tech-stack list
"Built a REST API using Node.js and Express" tells a reader what you touched, not what happened as a result. Compare that to: "Built a REST API handling 50K daily requests, reducing average response time from 800ms to 120ms through query optimization and caching." The second version demonstrates judgment and outcome, not just exposure to tools.
List technologies precisely, not vaguely
"Proficient in various web technologies" is the kind of line that makes a technical reviewer skip to the next resume. Name the actual languages, frameworks, and tools - React, PostgreSQL, Docker, AWS Lambda, whatever is genuinely true - both because it reads as more credible, and because ATS keyword matching depends on the specific terms in the job posting appearing in your resume too.
Structure each role around 3-5 strong bullets, not a wall of text
Pick your most significant, most quantifiable contributions per role rather than listing everything you touched. A senior engineer skimming your resume is looking for signal: scale (users, requests, data volume), ownership (did you lead this or contribute to it), and measurable outcome (faster, cheaper, more reliable, more accurate).
Projects matter more here than in most other fields
Especially early in a software career, a well-documented personal or open-source project can carry as much weight as a job. Include a live link or GitHub link if the project is genuinely presentable, and describe it with the same "what you built + outcome" structure as a work experience bullet, not just a one-line mention.
Skip the objective statement; use a short technical summary instead
If you include a summary at all, make it specific: "Backend-focused software engineer with 3 years building distributed systems in Go and Python, currently focused on infrastructure reliability." That's more useful to a reader than "results-driven engineer seeking new challenges."
Don't bury your GitHub, portfolio, or LinkedIn
Put these links in your contact section where they're immediately visible, not at the bottom of the page where a fast skim will miss them.
A note on ATS parsing for technical resumes
Technical resumes are especially prone to a specific ATS problem: skills tables and multi-column layouts. A neat two-column "Languages | Frameworks | Tools" table looks clean visually but can parse incorrectly or get skipped entirely by some ATS software. A single-column list is safer. Our ATS checklist covers this pattern in more depth.
Frequently asked questions
Should I include every programming language I've ever touched? No - list what you can actually speak to in an interview. A shorter, honest list reads better than a long one that invites a question you can't answer well.
Do I need a portfolio site in addition to a resume? Not required, but a live portfolio or well-documented GitHub adds real credibility, especially for frontend, full-stack, and early-career roles where project work carries more weight relative to job history.
How technical should my resume bullets be? Specific enough to be credible to an engineer, but written so a non-technical recruiter doing an initial screen can still understand the outcome. "Reduced page load time by 40%" works for both audiences; deep implementation detail belongs in the interview, not the resume.
Once you've got a draft, run it through CVIEX's ATS Resume Checker against the specific job description you're targeting to see exactly which keywords you're missing.