What should a backend developer put on a resume?

The services and data systems you built or owned, with the language and data store named, the scale they ran at, and one result per bullet: latency, throughput, uptime, cost or delivery speed.

How do I show backend impact without access to metrics?

Use what you remember and can defend: the number of services, users or records involved, the before/after time of a job you sped up, incidents prevented, or manual work removed. Estimates are fine if you can explain them in an interview.

Should I list every database I've touched?

No. List the ones you could design a schema in or debug in production. A long list of tools you used once makes the strong ones harder to see.

What projects should I put on a backend developer resume?

Projects that show an API or service under real conditions: authentication, a database with migrations, background jobs, tests and a deployment. Name the stack and any load or latency numbers you measured.

Should a Node.js, Java or Python backend resume look different?

The structure is the same. Change the stack you lead with to match the post, and use that language's ecosystem terms (Express or NestJS, Spring Boot, Django or FastAPI) in your bullets.

How to write a backend developer resume

By Mubeen Jawed, founder of ResumeForDev · Updated November 7, 2026

Short answer

A backend developer resume (or backend engineer resume) should show the systems you built or owned and how they behaved under load: requests per second, latency, uptime, data volume, cost. Each bullet should name the service, the language and data store (Go and PostgreSQL, Python and Redis) and one number that shows scale or improvement. Put the languages, databases, cloud and infrastructure tools in a grouped skills section, and make sure each one also appears in a bullet.

Key points

Scale and reliability are the backend metrics: RPS, p95 latency, uptime, data volume.
Name the language and the data store in the bullet.
Show design decisions (caching, queues, schema changes), not only endpoints shipped.
Cost savings and incident reduction count as results.

What backend hiring managers look for

Backend reviewers want proof you can build services that stay up, stay fast and stay correct as traffic grows. They read for scale (how much traffic, how much data), judgement (why you chose a queue, a cache or a schema change) and ownership (did you run it in production, carry the pager, fix the incident).

Before and after

Before:Built REST APIs for the mobile app using Node.js.

After:Designed and built the order API in Node.js and PostgreSQL serving ~1,200 requests/second at peak, adding Redis caching that cut p95 latency from 480ms to 110ms.

Same work. The second names the service, the stack, the load and the measured improvement.

Backend metrics worth looking up

Where to find numbers for backend bullets
Metric	Where to find it	Example phrasing
Throughput	APM, load balancer or gateway metrics	~1,200 requests/second at peak
Latency	APM dashboards (p50, p95, p99)	cut p95 latency from 480ms to 110ms
Data volume	Database size, event counts	processing 40M events/day
Reliability	Uptime/SLO dashboards, incident log	raised availability from 99.5% to 99.95%
Cost	Cloud billing	cut monthly database spend ~30%
Delivery	CI history	reduced deploy time from 25 to 6 minutes

Example backend bullets

Split a slow synchronous checkout path into a queue-backed worker (SQS and Python), removing timeouts during sales events that peaked at 5x normal traffic.
Redesigned the PostgreSQL schema and indexes for the reporting service, cutting the heaviest query from 9s to 300ms.
Built the authentication service (Go, JWT, OAuth 2.0) used by 6 internal services and ~80k users.
Added structured logging, tracing and alerts to the payments API, cutting mean time to detect incidents from ~40 minutes to 5.
Migrated 14 cron jobs into an Airflow pipeline with retries and alerting, ending the weekly manual re-runs.

The skills section for backend roles

Backend job posts usually filter on a language (Java, Go, Python, Node.js), databases (PostgreSQL, MySQL, MongoDB, Redis), API styles (REST, GraphQL, gRPC) and the deployment stack (Docker, Kubernetes, AWS or GCP, CI/CD). List what you've used in production first.

Languages: Go, Python, TypeScript, SQL
Data: PostgreSQL, Redis, Kafka, Elasticsearch
Infrastructure: Docker, Kubernetes, AWS (ECS, RDS, SQS), Terraform
Practices: REST, gRPC, CI/CD, observability (OpenTelemetry, Grafana)

On ResumeForDev, set your target role to “Backend Engineer”. Without a job post, the keyword check compares your resume against a backend vocabulary. Paste a job description and the keyword check uses that post's terms instead; on Pro, the writer also tailors the bullets to it. Before writing, it asks follow-up questions about the numbers above, and it removes any number or skill you never gave it. Your first resume is free.

Frequently asked questions

What should a backend developer put on a resume?: The services and data systems you built or owned, with the language and data store named, the scale they ran at, and one result per bullet: latency, throughput, uptime, cost or delivery speed.
How do I show backend impact without access to metrics?: Use what you remember and can defend: the number of services, users or records involved, the before/after time of a job you sped up, incidents prevented, or manual work removed. Estimates are fine if you can explain them in an interview.
Should I list every database I've touched?: No. List the ones you could design a schema in or debug in production. A long list of tools you used once makes the strong ones harder to see.
What projects should I put on a backend developer resume?: Projects that show an API or service under real conditions: authentication, a database with migrations, background jobs, tests and a deployment. Name the stack and any load or latency numbers you measured.
Should a Node.js, Java or Python backend resume look different?: The structure is the same. Change the stack you lead with to match the post, and use that language's ecosystem terms (Express or NestJS, Spring Boot, Django or FastAPI) in your bullets.