Senior Backend Engineer résumé example, in the Plainsong design
Eight years of distributed systems work, told through what each system did for the business rather than what it was built with.
Written for United States, at senior, in the software field, shown in the Plainsong design. Every name, employer, address and number below is invented.
Backend engineer with eight years on payment and messaging systems that cannot go down. Took a checkout service from 1.2% failed transactions to 0.08%, and now leads the three-person group that owns it.
Experience
Senior Backend Engineer, Northbank Payments · March 2022 – present
Payments platform group of nine. Owns authorization, settlement and the merchant ledger.
Rebuilt the authorization path around an idempotency ledger, taking failed transactions from 1.2% to 0.08% and ending a class of duplicate-charge refunds worth about $340k a year.
Cut p99 settlement latency from 2.4s to 310ms by replacing nightly batch reconciliation with an event-sourced ledger in Go.
Led the migration of 40 services to a shared gRPC contract, retiring 11k lines of per-service HTTP glue.
Wrote the on-call runbook the team still uses; paging volume fell by half in the quarter after it landed.
Backend Engineer, Cedarline Systems · June 2019 – February 2022
Designed the message bus behind a fleet-tracking product serving 18,000 vehicles, sustaining 90k events a minute on three nodes.
Moved the deploy pipeline from hand-run scripts to GitOps, taking a release from 40 minutes of supervision to four.
Found and fixed a connection-pool leak that had caused six months of Monday-morning outages.
Software Engineer, Aperture Retail · August 2017 – May 2019
Built the inventory sync between five warehouses and the storefront, cutting oversold orders by 71%.
Added the integration test suite the team had gone two years without; it caught 23 regressions in its first quarter.
Projects
Ledgerkit — An open-source double-entry ledger for Go, used by four payment startups.
Education
B.S. Computer Science · University of Colorado Boulder · August 2013 – May 2017
The summary leads with a single reliability result, failed transactions “from 1.2% to 0.08%”, and the bullet behind it adds the money: about $340k a year of duplicate-charge refunds ended.
Latency is given with the percentile and both values, p99 settlement “from 2.4s to 310ms”, the level of precision a senior engineer can be asked to defend in an interview.
Ledgerkit sits under projects with 1,400 stars and 31 contributors, giving outside evidence of the Go and event sourcing skills claimed in the skills list.
Operational work counts here: the on-call runbook that halved paging volume and the connection-pool leak behind six months of Monday-morning outages show ownership beyond feature work.
Senior Backend Engineer résumé: common questions
How long should a senior software engineer resume be?
One page works up to about ten years; two pages are fine beyond that when each role has measurable results. Cut early roles to two bullets and drop coursework entirely.
Should a backend engineer resume link to GitHub?
Yes, if it holds work you would discuss in an interview, such as a maintained open-source project. Link it in the header and list the project with a usage measure, like stars, contributors or adopters.
What skills should a senior backend engineer resume list?
Languages (Go, Python, SQL), systems (Kubernetes, Kafka, PostgreSQL, gRPC) and practices such as event sourcing or incident review. Keep it to what you have run in production, and use the job post’s wording.
