ResumeFinch

Software engineers

Software engineer resume template and examples

A strong software engineer resume is one column, usually one page, with experience (or projects, early on) near the top and bullets that name the system, the stack and a measured result. The template here is Keystone, a dense layout built for engineering resumes, shown with a fictional senior backend engineer's resume you can open in the builder and rewrite as your own.

Below the preview you will find example bullets for each career level, rules for when projects should outrank jobs, section orders by stage, and a note on software engineer CVs. If you came looking for the LaTeX layout Keystone is modeled on, the Jake's Resume page compares the two.

Free to build and preview. Downloads are a one-time payment, no subscription.

Harriet Volkov
Senior Software Engineer, Backend and Distributed Systems
harriet.volkov@email.com | (503) 555-0182 | Portland, OR | linkedin.com/in/harrietvolkov | github.com/hvolkov
Summary

Backend engineer with 7 years building payment and freight systems in Go and PostgreSQL on AWS. Designs services that stay correct under retries and partial failure, leads cross-team migrations, and mentors engineers through their first on-call rotations.

Experience
Senior Software Engineer, Payments PlatformMar 2023 – Present
Larkspur CommercePortland, OR
•Led the design of an idempotent payment ledger in Go and PostgreSQL that processes 3M transactions a day with zero double charges since launch.
•Moved 14 services from a shared database to an event stream on Kafka over two quarters, coordinating 4 teams and finishing with no customer-facing downtime.
•Cut p99 checkout latency from 1.8 s to 650 ms by batching fraud-score calls and adding a read-through cache for merchant settings.
•Wrote the design review template now used by the 30-engineer platform group and ran its review meeting for a year.
•Mentored 3 engineers to promotion, including pairing on their first incident command during on-call.
Software Engineer IIJun 2020 – Feb 2023
Cobaltline FreightPortland, OR
•Built the shipment tracking API in Go and gRPC that carriers polled 40M times a month, holding 99.95% availability over its last 12 months.
•Replaced a cron-based invoicing job with a queue-driven worker pool, shortening month-end billing from 11 hours to 90 minutes.
•Introduced OpenTelemetry tracing across 9 services, which shortened the median time to find a failing dependency during incidents from 40 to 10 minutes.
Software EngineerJul 2018 – May 2020
Meadowlark TicketingBoise, ID
•Rebuilt seat-hold expiry in Python and Redis so on-sale spikes of 20,000 concurrent buyers no longer released seats twice.
•Added contract tests between the box-office app and the inventory service, catching 6 breaking API changes before they reached production.
•Took part in a weekly on-call rotation and wrote 12 incident reviews with follow-up tickets tracked to closure.
Skills
Go •Python •SQL •PostgreSQL •Kafka •Redis •gRPC and REST API design •AWS (ECS, RDS, SQS, Lambda) •Kubernetes •Terraform •OpenTelemetry •Distributed systems design
Open Source and Talks
•Maintainer of readmirror, an open-source Go tool that replays production read queries against a staging database (about 900 GitHub stars).
•Speaker, Portland Go meetup, 2024: "Exactly once is a lie: designing for retries in payment systems."
Education
B.S. in Computer Engineering2014 – 2018
Cascadia State UniversitySalem, OR

Senior capstone: a fault-tolerant sensor network for an irrigation district, written in C and Go.

Keystone resume templateDense and technicalATS-safe · 1 column

What reviewers look for on a software engineer resume

The first read of an engineering resume is fast, and it is mostly a search for evidence that you have built things that run in production. Bullets that describe duties ("responsible for backend services") give a reviewer nothing to find. Bullets that name what you built, what it ran on and what changed afterwards answer the questions before they are asked.

  • The system and its users: what the code did and who depended on it, such as carriers, shoppers, other teams or a data pipeline.
  • The stack, inside the sentence: "in Go and PostgreSQL" tells more than a language appearing only in the skills list.
  • A result someone could check: latency, cost, error rate, adoption, time saved, or the incident that stopped happening.
  • Ownership words that are true: led, designed, owned, migrated. Use "contributed to" when that is what happened; interviewers ask.
  • Production habits: on-call, incident reviews, tests, rollouts behind flags. They separate shipped work from coursework.

Software engineer resume bullets by level

What a bullet has to prove changes as you move up. The examples are fictional and their numbers are placeholders; use your own figures, or describe the change in words when you cannot share one.

LevelWhat the bullet has to proveExample bullet
New grad (internship)You shipped code into a real team's codebaseAdded retry handling to the order-sync job in TypeScript during a summer internship, ending a daily manual rerun by the support team.
New grad (project)You finished something and someone used itBuilt a study-room booking site in Django for a 2,000-member student union, replacing a shared spreadsheet.
Mid-level (feature)You own work from spec to launchOwned the saved-search feature from spec to launch in Kotlin and Postgres; it now accounts for 15% of weekly sessions.
Mid-level (reliability)Your code holds up in productionCut the nightly ETL failure rate from 1 in 5 runs to 1 in 60 by adding schema checks and idempotent writes.
Senior (direction)You set technical direction others adoptWrote and drove the design for queue-based search indexing, adopted by 3 teams and cutting index lag from hours to under a minute.
Senior (people)You make the engineers around you betterStarted the frontend review rotation and mentored 4 engineers, 2 of whom now lead their own projects.
Read your bullets against the middle column for the level you are applying to.

