RefolkCandidates
JobsBuild my resume

Resume example

Software Engineer resume example

Designs, writes, and ships the code behind a product. Below is a complete software engineer resume, written the way one has to be written to survive a first screen, with every bullet explained underneath.

6,200
open right now
850
companies hiring right now
26%
of those openings are remote
Mostly in

San Francisco, New York, Mountain View

Hiring now
  • Anduril Industries353
  • SpaceX246
  • Databricks161
  • OpenAI147
  • Applied Intuition92
  • Roblox92
  • Rippling89
  • Waymo86

Counted by Refolk from the public job boards of 1,745 companies, refreshed through the day. These are live openings, not a forecast, so the numbers move as roles are posted and filled.

Alex Moreno

Software Engineer

alex.moreno@example.com · +1 555 0134 · Berlin · alexmoreno.example

Summary

Software Engineer with eight years of experience. Shipped a billing rewrite that cut failed payments from 4.1% to 0.6%, recovering roughly $40k a month in lost revenue. Looking for a software engineer role with more ownership of Python and the decisions around it.

Experience

Senior Software Engineer, Northwind Systems

2022 - Present

  • Shipped a billing rewrite that cut failed payments from 4.1% to 0.6%, recovering roughly $40k a month in lost revenue.
  • Cut p95 API latency from 840ms to 210ms by replacing three chained lookups with a single materialised view.
  • Migrated 60 services off a deprecated auth library over two quarters with no customer-facing downtime.

Software Engineer, Meridian Labs

2018 - 2022

  • Owned the TypeScript side of the work at a 40-person product company, and documented it well enough to hand over cleanly.
  • Set the approach the team still uses for Go.

Skills

Python · TypeScript · Go · REST APIs · PostgreSQL · Docker · CI/CD · Git

Education

BSc Computer Science, 2018

A sample, not a real person. The name, the employers, and the figures are invented to show the shape of a strong page - use the structure and put your own evidence in it.

How to read this software engineer resume example

The sample above is not a template to copy word for word - copied resumes read as copied. It is here to show the shape of a page that gets past a first screen: one column, standard headings, and bullets that end in an outcome rather than a duty. Evidence you have shipped something real to production and owned it afterwards.

  • Every bullet opens with a verb and carries a number. That is the pattern, not a coincidence.
  • The summary makes a claim and then supports it in the first bullet underneath.
  • Skills are named tools, not adjectives, and each one appears again in the experience section.
  • The earlier role is short. Recent work carries the weight of the page.

The numbers in a software engineer resume

The most common thing missing from a software engineer resume is a number. Not because the work had none, but because nobody wrote them down at the time. These are the measures a software engineer can usually reach for, and the example uses them.

  • Shipped a billing rewrite that cut failed payments from 4.1% to 0.6%, recovering roughly $40k a month in lost revenue.
  • Cut p95 API latency from 840ms to 210ms by replacing three chained lookups with a single materialised view.
  • Migrated 60 services off a deprecated auth library over two quarters with no customer-facing downtime.

Before and after: rewriting a weak bullet

Most software engineer resumes are one edit away from being much stronger, and the edit is the same every time: replace the description of the job with the result of doing it. The pairs below are the same work, written twice.

  • Weak: "Responsible for python and related tasks." Strong: "Shipped a billing rewrite that cut failed payments from 4.1% to 0.6%, recovering roughly $40k a month in lost revenue."
  • Weak: "Worked on typescript projects across the team." Strong: "Cut p95 API latency from 840ms to 210ms by replacing three chained lookups with a single materialised view."
  • Weak: "Helped improve processes and supported software engineer initiatives." Strong: "Migrated 60 services off a deprecated auth library over two quarters with no customer-facing downtime."

Adapting the example to your own history

Work backwards from the posting. Find the two or three things it actually screens for, then make sure the top third of your page answers them. Everything below that is supporting evidence.

  • Reorder your bullets so the one closest to the posting comes first in each role.
  • Rewrite the summary for the specific job. It is the only part a human reliably reads.
  • Cut any skill you would not want to be asked about for ten minutes.
  • Keep Python, TypeScript, Go visible in context, not stranded in a list.

FAQ

Can I copy this software engineer resume example?
Copy the structure, not the sentences. The layout, the ordering, and the shape of the bullets all transfer. The content does not: a recruiter who reads twenty resumes for the same role notices identical phrasing quickly, and the numbers in this sample are illustrative rather than anyone's real history.
What if I do not have numbers like these?
Most people have more than they think. Look for volume, frequency, time, cost, error rate, or a before-and-after on anything you touched. Where the number genuinely does not exist, say what changed and who noticed - "the process that used to need a weekly meeting now does not" is a real outcome without a metric.
How long should a software engineer resume be?
One page up to about eight years of experience, two pages beyond it. This example is one page. Length signals scope, so a long page with small-scope bullets reads worse than a short one.
Will this format pass an applicant tracking system?
Yes. One column, real text, standard headings, and no graphics or tables is the format parsers handle reliably. Most parsing failures come from multi-column layouts, text inside images, and headings the parser does not recognise.
Should the example change for a more senior software engineer role?
The structure stays. What changes is the scope in the bullets: more ambiguity you resolved yourself, more decisions with a tradeoff, and more effect on work that was not directly yours. Evidence you have shipped something real to production and owned it afterwards.

More for software engineers

Software Engineer resume guideSoftware Engineer cover letterSoftware Engineer interview prepBuild a software engineer resume

Other resume examples

Frontend Engineer resume exampleBackend Engineer resume exampleFull Stack Engineer resume exampleMobile Engineer resume exampleDevOps Engineer resume exampleSite Reliability Engineer resume exampleSecurity Engineer resume exampleQA Engineer resume exampleEngineering Manager resume examplePlatform Engineer resume example

Pick a layout

Resume templatesATS-friendly resume templateOne-page resume template

Put this to work

Reading about the job search is not the job search.

Paste your career in once. I write the resume, then every week I rank the live openings against your history, tailor a resume and a cover letter to the best of them, and keep going until you land. You press send, and that is the whole of your part.

  • 140+ curated roles a week, found, written, and scored for you.
  • Every bullet stays inside what your history actually supports.
  • Queued, submitted, interviewing, offer, all in one place instead of a spreadsheet.
Build my resumeHow auto apply works

500 free credits on sign-up. No card.