Technology · Senior
Backend Developer Resume Example
A resume for a senior backend developer with over ten years of experience, set in telecoms messaging. It shows how to express scale and reliability in real units, how to make design ownership and mentoring visible, and how to compress early roles so the page stays focused on recent work.
The example resume
Laid out in the Docket template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.
Tomasz Wieczorek
Senior Backend Developer
- tomasz.wieczorek@example.com
- +1 555 0168
- Kraków, Poland
- linkedin.example.com/in/tomasz-wieczorek
Professional summary
Senior backend developer with 12 years of experience designing APIs and high-volume messaging systems for telecoms. Works mainly in Go and PostgreSQL, with Kafka for event streaming. Led the design of an SMS delivery platform that carries 45 million messages a day at 99.98% availability, and mentors a team of five.
Work experience
Senior Backend Developer
Baltic Relay Telecom, Kraków
Apr 2020 – Present
- Designed the SMS delivery platform in Go: 14 services and a versioned REST and gRPC API carrying 45 million messages a day for 210 business customers
- Partitioned the 2 TB message log table in PostgreSQL by day and moved cold data to object storage, bringing p99 query time from 1.9 s to 140 ms
- Replaced a RabbitMQ work queue with Kafka and consumer-side idempotency keys, ending duplicate deliveries during carrier retries
- Agreed service level objectives with operations and added circuit breakers and backpressure for peaks of 3,200 messages a second, raising availability from 99.9% to 99.98%
- Mentored 5 developers and ran the weekly design review for the messaging group
Backend Developer
Orzel Mobile Services, Kraków
Jun 2016 – Mar 2020
- Built the number porting and SIM activation APIs in Java and Spring Boot, processing 25,000 requests a day from retail systems
- Reduced the billing export run time from 5 hours to 50 minutes by batching writes and adding 3 covering indexes
- Introduced Flyway database migrations and zero-downtime deployment steps, ending the monthly maintenance window
- Led the on-call rota for 6 engineers and cut pages from 14 a week to 4 by removing noisy alerts
Junior Developer
Planty Software House, Kraków
Sep 2014 – May 2016
- Developed PHP and MySQL back ends for 6 client web applications, including a ticket booking system used at 3 venues
- Wrote the company's first API integration tests, run automatically on every merge
Skills
Languages: Go, Java, SQL, Python
Data: PostgreSQL (partitioning, replication, query tuning), Redis, ClickHouse
Messaging and APIs: Kafka, RabbitMQ, gRPC, REST, OpenAPI
Reliability: SLOs, load testing with k6, distributed tracing, circuit breakers, capacity planning
Platform: Kubernetes, Docker, Prometheus, Grafana, GitLab CI
Talks and open source
Idempotent consumers in practice: what "exactly once" really means
Talk at Vistula Backend Meetup
2024
Connection pool fixes for an open-source Go PostgreSQL driver
Contributor, 4 merged pull requests
2023
Education
MSc Computer Science
Wawel Hill University of Technology, Kraków
2009 – 2014
Open this example in the resume builder Start empty with this template
Why this resume works
- Scale is stated in the units backend engineers use: messages a day, peak messages a second, table size in terabytes and availability to two decimal places.
- Each reliability claim has a mechanism attached (partitioning, idempotency keys, circuit breakers, backpressure), so the reader can see how the 99.98% figure was reached.
- Seniority shows through design ownership, objectives agreed with operations, the weekly design review and mentoring, without the word "senior" having to do the work.
- The oldest role is cut to two bullets, which keeps a 12-year career on one page while still showing where it started.
- The first bullet mentions a versioned API and the 210 business customers who integrate with it, which shows awareness that a backend's users are other developers.
What employers look for in this role
- Design and build APIs and services that other systems depend on
- Model data and tune queries, indexes and schemas for growth
- Build asynchronous processing with queues and event streams
- Define and meet availability and latency targets
- Plan capacity and run load tests before peak periods
- Lead design reviews and mentor other developers
- Share on-call duty and write post-incident reviews
Skills to consider
List only the skills you can back up with an example. These are the ones that come up most for this kind of role.
- APIs and services
- REST and gRPC design, API versioning and OpenAPI, Authentication and rate limiting, Idempotency and retries, One or two server languages in depth (Go, Java, C#, Python or Node.js)
- Data and messaging
- PostgreSQL or MySQL internals, Indexing and query plans, Partitioning and replication, Redis or Memcached, Kafka, RabbitMQ or SQS, Schema migrations without downtime
- Reliability and scale
- Service level objectives, Load and capacity testing, Distributed tracing, Circuit breakers and backpressure, Incident response, Cost-aware design
More bullet points to adapt
Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.
- Added cursor-based pagination to 12 list endpoints, removing timeouts on accounts with more than a million records
- Split a database shared by 5 services into per-service schemas over 9 months, with dual writes and verification at each step
- Introduced per-customer rate limiting with a token bucket in Redis, protecting the platform from a single client's retry storm
- Wrote a k6 load test reproducing a seasonal peak at twice the expected volume and fixed the 3 bottlenecks it exposed before the event
- Cut database CPU use by 40% by rewriting 6 queries identified from the slow query log and adding 2 partial indexes
- Led the review of a 3-hour outage, traced it to connection pool exhaustion and delivered the 4 follow-up actions within a month
Words that recur in adverts
These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.
Which sections to include
At senior level the summary should state scale and scope in one line, because that is how backend roles are sized. Experience follows and should be weighted heavily towards the last five to eight years; early roles can shrink to a line or two. Skills come next, grouped by data, messaging and reliability so that depth is visible. A short section for talks, published articles or open-source work makes a good fourth section for a senior developer. Education sits at the bottom. If the page overflows, cut old technology from the skills list before you cut results from recent bullets.
Mistakes to avoid
- Describing endpoints built ("created CRUD APIs for orders") with no sign of the volume, latency or failure handling that distinguish senior backend work.
- Quoting uptime with no period or definition; "99.98% availability over 12 months against an agreed objective" can be discussed, "five nines" usually cannot.
- Giving every job equal space, so a PHP agency role from ten years ago takes as much room as the platform you designed last year.
- Claiming a system "scales to millions of users" when it has only been load tested, or never measured; give the traffic it actually carried.
- Leaving out data work such as schema design, migrations, indexing and partitioning, even though it is often the hardest part of the job and the part interviewers probe.
Questions and answers
How do I show seniority on a backend resume?
Through scope and judgement more than the job title. Show what you designed, the trade-offs you chose, the targets you agreed and met, and the people you reviewed or mentored. A bullet about ending a maintenance window with zero-downtime migrations says more than "senior-level expertise in databases".
Should I include every technology from a long career?
No. List what you would be happy to use again and what the advert asks for. Older technology can appear inside the bullet for the job where you used it, which keeps the record honest without making the skills list look dated.
What if my systems are small in scale?
Give the real numbers and emphasise correctness, reliability and design quality instead. A billing system for 300 customers where errors are expensive is serious backend work. Inflated figures tend to fall apart in a system design interview; the guide to technical interviews explains what those sessions probe.
Is a two-page resume acceptable for a senior backend developer?
Often yes, and conventions differ between countries. One page is still achievable for most careers if older roles are compressed. If you do use two pages, make sure the first one alone shows your current scope and best results.