What should a backend developer CV focus on?

The services you built and ran, the data they handled, and how you kept them fast and reliable. Frameworks matter less than the problems you solved with them.

How do I describe scale if my company was small?

Use honest figures, even modest ones, and add context such as data size, number of integrations or the number of customers who depended on the service.

Should I mention on-call experience?

Yes. It shows you owned production systems. Pair it with one example of an issue you diagnosed or prevented.

Engineering

Backend Developer CV: what gets you shortlisted

Backend screeners want to see systems, not syntax. The strongest CVs explain which services you built, how they handled load and failure, and how you worked with data. Without that, a backend CV looks like a list of frameworks.

Get my free score

One-time analysis • $1.99 • No subscription

What employers look for in a Backend Developer CV

Screeners check these first. Each one should be visible in your job entries, not only in a skills list.

APIs and services you designed and ran in production, with the language and framework named.
Database work: schema design, query tuning, migrations and knowing when to use which store.
Reliability habits such as monitoring, alerting, incident response and post-incident fixes.
Handling scale or load: caching, queues, background jobs and concurrency.
Security basics like authentication, authorisation and handling sensitive data.

Skills Backend Developer postings often ask for

Listing a skill is not the same as showing it. Resymetry counts a skill as matched only where your CV shows you used it.

Java
Python
Go
Node.js
PostgreSQL
MySQL
Redis
Kafka or RabbitMQ
REST APIs
gRPC
Docker
Observability

4 common Backend Developer CV mistakes and how to fix them

Naming databases without saying what you did with them.
Fix: Mention schema design, a slow query you fixed or a migration you led.
No mention of production operation.
Fix: Show that you ran what you built: on-call, dashboards, alerts or incident fixes.
Vague scale such as "high-traffic systems".
Fix: Give a real figure: requests per second, rows, events per day or number of clients.
Every bullet starts with "Developed" or "Implemented".
Fix: Start with the outcome, then say how you achieved it.

Weak and strong CV bullets

Illustrative examples, not real candidates. Use your own work and only numbers you can back up.

Weak: Developed REST APIs.
Stronger: Designed the pricing API in Java and Spring Boot, handling about 1,500 requests per second at peak with 99.95% monthly uptime.
Weak: Worked with PostgreSQL.
Stronger: Rewrote the reporting queries and added two indexes in PostgreSQL, cutting nightly job time from 3 hours to 25 minutes.
Weak: Participated in on-call.
Stronger: Joined the on-call rotation and led the fix for a queue backlog incident, adding alerts that caught the next two early.

Know your chances for Backend Developer roles

Your score and your biggest problems are free. The full report is a one-time $1.99.