What hiring managers look for in a software engineer resume
Hiring managers and recruiters read a software engineer resume for three things: what you can build with, how big and how critical the things you built were, and whether you can work on a team without close supervision. The first is answered by your skills section and the stack named in each role. The second and third come from your bullet points.
The most useful bullets connect a technical decision to a result someone outside engineering would care about: a page that loads faster, an outage that stopped happening, a release process that went from a day to an hour. "Wrote microservices in Go" tells a reader your tools; "Rebuilt the pricing service in Go, halving checkout latency at peak" tells them why you were worth hiring.
Applicant tracking systems match the words in your resume against the job description, so name languages, frameworks and cloud services exactly as the posting does ("PostgreSQL", not just "databases"). Keep the layout to one column of plain text with standard headings so the parser reads it in the right order.
Links matter more in this field than most. A GitHub profile or portfolio with one or two well-documented projects can carry a junior application. Put the link in your header, and only link work you are happy for a reviewer to read.
Software Engineer resume summary examples
Pick the one closest to your experience and replace every detail with your own. A summary should be three or four sentences; see the summary guide for the structure.
Software Engineer bullet point examples
Each bullet starts with a strong verb, says what you did and shows the result. Only use numbers you can explain in an interview; if you don't know an exact figure, describe the scale instead (for example, "for a 30-bed ward").
Performance and reliability
- Cut p95 API latency from 820 ms to 390 ms by moving pricing lookups to a Redis cache
- Reduced monthly pager incidents from 14 to 3 by adding health checks and automatic rollbacks
- Found and fixed a connection-pool leak that caused weekly database failovers
- Load-tested the order service to 5× normal peak before the holiday sale; no incidents during the event
- Introduced structured logging and dashboards that cut average time to diagnose incidents from hours to minutes
Building features and products
- Built the saved-carts feature end to end (API, database schema, React UI) used by 40% of returning shoppers
- Designed and shipped a public webhooks API now used by 120 partner integrations
- Replaced a nightly batch export with an event-driven pipeline in Kafka so warehouses see orders within seconds
- Wrote the migration plan and scripts to move 300 GB of order history to a new schema with no downtime
- Added feature flags so product managers can roll out changes to 5% of users first
Team, process and mentoring
- Mentored two junior engineers through their first on-call rotations
- Cut CI pipeline time from 25 to 9 minutes by parallelising tests and caching dependencies
- Wrote the team's design-document template, now used for every service change above one sprint
- Raised unit-test coverage of the payments module from 40% to 85% while shipping new features
- Ran fortnightly code-review clinics that shortened average review turnaround from two days to same day
Skills for a software engineer resume
List the skills the job description asks for first, using its exact wording, and leave out tools you could not discuss in an interview. Group them so a reviewer can scan the list in a few seconds.
Languages and frameworks
- Go, Python, Java, TypeScript
- React, Node.js, Django, Spring Boot
- SQL and query optimisation
- REST and gRPC API design
Infrastructure and tools
- AWS, GCP or Azure
- Docker and Kubernetes
- PostgreSQL, Redis, Kafka
- CI/CD (GitHub Actions, GitLab CI)
- Observability: Prometheus, Grafana, OpenTelemetry
Working skills
- System design and design documents
- Code review
- Incident response and on-call
- Mentoring
- Writing for non-engineers
Common mistakes on software engineer resumes
A skills list with every technology you have touched
Thirty tools in a row tells a reviewer nothing about which ones you know well, and invites interview questions you can't answer. Keep the list to what you have used in real work or serious projects, and make sure the job description's main stack appears in your bullets too.
Bullets that describe duties instead of results
"Responsible for backend services" could describe anyone on the team. Say what you built or changed and what happened next. The XYZ formula is a simple way to structure each bullet.
Skill bars and two-column designs
Rating yourself "4 of 5 in Python" means nothing to a reader, and graphic skill bars or multi-column layouts can come out scrambled in an ATS. Plain text in one column is safer for engineering roles.
Listing a GitHub link with nothing in it
If your public repositories are empty forks or unfinished tutorials, leave the link off. One documented project with a clear README is worth more than twenty abandoned ones.
Frequently asked questions
How long should a software engineer resume be?
One page for up to about ten years of experience. Senior and staff engineers with a long record of large projects can use two pages, as long as the first page holds the most recent and most relevant work.
Should I include personal projects?
Yes if you are early in your career or changing fields, and the project shows skills the job needs. Describe it like a job: what you built, with what, and what it does. Experienced engineers can usually leave side projects off unless they are directly relevant.
Do I need a summary on a software engineer resume?
A short summary helps when it names your specialism (backend, mobile, data) and main stack, because that is what a recruiter checks first. Keep it to three lines. A generic objective statement adds nothing.
Should I put my GPA on my resume?
Only in your first year or two after graduating, and only if it is strong (for example 3.5 or higher on a 4.0 scale). After your first full-time role, remove it.
Related guides
- How to Write a Software Engineer Resume: Structure, Impact Bullets and Examples
- The XYZ Formula for Resume Bullet Points, with 20 Before-and-After Examples
- How Applicant Tracking Systems Read Your Resume, and What Actually Gets You Filtered Out
- How to Tailor Your Resume to a Job Description in 15 Minutes
- One-Page or Two-Page Resume? What the Research Says and How to Decide