Engineering
Backend Developer CV: what employers ask for
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.
From real postings
We read 88 Backend Developer job postings from 39 companies on 6 November 2026. The most named asks were Distributed systems (44), Monitoring / observability (40) and Java (37). 56 postings stated years of experience; the middle value was 5.
One-time analysis • $2.99 • No subscription
What a strong Backend Developer CV looks like
Start here if you are editing a CV today. The evidence for each point follows below.
Section order, top to bottom
- HeaderName, email, phone, city, and a link only if it shows backend work you can discuss.
- SummaryTwo or three lines: your title, years of experience, your language, and the scale of the systems you run.
- ExperienceMost recent first. Bullets about services you built or ran: traffic, data size, latency, uptime, incidents.
- SkillsGrouped: languages, frameworks, databases, messaging, cloud. Keep only what you have used in production.
- ProjectsUseful early on: one service with an API, a database, tests and deployment.
- EducationDegree and year, kept short.
The summary
Lead with your language and the scale you work at. About half the postings we read mentioned distributed systems, so if you have run services that talk to each other under load, say so here.
Backend developer with six years of experience in Java and Kotlin. I build and run payment services handling thousands of requests per second, with PostgreSQL and Kafka on AWS.
Skills: show them, do not just list them
Java and Python were named equally often in our sample, with Go close behind. Distributed systems, monitoring and cloud came up more than any database. Show each through a service you built or kept running, with numbers about load or reliability.
Weak and strong bullets
Illustrative rewrites, 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.
Why it works: Language, framework, load and uptime together. Those are what backend reviewers scan for.
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.
Why it works: Says exactly what changed in the database and what it saved.
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.
Why it works: On-call and incident work show you ran the system, not only wrote it.
What Backend Developer job postings ask for
Counted from 88 real postings, not guessed. When you paste a posting into Resymetry, it checks each of these asks against your CV and marks it as shown, only listed, or missing.
| Skill or ask | Postings naming it | Only as nice to have |
|---|---|---|
| Distributed systems | 44 of 88 | 2 |
| Monitoring / observability | 40 of 88 | 3 |
| Java | 37 of 88 | 4 |
| Python | 37 of 88 | 6 |
| Cross-functional work | 36 of 88 | 4 |
| AWS | 29 of 88 | 6 |
| Go | 29 of 88 | 5 |
| Kubernetes | 21 of 88 | 5 |
| Stakeholder management | 20 of 88 | 3 |
| Machine learning | 19 of 88 | 2 |
Show 8 more
| Skill or ask | Postings naming it | Only as nice to have |
|---|---|---|
| System design | 19 of 88 | – |
| PostgreSQL | 17 of 88 | 1 |
| Roadmap | 16 of 88 | – |
| CI/CD | 15 of 88 | 1 |
| GCP | 15 of 88 | 3 |
| Kafka | 15 of 88 | 3 |
| Data modelling | 14 of 88 | – |
| SQL | 14 of 88 | – |
How we counted
On 6 November 2026 we read 88 live Backend Developer postings from 39 companies, through their public job boards (Greenhouse, Lever and Ashby). A posting counted when its title matched the role. We took at most three per company, so no single employer sets the result.
A skill counts once per posting, when it is named outside the benefits and company boilerplate. Matching is by keyword, so read the numbers as “named in”, not “strictly required”. “Only as nice to have” means it appeared only under a heading such as “Nice to have” or “Bonus”. 40 of the 88 postings had such a heading, so that column is a floor.
By location on the posting: 40 US, 13 UK, 11 India, 24 elsewhere or remote. Most employers in the sample are technology companies, which skews the result towards their stacks.
Companies sampled: Affirm, Airbnb, Anduril, Asana, Brex, Cohere, Coinbase, Databricks, Deliveroo, Dropbox, Duolingo, ElevenLabs, Fivetran, GitLab, HackerRank, InMobi, Lyft, Modal, Monzo, Okta, OpenAI, Oscar Health, Outreach, Paytm, Perplexity, Ramp, Reddit, Robinhood, Roblox, SoFi, SpaceX, Spotify, Squarespace, Stripe, Toast, Vanta, Vercel, Wealthfront, Zscaler.
The script that produced these numbers is scripts/role-postings.mjs in the Resymetry repository. It stores counts only, never the text of a posting.
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.
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.
Starting from scratch, or the layout is the problem rather than the content? There are free ATS CV templates to start from.
Know your chances for Backend Developer roles
Your score and your biggest problems are free. The full report is a one-time $2.99.
Backend Developer CV questions
- 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.