A senior resume that only has mid-level bullets reads as mid-level, however many years it covers. If most of your bullets are about features you built alone, add the design decisions, migrations and mentoring that a senior role expects, provided they happened.

Projects vs experience on a developer resume

Paid work almost always outranks projects, because it shows code that other people relied on. Projects earn a place above experience in three situations: you are a student or new graduate without an internship, you are moving into software from another career or a bootcamp, or a project is clearly more advanced than your current job.

A project is worth listing when it is deployed or published, has users or contributors other than you, or solved a hard problem you can talk about for ten minutes. Tutorial clones and course assignments everyone in your class built rarely help. Merged contributions to an established open-source project count as experience in all but name; list them with the project name and what the change did.

Freelance and contract work goes under Experience as a normal entry with your own business name or "Independent contractor", not under Projects. In ResumeFinch, projects live in a custom section added from the Projects preset, one item per project, and you can drag that section above or below Experience as your career changes.

Tech resume section order by career stage

StageSection orderWhy
Student or new graduateEducation, Experience, Projects, SkillsThe degree and coursework are your most recent full-time commitment.
Career changer or bootcamp graduateSummary, Projects, Skills, Experience, EducationThe summary explains the switch, and projects carry the technical evidence.
One to six yearsSummary (optional), Experience, Skills, Projects, EducationJobs now prove more than projects; keep one or two projects only if they add something.
Senior and staffSummary, Experience, Skills, Open source or talks, EducationScope and direction lead; education shrinks to one line.
Drag sections into any of these orders in the builder; the content stays in place.

Writing the skills section

List what you could be interviewed on tomorrow. A long list of every language you touched once makes reviewers doubt the ones that matter, and a skills section without the posting's main language or cloud provider makes them wonder whether you missed it. Match the posting's spelling ("PostgreSQL" or "Postgres") when you have the skill.

Skip office software, operating systems you use as a consumer, and self-rated proficiency levels. Group related items, either as separate entries (as in the sample) or as labeled groups like "Languages: Go, Python, SQL" if you prefer the Jake's Resume style.

Worked example: the senior backend sample

  • The headline under her name states level and specialty in one line, so a reviewer filtering for backend seniors does not have to read further to know she fits.
  • Each role's first bullet is the largest piece of work in it. The ledger bullet names the language, the database, the volume and a correctness result, which is what a payments team will ask about first.
  • Every senior bullet at Larkspur shows direction or people: a migration across four teams, a design review template, mentoring. The Cobaltline bullets are mid-level work, which is right for that job.
  • Skills sit above Education and the open-source section because, seven years in, tools are what the reader is checking. The degree is one line with a capstone note, enough to answer the question without taking space.
  • Open source and a meetup talk get their own section instead of a Projects list. At this level, a maintained tool and a talk show reputation, which matters more than another side project.

Software engineer CV or resume?

In the US and Canada, a software engineer CV and a software engineer resume are the same document: one or two pages of work history, skills and education. Outside North America, "CV" is the everyday word for that same document, so a posting asking for a CV from a developer usually wants exactly what this page describes. A long academic CV with publications is only expected for research scientist and faculty roles.

ResumeFinch pages are US Letter size only, with no A4 option. A Letter PDF reads normally on screen anywhere; a reviewer printing it on A4 paper may need the printer's fit-to-page setting. Keystone's 10 pt text stays legible if the page is scaled down slightly to fit.

Frequently asked questions

Should a software engineer resume include a GitHub link?

Include it when the profile shows work you would discuss in an interview: pinned repositories with READMEs, real commit history or merged contributions. An empty or coursework-only profile is better left off. Put the link in the website field so it prints in the contact line.

How many projects belong on a developer resume?

Two or three for a student or career changer, each with its stack and one line about users or outcome. With a few years of paid work, one project or none is normal, unless it shows something your jobs do not, such as a widely used open-source library.

Do I need to list every programming language I have used?

No. List the languages you could write in an interview without preparation, then the frameworks and infrastructure you used in the last few years. A language you have not touched since school can go, unless the posting asks for it and you can refresh quickly.

How do I list Engineer II and Senior Engineer at the same company?

Add each title as its own experience entry with its own dates, newest first, and keep the company name identical on both so the promotion is obvious. ResumeFinch does not merge entries for the same employer, so the two entries simply sit one after the other.

Is a summary worth adding to a software developer resume?

For experienced engineers and career changers, yes: two or three sentences that state level, specialty and the kind of systems you build. New graduates can usually skip it, since education and projects already say what a summary would.

Ready to fill in your resume?

Start with Keystone. You can switch templates anytime.

More templates to try

Browse all resume templates

Resume examples by job

Related articles

Related template pages