A software engineer resume gets scanned for two things fast: what you've actually shipped, and whether your stack matches the role. Listing frameworks isn't enough — the strongest resumes tie each project to a measurable outcome (latency, uptime, users, revenue) instead of just describing responsibilities.
Resume summary example
“Backend-focused software engineer with 5 years building and scaling APIs serving 2M+ daily requests. Shipped a service migration that cut p95 latency by 40% and led a 4-person team through a zero-downtime database migration. Comfortable owning a feature from design doc to production.”
Experience bullet point examples
- Led the migration of a monolithic billing service to microservices, reducing average API response time from 800ms to 210ms
- Built a CI/CD pipeline using GitHub Actions that cut deployment time from 45 minutes to 6 minutes across 12 services
- Designed and shipped a rate-limiting layer that reduced downstream database load by 35% during peak traffic
- Mentored 3 junior engineers through code review and pairing, two of whom were promoted within a year
- Diagnosed and resolved a memory leak in a Node.js service that had caused weekly production restarts, eliminating the issue entirely
Skills to include
Hard skills
Soft skills
Common mistakes to avoid
- Listing every language and framework you've ever touched instead of the 6-8 that are actually relevant to the job posting.
- Describing responsibilities ("worked on the payments team") instead of outcomes ("reduced payment failure rate by 18%").
- Leaving out scale — "built an API" tells a recruiter nothing; "built an API handling 500K requests/day" does.
Frequently asked questions
Should I include a GitHub or portfolio link?
Yes, if it's current and reflects your best work — a stale or empty GitHub profile linked prominently can hurt more than help. Put it in the header next to your email.
How technical should the bullet points be?
Specific enough to prove depth (name the actual technology and the actual metric), but written so a non-technical recruiter can still tell it mattered. Lead with the outcome, follow with the how.