Software engineer resume example
One page for most people, two once you have a decade behind you. Reverse chronological, no columns, no photo. What follows is the shape US hiring teams read fastest, and the wage data comes from BLS rather than an aggregator.
Applying in India? See the software engineer resume written for Indian employers
The bullets and skills are this page's own. The name, employer and dates are invented.
An applicant tracking system usually reads your resume as plain text before a person does. This page covers what that text should hold for software engineer roles: the words postings use, bullets with real numbers in them, and a layout a parser can read. Every example here is invented, written to show how specific a strong software engineer resume gets.
Must-have skills for a software engineer resume
These skills come up often in software engineer job postings, and recruiters search their ATS for them. Include every one you genuinely have, in the words the posting uses.
Pro tip: mirror the job description exactly
If the job description says "React.js" and you write "React", a recruiter searching for the exact term may not find you. Use the posting's phrasing and acronyms in your skills section and bullet points, where they are true of you.
Strong software engineer resume bullet examples
Every bullet below follows the same formula: strong action verb + what you did + quantified impact. Study the structure, then replace the numbers with your real achievements. Generic bullets like "responsible for X" tell a recruiter nothing about what you achieved.
Action
Start with Built, Reduced, Migrated, Designed, Optimized, Led.
Tools
Name the exact tool or method: Python, Java, TypeScript, Go.
Impact
End with a number: time saved, cost, volume, quality, or people served.
Software Engineer - Scope and ownership
01
Led the migration of a payments monolith to seven services, cutting median deploy time from 47 minutes to 9 and removing the release freeze that had blocked Friday shipping.
Software Engineer - Performance
02
Rewrote the notification pipeline in Go to handle 2.1M events per day at p99 latency of 180ms, down from 1.4s, with no increase in infrastructure spend.
Software Engineer - Debugging
03
Found and fixed an N+1 query pattern in the ORM that accounted for 38% of database load; API p95 fell from 820ms to 240ms across all endpoints.
Software Engineer - Mentoring
04
Mentored four engineers through weekly one-to-ones and review; three were promoted within eighteen months and two now lead their own services.
Common mistake: weak action verbs
Avoid passive openers like "Responsible for", "Helped with", or "Worked on". These tell the recruiter nothing about your actual contribution. Replace them with ownership verbs: Built, Designed, Led, Reduced, Launched, Architected, Negotiated, Delivered. Then always end with a number.
The bullets above, in a finished resume
Rendered by the same exporter the builder uses, in an ATS-safe single-column template. No tables and no side columns, because that is what the format advice further down this page tells you to avoid.
The bullets and skills are this page's own. The name, employer and dates are invented.
Software engineer resume writing guide
Three areas where most software engineer resumes either win or lose against the competition. Read each section carefully, even one improvement here can meaningfully increase your response rate.
What a US hiring team looks for first
Scope, then evidence. A recruiter scanning your resume is trying to work out what size of problem you have handled and whether the result is yours or your team's. Name the system, the change and the number it moved, in that order. Lead with impact rather than responsibility. "Responsible for the payments service" tells them nothing they cannot infer from your title. "Cut median deploy time from 47 minutes to 9" tells them what happened while you were there.
How to write bullets a parser reads cleanly
Start with a verb, put the number in the middle, and finish with what it enabled. Avoid tables, columns and text boxes: parsers read them out of order or drop them entirely, and a bullet that lands in the wrong section reads as nonsense. Quantify the thing you actually changed. Latency, throughput, cost, deploy frequency, incident count, review turnaround. If you cannot measure it, describe the scope instead: how many services, how many engineers, how much traffic.
Sections, in order
Contact, summary, experience, skills, education. Projects go above education if you are early in your career and below it once you have three or four years of work to point at. Leave out: a photo, your date of birth, marital status, full street address and your Social Security number. US hiring norms prohibit employers from asking for most of these before an offer, and including them signals unfamiliarity rather than openness.
Software engineer salary in the United States
National figures for Software Developers, the occupation BLS counts this job under. These are percentiles across everyone employed in it, not steps on a career ladder: half of all workers earn more than the median and half earn less.
10th percentile
$82,460
Nine in ten earn more than this
Median
$135,980
Half earn more, half earn less
90th percentile
$214,670
One in ten earns more than this
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (OEWS), national cross-industry estimates, May 2025, SOC 15-1252. Annual wages, excluding bonuses, equity and other non-wage compensation. Current release at bls.gov/oes.
See the full pay range, from the 10th to the 90th percentile, and pay by metro
How to use these numbers
They are national and cross-industry, so your city and sector move them a long way. Use the median as the anchor, name a specific number rather than a range, and justify it with the single most quantified achievement on your resume.
Software engineer resume format and structure
Standard section names in a familiar order are easiest for an ATS to parse and for a recruiter to skim. Use this structure:
Section 01
Contact information
Name, professional email, phone, LinkedIn URL, and city/country. No photo, no date of birth, no full address. Keep it to 2 lines maximum.
Section 02
Professional summary
2-3 sentences. Years of experience as a software engineer, your primary specialty, and your single biggest quantified achievement. No fluff.
Section 03
Work experience
Reverse-chronological order. Company name, your title, dates (month/year), location. 3–5 bullet points per role, each with a number. Most recent role gets the most bullets.
Section 04
Skills
List Python, Java, TypeScript, Go, React, and other relevant tools. Group by category if you have 10+ skills.
Section 05
Education
Degree, institution, graduation year. No GPA unless above 3.5 and within 3 years of graduation. Certifications go here or in a separate Certifications section.
Section 06
Optional sections
Projects (essential for early-career), Certifications, Publications, Open Source, or Languages. Only include if genuinely adding signal.
Questions
Software engineer resume, frequently asked questions
Answers to the most common questions job seekers have when writing a software engineer resume, covering format, keywords, length, and ATS optimization.
Resume examples for other roles
Need a guide for a different job title? Each page includes role-specific ATS keywords, real bullet examples, and a writing guide.
Build your software engineer resume
Use our free tools to build, score, and optimize your resume for the specific job description you're applying to.
Sources and references
Where the skills, tooling and pay figures on this page come from.
From example to yours
Start from this, then make it yours
The builder takes an example like this one and lets you edit it in place. The score updates as you type, so you can see whether a change helped rather than guessing.
Open the builder
The real resume library, on a sample account with sample scores.
Build your software engineer resume, free
Start from an example like this in the builder and watch the score move as you edit. Building, scoring and a watermarked export are free, with no card.