Software Engineer resume example

A complete example you can copy from. The person and companies are made up; the structure is what works.

Ryan Mitchell

Software Engineer · Backend, APIs and cloud infrastructure

Austin, TX·ryan.mitchell@email.com·(512) 555-0173·linkedin.com/in/ryan-mitchell

Summary

Backend software engineer with 6 years of experience building APIs and services in Go and Python for payments and logistics products. Led the move of a monolith to services on AWS, cut p95 latency by 60% and mentor three engineers. Comfortable owning a feature from design doc to on-call.

Experience

Software Engineer II·LedgerlyMar 2022 – Present

Austin, TX

  • Split the payments monolith into five Go services on AWS ECS, cutting p95 checkout latency from 900 ms to 350 ms.
  • Designed an idempotent retry queue for card payouts that brought failed payouts from about 1.2% to under 0.1%.
  • Built the internal feature-flag service now used by 14 teams to ship behind flags and roll back in seconds.
  • Wrote the team's on-call runbooks and alert rules, reducing pages per week from 30 to 8.
  • Mentor three junior engineers through code review and pairing; two were promoted within 18 months.

Software Engineer·Routewise LogisticsJul 2020 – Feb 2022

Dallas, TX

  • Built REST and GraphQL APIs in Python (FastAPI) that served live shipment tracking to 2,000+ business customers.
  • Moved slow reporting queries to read replicas and added indexes, taking the main dashboard load from 12 s to 1.5 s.
  • Added contract tests to the CI pipeline, catching breaking API changes before release and halving rollbacks.

Education

B.S. Computer Science2016 – 2020

Texas State University

Skills

Go · Python · TypeScript · PostgreSQL · Redis · AWS (ECS, Lambda, SQS) · Docker · Kubernetes · Terraform · GraphQL · CI/CD with GitHub Actions · System design

Certifications

AWS Certified Developer – Associate

Languages

English (Native or Bilingual)

Make yours from your LinkedInFree, no sign-up. Your PDF never leaves your browser.

What a software engineer resume needs to show

Engineering resumes are read by two very different people. A recruiter checks whether your stack and level match the opening, often in under a minute. Then an engineer or engineering manager reads the bullets and asks harder questions: was this person driving the work or nearby when it happened, how big was the system, and did anything measurable change?

Answer both. Put your languages and level where the recruiter will see them, then make every bullet about what you built, the scale it ran at and the result: latency, uptime, cost, adoption by other teams, incidents avoided. “Worked on microservices” says nothing; “split the monolith into five services and cut p95 latency by 60%” gives an interviewer something to dig into.

Resume summary examples

A summary is optional for engineers, but a short one helps when your title is vague (“Software Engineer II” means different things at every company). Say your area, years and one result.

Mid-level backend: Backend engineer with 6 years in Go and Python, building payment and logistics APIs on AWS. Led a monolith-to-services migration that cut p95 latency by 60%.

New graduate: Computer science graduate with two internships in full-stack development (React, Node.js, PostgreSQL). Built and shipped a campus marketplace app used by 1,200 students; code and write-up on GitHub.

Senior or staff: Staff engineer with 12 years in distributed systems. Set the architecture for a platform handling 40,000 requests a second, and grow engineers through design reviews and mentoring.

If you are coming from a bootcamp or another career, a short resume objective that names the role you want and what you built while learning can do the same job.

How to list your tech stack

Group skills so they can be scanned in a few seconds, and keep the job ad’s exact words (an applicant tracking system and a recruiter both match on “PostgreSQL”, not “SQL databases”):

Languages

  • Go
  • Python
  • TypeScript
  • Java
  • C#
  • SQL

Frameworks

  • FastAPI
  • Django
  • Spring Boot
  • Node.js
  • React

Data and infrastructure

  • PostgreSQL
  • Redis
  • Kafka
  • AWS or GCP
  • Docker
  • Kubernetes
  • Terraform

Practices

  • system design
  • testing and CI/CD
  • observability
  • code review
  • on-call

Leave out skill bars, star ratings and “proficient in Microsoft Word”. Put the stack used in each role inside the bullets too, so a reader can see where you used Kubernetes and not only that you know the word.

