This software engineer resume template gives you a complete engineering resume as text you can copy, with every date hung in the left margin so a career of any length scans top to bottom. The layout is called Gutter. A4 · 2 pages.
First page of the sample as the Gutter template prints it: Katarzyna Wrzosek, Staff Backend Engineer
What should a software engineer resume include?
A short summary, your roles with results you can measure, selected projects or talks, skills grouped by kind, education and languages. The sample backs almost every bullet with a number: requests per second, latency, incidents or cost.
Lead with the system and the result, then the method: throughput raised "from 9k to 40k requests per second at the same cloud cost".
Show reliability work in the numbers teams track, such as p99 latency or incidents per year.
Name the team and its size on the line under each title, as in "Routing platform, 14 engineers".
Give open source, talks and workshops their own section, with one line on what each covers.
Group skills into languages, platform and practices instead of one long list.
State language levels on the CEFR scale, such as "English: C2".
Software engineer resume example, in full
Katarzyna Wrzosek is a made-up person: the name, employers, schools and contact details are invented to show how the layout reads when it is full. Copy the Markdown, then replace the words with yours.
Katarzyna Wrzosek
Staff Backend Engineer
Berlin, Germany
+49 151 0000 0000
k.wrzosek@mailbox.example
kwrzosek.example
github.com/kwrzosek
Summary
Backend engineer with 12 years of experience building high-volume logistics and payments systems in Go and Kotlin. Leads cross-team designs for routing and pricing services that handle 40k requests per second, and mentors engineers towards senior roles. Looking for a staff or principal role on a platform with hard reliability targets.
Experience
Staff Backend Engineer, Varnstead Freight Mar 2022 – Present
Routing platform, 14 engineers Berlin, Germany
Redesigned the route-pricing service from a shared Postgres monolith into three event-driven Go services, raising peak throughput from 9k to 40k requests per second at the same cloud cost
Cut p99 quote latency from 820 ms to 140 ms by moving rate tables into a read-through cache with versioned invalidation
Led the incident review programme: Sev-1 incidents fell from 11 to 3 a year, and mean time to recovery dropped from 74 to 22 minutes
Wrote the RFC process now used by 9 teams, with 63 design documents reviewed in its first year
Set the platform's service level objectives with product and support, replacing 40 noisy alerts with 12 burn-rate alerts that page only on customer impact
Planned the move of 31 services from a self-managed Kafka cluster to a managed one with no customer-visible downtime, finished two weeks early
Mentored 5 engineers, 3 of them promoted to senior
Senior Software Engineer, Paylark Jun 2018 – Feb 2022
Yes. The margin dates suit any length of career, and a junior resume simply ends sooner. The sample still keeps a part-time junior developer job as its last entry.
How do I tailor it to one job?
Keep this version as your base, make a copy for the posting and move the bullets that match its stack to the top of each role. The step-by-step tailoring guide walks through it.