Backend Developer resume example
By Bhagirath Sheela, founder of JobCatch ·
Backend work is invisible to users, so your resume has to make it visible: what services you built, what load they carried, and what you did when they broke. Hiring managers read for reliability and scale, and they trust numbers from production more than lists of tools.
What recruiters look for
- The language and framework the team uses, and databases you have run in production
- Throughput, latency and uptime figures for services you owned
- Design decisions: caching, queues, schema changes, API design
- On-call and incident experience, which shows you can be trusted with production
Section order
With experience
- Summary
- Skills
- Experience
- Projects
- Education
- Certifications
As a fresher
- Summary
- Education
- Skills
- Projects
- Internships
- Certifications
- Achievements
Summary examples
Fresher
Backend-focused computer science graduate who has built REST APIs in Node.js and Spring Boot with PostgreSQL, deployed on AWS. Strong in SQL and data structures.
Experienced
Backend developer with five years building high-traffic APIs in Java and Go. Owns services handling 12,000 requests a second at 99.95% uptime, and designed the event pipeline on Kafka.
Skills, spelled the way postings spell them
An applicant tracking system matches the words in the job posting, and it does not reliably treat two spellings as one skill. The left column is the form most postings use; the right, other spellings people type. Use the posting's own spelling for each application, and list only what you can discuss in an interview.
| Skill | Also written as |
|---|---|
| Java | Core Java, Java SE |
| Go | Golang |
| Python | Python 3 |
| Spring Boot | SpringBoot, Spring |
| Node.js | NodeJS, Node, Node JS |
| REST APIs | REST, RESTful APIs, REST API |
| Microservices | Microservice architecture |
| PostgreSQL | Postgres, PostgresSQL |
| MySQL | My SQL |
| Redis | — |
| Message queues (Kafka) | Kafka, Apache Kafka |
| Docker | Containerisation, Containerization |
| Kubernetes | K8s, EKS, AKS |
| AWS | Amazon Web Services |
| Database design | Schema design, Data modelling, Data modeling |
Also worth listing if you have them: System design.
Bullet examples
Each bullet says what you did and what changed because of it. Change the numbers to your own; a recruiter will ask about every one.
- Designed and own the notification service in Go, sending 3 crore messages a day at 99.95% uptime.
- Moved order events from database polling to Kafka, cutting end-to-end delay from 45 seconds to under 2.
- Redesigned the PostgreSQL schema for the ledger; the heaviest report query dropped from 14 s to 600 ms.
- Added rate limiting and idempotency keys to the public API, ending duplicate-payment incidents.
- Wrote the on-call runbook for five services; mean time to recovery fell from 52 to 18 minutes.
For freshers: projects and internships
- Built a URL shortener in Node.js and Redis handling 2,000 requests a second in a load test.
- Wrote a REST API for a college event app in Spring Boot and PostgreSQL, used by 900 students.
- Interned on a backend team: added pagination and indexes to a slow admin API, cutting load time by 70%.
Mistakes to avoid
- Bullets with no scale. "Built APIs" could be a weekend project; "12,000 requests a second" could not.
- Hiding incident and on-call work. Handling an outage well is one of the strongest things a backend engineer can show.
- Listing every database you have ever connected to. Name the ones you have designed for and run in production.
What an ATS reads from this sample
An applicant tracking system turns the PDF into plain text before anyone reads it. This is that text for the sample above, extracted by the same code as "What the ATS reads" in the app. Everything is in reading order, under the right heading, with the name and email intact — which is what a single-column template is for.
Rahul Verma Backend Developer [email protected] | +91 98765 43210 | Hyderabad, Telangana | linkedin.com/in/rahulverma Summary Backend developer with five years building high-traffic APIs in Java and Go. Owns services handling 12,000 requests a second at 99.95% uptime, and designed the event pipeline on Kafka. Technical skills Java · Go · Python · Spring Boot · Node.js · REST APIs · Microservices · PostgreSQL · MySQL · Redis · Message queues (Kafka) · Docker · Kubernetes · AWS · Database design · System design Projects Load-testing toolkit Internal tool that replays production traffic against staging; now part of every release. Experience Senior Backend Developer, Relaywave Systems Jun 2022 – Present Hyderabad Designed and own the notification service in Go, sending 3 crore messages a day at 99.95% uptime. Moved order events from database polling to Kafka, cutting end-to-end delay from 45 seconds to under 2. Redesigned the PostgreSQL schema for the ledger; the heaviest report query dropped from 14 s to 600 ms. Backend Developer, Ledgerly Finserv Jul 2020 – May 2022 Hyderabad Added rate limiting and idempotency keys to the public API, ending duplicate-payment incidents. Wrote the on-call runbook for five services; mean time to recovery fell from 52 to 18 minutes. Education B.Tech, Computer Science 2016 – 2020 IIIT Hyderabad · 8.0 CGPA Certifications Confluent Certified Developer for Apache Kafka, 2023 Languages English, Hindi
Interview questions to prepare
The app's interview prep for this sample and a plain Backend Developer posting. It works from the resume and the posting only, and tells you how to prepare, never what to say.
Questions every interview has
- Tell me about yourself. Two minutes: what you do now (Senior Backend Developer at Relaywave Systems), one result you are proud of, and why this role is next.
- Why do you want this job? Read their website and one recent piece of news before the call. Name something specific.
- Why are you leaving your current job? Say what you are moving towards. Do not criticise your employer.
- What is your notice period, and what salary are you expecting? Decide your number before the interview, so you are not deciding it on the call.
About the skills the job asks for
- Tell me about a time you used Python. Pick one real example: what the problem was, what you did, and what changed.
- Tell me about a time you used Java. Pick one real example: what the problem was, what you did, and what changed.
- Tell me about a time you used Node.js. Pick one real example: what the problem was, what you did, and what changed.
- Tell me about a time you used Spring Boot. Pick one real example: what the problem was, what you did, and what changed.
- Tell me about a time you used REST APIs. Pick one real example: what the problem was, what you did, and what changed.
About what the resume claims
- You wrote: "Designed and own the notification service in Go, sending 3 crore messages a day at 99.95% uptime." Expect three follow-ups: how exactly, what was your own part, and how you know it worked.
- You wrote: "Moved order events from database polling to Kafka, cutting end-to-end delay from 45 seconds to under 2." Expect three follow-ups: how exactly, what was your own part, and how you know it worked.
- You wrote: "Redesigned the PostgreSQL schema for the ledger; the heaviest report query dropped from 14 s to 600 ms." Expect three follow-ups: how exactly, what was your own part, and how you know it worked.
Questions to ask them
- What would a good first three months in this role look like?
- Who would I work with most closely?
- What are the next steps, and when should I expect to hear back?
Templates that suit this role
All of these are single-column and read cleanly by an applicant tracking system. Classic is free, with no watermark.
Questions
What projects should a backend fresher show?
Something with a database, an API and a deployment: a URL shortener, a booking system or a chat backend. Include a load test or a design note, because that is what separates it from a tutorial.
Is system design needed on a backend resume?
Not as a heading. Show it inside your bullets — the queue you introduced, the cache you added, the schema you changed and why. That is what interviewers will ask you to explain.
Next: the Backend Developer cover letter the app drafts from this resume, and how to show Java, Python, Spring Boot on a resume.
More engineering resume examples: Software Engineer · Frontend Developer · Full Stack Developer · React Developer · React Native Developer · Angular Developer · Node.js Developer · Java Developer · Python Developer · .NET Developer · Golang Developer · PHP Developer · Android Developer · iOS Developer · Flutter Developer · Mobile App Developer · Embedded Software Engineer · Engineering Manager · Solutions Architect