Backend developer CV example with API, database and scale lines
A backend developer CV should show the systems you built, the load they carried, the APIs and data stores you designed, and how you measured reliability. Put that evidence inside each role, not in a long tool list.1
Written 13 October 2026. CitedCV. How we write our guides
Start with one system you can explain end to end
Pick the service you know best from your current or last job and write five facts about it on a scratch page: what it does for a user, how much traffic or data it handles, which language and data store it runs on, which part you designed or changed, and one number from before and after your change. If you cannot fill all five, choose a different system. A backend interview usually goes deep on one design, so the CV should lead with the one you can defend.
Where the numbers usually live
- Monitoring dashboards: request rate, error rate and latency percentiles for the endpoints you own.
- Load-test reports and capacity plans, which often state the target throughput.
- Postmortems and incident tickets, for recovery times and the fix you shipped.
- Pull request descriptions and migration plans, for row counts, table sizes and query timings.
- Cloud or hosting invoices, if you reduced cost.
Copy the number with its unit and its time window. "1,200 requests per second at the daily peak" is a fact; "high traffic" is not.
What the official job profiles put first
O*NET OnLine files backend work under Software Developers (15-1252.00). Its task list starts with analysing user needs and software requirements within time and cost constraints, and includes modifying existing software to fix errors, adapt it or improve performance. Its technology list, drawn from employer job postings, marks PostgreSQL as in demand among databases and names Redis, Amazon DynamoDB and Oracle PL/SQL; Spring Boot among frameworks; and Apache Kafka, Git and Jenkins among other tools.
The US Bureau of Labor Statistics adds that some applications developers create databases or programs for internal or online use, and that most developers hold a bachelor's degree in computer and information technology or a related field. The UK National Careers Service profile lists writing and updating code, testing at each stage, recording changes with reasons, and maintaining systems once they are running.
| What a reviewer looks for | What proves it on a CV | Where it goes |
|---|---|---|
| A data store you understand, not just one you used | Schema, index or partition decision with a timing before and after | A bullet under the role |
| APIs other teams depend on | Number of consumers, call volume, versioning or contract tests | A bullet under the role |
| Behaviour under load | Throughput and a latency percentile at a stated load | The first bullet of your strongest role |
| Production ownership | On-call rota, incidents handled, postmortems written | One bullet per role at most |
| Stack | Language versions, frameworks, queues, caches | A short skills block after experience |
No licence to show
Neither the O*NET profile nor the National Careers Service profile for software developers lists a licence or registration. Compare the National Careers Service profile for IT security roles, which says you will need to pass enhanced background checks. For backend work the proof is the code and the systems, so the experience section carries the weight.
Scale numbers that hold up in an interview
Google's Site Reliability Engineering book explains why averages hide the slow requests: most metrics are better thought of as distributions, and a high percentile such as the 99th shows a plausible worst case. It defines a service level indicator as a measured quantity, a service level objective as the target for it, and an agreement as the contract with consequences. Use the same words on your CV and an interviewer who runs production systems will read them the way you meant.
| Vague line | Line with a checkable number (illustrative) |
|---|---|
| Improved API performance | Cut p99 latency of GET /orders from 640 ms to 180 ms at 1,200 requests per second |
| Worked with large databases | Partitioned a 120-million-row PostgreSQL table by month; nightly report query fell from 38 s to 2.1 s |
| Ensured high availability | Kept the payments API inside its 99.9% monthly availability objective for 11 of 12 months |
| Built microservices | Split settlement batch into 4 Kafka consumers; run time fell from 5 hours to 40 minutes |
Four rules for the numbers
- Name the percentile and the load: "p95 at 800 requests per second", never just "fast".
- Give the time window for volumes: per second, per day or per month.
- Say whose number it is: your service, your team, or the whole platform.
- Keep a source for each one, such as a dashboard export or a ticket, in case a reference check asks.
Example: experience and skills for a backend developer
Example only. Deniz Arslan and both employers are invented; the numbers show the form a line can take, not targets to copy.
Senior Backend Developer, a payments company, Istanbul, 03/2023 to present
- Designed the refund API (REST, OpenAPI 3.1) used by 4 internal services and 2 partner banks; about 1.8 million calls a month.
- Moved order reads from the PostgreSQL primary to 2 read replicas behind a Redis cache; p99 latency of GET /orders fell from 640 ms to 180 ms at 1,200 requests per second.
- Replaced a nightly settlement batch with 4 Kafka consumers; settlement now finishes in 40 minutes instead of 5 hours.
- Added object-level authorization tests to 14 endpoints after an internal review against OWASP API1:2023.
- On call one week in six; wrote 9 postmortems, 2 of which led to schema changes.
Backend Developer, an online marketplace, 07/2020 to 02/2023
- Built the seller inventory service in Java 17 and Spring Boot; 120 million rows in PostgreSQL, partitioned by month.
- Rewrote a report query with a composite index and a narrower join, checked with EXPLAIN ANALYZE: 38 s to 2.1 s.
- Introduced contract tests on 3 public endpoints after field renames broke two mobile releases.
Skills table for the same CV
| Area | Listed as | The line that backs it |
|---|---|---|
| Languages | Java 17, Kotlin, SQL | Inventory service; report query rewrite |
| Data stores | PostgreSQL (partitioning, replicas), Redis | Read replicas and cache; monthly partitions |
| Messaging | Apache Kafka | Settlement consumers |
| API design | REST, OpenAPI 3.1, contract testing | Refund API; contract tests |
| Security | Authorization testing (OWASP API Top 10) | Object-level authorization tests |
| Operations | Docker, Kubernetes, Grafana, on-call | On-call rota and postmortems |
Every entry in the middle column points to a bullet above it. A skill with no line behind it is the first thing a technical interviewer will probe.
API and security lines reviewers recognise
The OWASP API Security Top 10, 2023 edition, gives backend teams a shared vocabulary. Its first item is Broken Object Level Authorization (API1:2023); others include Broken Authentication (API2), Unrestricted Resource Consumption (API4), Server Side Request Forgery (API7) and Unsafe Consumption of APIs (API10). Naming the item you fixed tells a reviewer exactly what kind of bug it was.
- Rate limits or quotas you added, and the abuse they stopped (API4).
- Authorization checks moved from the client into the service (API1, API5).
- Outbound calls you restricted to an allow-list (API7).
- An inventory of old API versions you retired (API9).
Versioning and contracts
If other teams call your API, say how many and how you kept them working: a deprecation window, a version header, or contract tests in the pipeline. This is the backend equivalent of a portfolio link, because it shows other people relied on your design.
Certificates are optional here
No certificate is required to work as a backend developer, and the profiles above do not ask for one. A cloud developer certificate can still help when a posting names that cloud. AWS lists its Certified Developer, Associate exam at 150 USD, 130 minutes and 65 questions, valid for 3 years. On 13 October 2026 its page said the current DVA-C02 exam has its final day on 30 November 2026 and that registration for DVA-C03 opens on 27 October 2026.
Write the certificate under its own heading with the month earned and the expiry month. Cloud certificates for operations and platform roles are covered on the DevOps engineer page.
Proof: sources and the date we read them
Every claim on this page comes from one of these pages, all read on 13 October 2026. Links are under Sources.
| Claim | Source |
|---|---|
| Tasks and in-demand technologies for software developers | O*NET OnLine, 15-1252.00 |
| Some developers create databases; usual degree | BLS Occupational Outlook Handbook, last modified 27 August 2026 |
| UK duties; no licence listed | National Careers Service, Software developer |
| Enhanced background checks for IT security roles | National Careers Service, IT security co-ordinator |
| Percentiles over averages; SLI, SLO and SLA | Google, Site Reliability Engineering, chapter 4 |
| API risk names and codes | OWASP API Security Top 10, 2023 |
| AWS Developer Associate exam facts and version change | AWS Certification |
Where this example stops
- A first job with no production system yet: the software developer page shows how a junior CV leans on projects and internships.
- Roles that are mostly pipelines, clusters and cloud accounts: the DevOps and cloud engineer page fits better.
- Interface-heavy full-stack roles: the frontend developer page covers live links and accessibility.
- If your employer forbids sharing traffic figures, give ranges or ratios ("about 3x faster") rather than inventing round numbers.
Applying abroad, and building the CV
For Germany, the developer CV page covers the IT route for people without a degree and what German employers expect in the document. For the Netherlands, the developer page covers English-language teams and the sponsor requirement. Neither repeats what is above, and this page does not repeat them.
CitedCV can draft this kind of CV from facts you enter or from an uploaded CV. It checks numbers and named entities in each line against those facts and drops a line it cannot match, so a latency figure appears only if you gave it. A new account gets 6 free credits for a first quick draft.
Questions people ask
How do I show scale on a backend developer resume?
Give throughput with a time unit, a latency percentile at that load, and data sizes in rows or gigabytes. Say whether the number is for your service or the whole platform.
What should a backend developer CV include?
The systems you built or changed, the APIs and data stores you designed, numbers for load and reliability, production ownership such as on-call, and a short skills block that each bullet supports.
Can I put p99 latency on my CV?
Yes, if you state the load and the before and after values. Google’s SRE book prefers percentiles to averages because averages hide slow requests.
How do I describe API experience on a resume?
Name the API style, how many teams or partners call it, its monthly volume, and how you kept consumers working through changes, such as versioning or contract tests.
Do backend developers need a certification?
No. The O*NET and National Careers Service profiles list none. A cloud developer certificate helps only when a posting names that cloud.
My employer will not let me share traffic numbers. What do I write?
Use ratios and ranges, such as "about 3x faster" or "tens of millions of rows", and keep them true. Do not replace a confidential number with an invented one.
Should OWASP appear on a backend CV?
Only next to a real fix. A line naming the OWASP API Top 10 item you addressed is specific; listing OWASP as a skill on its own says little.
Sources
- O*NET OnLine, 15-1252.00 Software Developerswww.onetonline.org/link/summary/15-1252.00
- U.S. Bureau of Labor Statistics, Occupational Outlook Handbook: Software Developerswww.bls.gov/ooh/computer-and-information-technology/software-developers.htm
- National Careers Service, Software developernationalcareers.service.gov.uk/job-profiles/software-developer
- National Careers Service, IT security co-ordinatornationalcareers.service.gov.uk/job-profiles/it-security-co-ordinator
- Google, Site Reliability Engineering, Service Level Objectivessre.google/sre-book/service-level-objectives/
- OWASP API Security Top 10, 2023 editionapi-security.owasp.org/editions/2023/en/0x11-t10
- AWS Certified Developer, Associateaws.amazon.com/certification/certified-developer-associate/