Backend engineer resume: a LaTeX example and how to write yours

Backend hiring managers read for three things: what you built, how much load it carried, and what got better because of you. A good backend resume makes those easy to find in a few seconds, with the stack named where the work happened rather than only in a skills list.

Start from this resumeTailor mine to a job

Free PDF download, no signup. The sample is a made-up person; replace every line with your own.

A sample backend engineer resume in Jake's Resume.

What recruiters look for

Systems you owned
Services, APIs, queues and databases you designed or rebuilt, not just tickets you closed.
Scale and numbers
Requests per day, latency, error rates, cost. One number per bullet is plenty.
Reliability work
Monitoring, on-call fixes, migrations without downtime, idempotency, retries.
The stack, in context
Go, Java, Node.js, PostgreSQL, Kafka named inside bullets, so a reader sees where you used them.

Weak bullets, and stronger ones

Worked on the payments API and improved performance.

Cut p95 latency of the payments API from 420 ms to 180 ms by adding Redis caching and fixing N+1 queries in PostgreSQL.

→ Names the system, the result with numbers, and the tools that did it.

Responsible for migrating jobs to a queue.

Moved 14 cron jobs onto event-driven processing with Kafka, removing nightly failures and saving ₹3.1L a month in compute.

→ Uses the words job posts use (event-driven, Kafka) for work you really did.

Helped with database design.

Designed the PostgreSQL schema for settlements, with idempotent writes that handle 1.2M transactions a day.

→ Shows ownership and scale instead of help.

Words backend engineer job posts use

Use the ones that are true for you, inside your bullets as well as in Skills.

  • REST APIs
  • microservices
  • PostgreSQL
  • Redis
  • Kafka
  • message queues
  • event-driven
  • Docker
  • Kubernetes
  • AWS
  • system design
  • observability
  • Go
  • Java
  • Node.js

Every job post is different. Check your resume against the exact post to see which of its must-haves your resume shows.

Tips

  1. 01Lead each bullet with the result, then how: "Cut X by Y% by doing Z".
  2. 02Put the stack inside bullets. A skills list alone counts for little with readers and screening software.
  3. 03Under 5 years of experience, keep it to one page: cut older, weaker bullets first.

Questions

Should a backend resume have a projects section?

Yes if you have under about 3 years of work experience, or a project shows something your jobs don't (an open-source library, a system at real scale). Otherwise experience matters more.

Do I need to list every language I know?

No. List what you could be interviewed on, and make sure the important ones also appear in your bullets.

Other resume examples

All of them use Jake's Resume, the one-page LaTeX template engineers share on Overleaf. Once yours is ready, tailor it to each job.