Engineering

Backend Developer Resume Example (2026)

Backend developer resumes win on throughput, reliability, and database fluency — not framework lists. The example below leads every bullet with a load metric or a latency cut, then earns the framework name by showing how it was used in production.

Check my backend developer resume See Backend Developer keywords

Sample resume

Backend Developer resume — full example

One-column, ATS-friendly layout. Names and numbers are illustrative.

Marcus Rivera

New York, NY · marcus.rivera@example.com · linkedin.com/in/marcusrivera · github.com/mrivera

Senior Backend Engineer

Professional Summary

Senior backend engineer with 6 years owning production services at a Series B fintech. Designed and shipped the company's payments ledger (8B+ rows, 99.99% read availability) and the API platform that 14 internal teams build on. Strongest at high-throughput Go and Python services, Postgres performance work, and event-driven architectures over Kafka.

Technical Skills

Languages: Go, Python, TypeScript, SQL, Bash
Frameworks: FastAPI, Django, gRPC, Gin, Echo
Data: PostgreSQL (replication, partitioning, query tuning), Redis, Kafka, Elasticsearch, DynamoDB
Infrastructure: AWS (EC2, RDS, SQS, S3, Lambda), Docker, Terraform, GitHub Actions
Practices: REST, gRPC, OpenAPI, Event-driven architecture, CI/CD, OpenTelemetry

Professional Experience

Senior Backend Engineer — Settle Pay

New York, NY · Apr 2023 — Present

Designed and shipped the company's payments ledger service in Go (Postgres + Kafka outbox); processed $4.2B of throughput in the first year with zero double-debit incidents on the partitioned 8B-row hot table.
Cut p99 API latency on the merchant gateway from 412ms to 138ms (-66%) by introducing a read-replica plan with PgBouncer + a hand-written query rewriter for the slowest 40 endpoints.
Owned the migration of 6 services from REST to gRPC; reduced inter-service payload size 71% and eliminated three classes of contract-drift bugs that had bitten the team in 2024.
Authored the company's API design guide (RESTful conventions, error envelope, pagination, idempotency keys); adopted by all 14 backend teams within four months.

Backend Engineer — Northgate Logistics

Remote · Jun 2020 — Mar 2023

Built the partner-facing webhook delivery system in Python (FastAPI + Celery + Redis); sustained 99.95% delivery rate at 1.2M events/day with exactly-once semantics via dedup keys.
Reduced AWS RDS spend $180K/year by introducing read replicas, query-result caching in Redis, and a kill-it-with-fire pass on N+1 ORM queries surfaced via slow-query logging.
Mentored 3 mid-level engineers; instituted a weekly engineering reading group that became the team's main inflection point per the eng retrospective.

Education

B.S. Computer Engineering — Rutgers University · 2020

Certifications

• AWS Certified Developer — Associate (2023)

Why this resume works

Bullets lead with the production metric (throughput, latency, spend) before the technology. The keyword engine credits the technology mention; the human reviewer credits the impact framing.
Database experience is named at the level of techniques (replication, partitioning, query tuning) — not just 'PostgreSQL'. JDs that specify those terms get exact matches.
REST + gRPC + OpenAPI + event-driven appear together — modern backend JDs typically name two or three of these. The implicit-match layer credits all of them when the resume names any one in context.
AWS sub-services are named explicitly (EC2, RDS, SQS, S3, Lambda) so JDs asking for 'AWS RDS experience' get a literal keyword hit, not just an implicit one.

Common mistakes

Listing 'REST APIs' as a single bullet without naming the throughput, latency, or number of endpoints. The Impact layer punishes vague bullets.
Saying 'experience with PostgreSQL' instead of naming a specific technique you used (partitioning, replication, indexing strategy). The latter scores higher and tells the interviewer what to dig into.
Listing only one cloud's sub-services. Many JDs require 'AWS or GCP' — having one with sub-services + at least mentioning the other improves the implicit match.
Burying the company size or transaction volume. '8B rows', '1.2M events/day', '$4.2B throughput' are the bullets recruiters circle.

ATS keywords

Backend Developer resume keywords ATS systems scan for

A condensed view. For the full categorized list, see the Backend Developer keywords page.

Hard skills

Backend development
REST APIs
GraphQL
gRPC
Microservices
Event-driven architecture
Distributed systems
Database design
Query optimization
Indexing strategy
Replication
Partitioning

Tools

Go
Python
Java
TypeScript
Node.js
FastAPI
Django
Flask
Express
Spring Boot
gRPC
PostgreSQL

Action verbs

Designed
Built
Owned
Shipped
Migrated
Refactored
Optimized
Reduced
Scaled
Implemented
Architected
Profiled

Soft skills

API design
Code review
Documentation
Mentorship
Cross-team collaboration
Technical writing
Pair programming
Estimation

See the full Backend Developer keyword list

Questions

Backend Developer resume — frequently asked

Should I list every database I've used?+

List the two or three you've used in production for substantive work — and name a technique you applied (partitioning, indexing, query tuning) for at least one of them. A long list with no specifics reads as resume-padding.

How do I describe API work without sounding generic?+

Anchor every bullet to a number: number of endpoints, requests per second, latency cut, payload size reduction, or downstream consumers. 'Built RESTful APIs' is buzzword-tier; 'cut p99 latency from 412ms to 138ms across 40 endpoints' is the version that scores.

REST or gRPC — which should I emphasize?+

Both, if you have both. Modern senior backend JDs typically ask for fluency in REST and at least exposure to gRPC. Name the protocol the JD names first; mention the other in skills.

Are open-source contributions worth listing?+

Yes if they're substantial (merged PRs to a project the interviewer will recognize, or a project of yours with real users). Single-commit toy repos hurt more than they help.

Related roles

Other examples you might want

Software Engineer resume example

View →

DevOps Engineer resume example

View →

Cloud Engineer resume example

View →

See how your backend developer resume actually scores.

Get the six-layer breakdown in under 30 seconds. No account, no credit card.

Run a free screen