Software engineer resume
How to write a software engineer resume that gets interviews
Engineering managers read resumes for signal: what you built, how hard it was, what you owned, and what changed because of it. Everything else is noise.
Here's what a strong software engineer or developer resume includes, how to write bullets that show impact, and how to match each resume to the tech stack in the job posting.
What to include
- A headline with the role you want, for example "Backend Engineer, Go and AWS".
- Experience with one line of context per role, then three to five impact bullets.
- Projects that show depth: scale, a hard problem solved, or real users.
- Skills grouped by type (languages, frameworks, cloud, databases), only the ones you can discuss in an interview.
- Links to GitHub, a portfolio or anything live.
Writing bullets that show impact
Start with a strong verb, say what you built and with what, and end with the result. For example:
- "Moved report generation to a Redis job queue, cutting API response time from 1.8 s to 400 ms."
- "Designed the billing service in Go and PostgreSQL, handling 40,000 payments a day."
- "Led the migration from a monolith to three services, with zero downtime."
Match the tech stack in the posting
A backend role at a Python shop and a frontend role at a React shop need different resumes from the same person. Lead with the work that uses their stack, use their terms, and trim what they don't care about.
OneProfile reads your GitHub repositories and your roles, then builds a resume for each job from the parts that match its stack, and shows which of the posting's keywords you cover and which you don't.
Section order by experience level
- Students and new graduates: summary, skills, projects, internships, education.
- Two to eight years: summary, experience, a few strong projects, skills, education.
- Senior and staff engineers: summary, experience with scope and leadership, selected projects or talks, skills, education.
A skills section that reads well
- Languages: Go, Python, TypeScript
- Backend: PostgreSQL, Redis, Kafka, gRPC
- Cloud: AWS (Lambda, DynamoDB, S3), Docker, Terraform
- Frontend: React, Next.js
Tailoring for different engineering roles
- Backend: services, APIs, data models, scale, reliability and latency numbers.
- Frontend: user-facing features, performance, accessibility, design collaboration.
- Full stack: end-to-end ownership, from database to interface.
- Data and machine learning: datasets, pipelines, models, and the business result.
- DevOps and platform: infrastructure as code, deployment speed, uptime, cost savings.
Why engineering resumes get rejected
- Bullets that list duties ("responsible for the API") instead of results.
- A long skills list with no evidence in the experience section.
- No links to code, a portfolio or anything live.
- The same resume sent to backend, frontend and data roles.
Questions
How long should a software engineer's resume be?
One page for under about five years of experience, up to two pages beyond that.
Should I list every technology I know?
No. List the ones relevant to the job that you could discuss in depth. A long list of tools you barely used hurts more than it helps.
Do side projects matter?
Yes, especially early in your career or when switching stacks. Show what you built, its scale and what you learned.
Should I include my GPA on an engineering resume?
Include it in your first year or two out of college if it's strong or the employer asks. After that, your work speaks louder and it can come off.
How do I show impact without exact numbers?
Use the scale you do know (users, requests, team size, time saved) or the before and after ("from manual to automated"). Never make numbers up.
Try it on the next job you apply for.
Build your engineer resume free