Bullet points that show impact

Each bullet should answer “so what?”. Start with an action verb, name the technology when it matters and end on the measurable result:

  • Split a payments monolith into five Go services on AWS, cutting p95 checkout latency from 900 ms to 350 ms.
  • Designed an idempotent retry queue that brought failed payouts from 1.2% to under 0.1%.
  • Built an internal feature-flag service adopted by 14 teams, so releases can be rolled back in seconds.
  • Reduced monthly AWS spend by $9,000 by right-sizing instances and moving batch jobs to spot capacity.
  • Added contract tests to CI that catch breaking API changes before release, halving rollbacks.
  • Rewrote alert rules and runbooks, taking on-call pages from 30 a week to 8.
  • Led the design review and rollout of a new auth flow for 300,000 users with zero downtime.

No numbers? Use scale (requests per second, users, teams depending on it), before and after (minutes to seconds), or scope (“owned end to end, from design doc to launch”).

Projects and GitHub

For new graduates, bootcamp grads and career changers, a projects section often matters more than the experience section. Two or three projects are enough if each one has a name, the stack, what it does and a link. Projects with real users, a deployed URL or a clear README beat a long list of tutorials.

Experienced engineers can usually skip it, unless a side project shows something their job doesn’t (say, Rust or mobile when your day job is Java). A GitHub link goes in the summary or next to a project; it only helps if the pinned repositories are ones you would happily discuss in an interview.

Tips for a software engineer resume

  • Make your level obvious. Mention scope words that match it: “owned”, “led the design”, “mentored” for senior roles; “shipped”, “built”, “fixed” for earlier ones.
  • Keep it to one column and plain text. Two-column templates and icons often scramble in parsers. An ATS-friendly resume is boring to look at and easy to read.
  • Cut the obvious. Git, Jira, Agile and “problem solving” are assumed. Use the space for one more result.
  • Tailor the top third. Reorder skills and the summary for each application so the first lines match the role (backend, frontend, platform, mobile).
  • Be ready to defend every line. Interviewers pick bullets and ask “how exactly?”. If you can’t explain a number, round it or drop it.

LinkedIn headline examples

Tech recruiters search LinkedIn by stack and seniority, so a LinkedIn headline that says both gets you into more searches:

  • Software Engineer · Backend | Go, Python, AWS | Payments and distributed systems
  • Senior Software Engineer at a fintech · Building reliable APIs · Mentor
  • New Grad Software Engineer · React, Node.js, PostgreSQL · Open to full-stack roles

Already have your roles and projects written on LinkedIn? Export the profile PDF and run it through LinkedIn to resume: it gives you a clean one-column draft in the browser, and you can tighten the bullets before downloading.

Wondering what the job pays? See what a software engineer earns on our Software Engineer salary page: the median, the pay range and what moves it.

Pixelin

The same resume as a Pixel CV

This is Ryan's profile as a 16-bit character sheet: years of experience become a level, languages become hearts. It is not for job applications, it is for your LinkedIn feed, where a picture gets far more attention than a text post.

Create your Pixel CV

FAQ

Should I put my GitHub on a software engineer resume?

Yes, if it has something worth opening, such as a project with a clear README or real contributions to open source. An empty profile or a page of tutorial forks adds nothing, so leave it off rather than send people there.

How long should a software engineer resume be?

One page for most engineers with under ten years of experience. Senior and staff engineers can use two, as long as the second page is still about impact and not a full list of every technology touched.

Should I include a projects section if I already have work experience?

Only if the projects show something your jobs don't, such as a different language or a product with real users. Otherwise the space is better spent on stronger work bullets.

Do I need to list every programming language I know?

No. List the languages and tools you could be interviewed on tomorrow, starting with the ones the job ad names. A long list of things you used once makes it harder to see what you are actually good at.

Daniel Peris

Written by

Daniel Peris

Entrepreneur and product builder

On the internet since 1995 and launching online products since 2009, from one of the first app marketing agencies to tools like Pixelin. Writes about LinkedIn, resumes and standing out online.