Back-End Developer resume example

This example shows how a back-end developer in Dublin can present API, database and reliability work with measurable outcomes. It pairs a mid-level current role with an earlier junior role to show clear growth.

Start with this template

Sofia Alvarez

Back-End Developer

Dublin

Professional summary

Back-end developer with 6 years of experience building REST services and data pipelines in Python and Go. Skilled at PostgreSQL tuning, event-driven design and reliable deployments. Collaborates closely with front-end and product teams to ship stable features.

Experience

Back-End Developer · Liffey Commerce Systems
2021 – Present
- Built payment and messaging integrations in Go, adding retry logic and idempotency keys that cut duplicate transactions to near zero
- Tuned PostgreSQL queries and added composite indexes, reducing p95 response time on the orders API from 900 ms to 310 ms
- Introduced Kafka-based order events to replace nightly batch jobs, so reporting data arrived within two minutes instead of the next morning
Junior Software Engineer · Harbour Data Works
2018 – 2021
- Wrote SQL migrations and Python endpoints for reporting features, delivering 12 customer-requested dashboards over two years
- Documented API contracts with OpenAPI specifications, helping front-end developers integrate new endpoints without waiting on clarifications
- Automated staging deployments with Docker and a CI pipeline, shortening release preparation from half a day to about 45 minutes

Skills

Python · Go · REST API design · PostgreSQL · SQL · Kafka · Docker · Kubernetes · AWS · CI/CD

Education

BSc, Computer Science — Dublin Technical University (2018)

This example is fictional and written for illustration. Replace every name, company, date and number with your own facts.

Name the data stores, queues and languages next to each achievement, such as PostgreSQL or Kafka, so the scope of your work is clear.
Quantify performance work with before and after figures like p95 latency, throughput or query time rather than saying you improved speed.
Describe reliability work through concrete results: fewer incidents, shorter recovery time, or an SLO you defined and met.
Mention who consumed your APIs, such as mobile or front-end teams or partners, to show you understand integration and contract design.
Show ownership by stating what you designed, migrated or on-called for, instead of listing tasks the whole team did.

Should a back-end resume list every language and tool I have used?

No. List the technologies you can discuss in depth and have used in recent roles. A focused list of 8 to 10 skills reads better than a long inventory, and each should be backed by a bullet.

How do I show impact if I do not own business metrics?

Use engineering metrics you can observe: latency, error rates, deployment time, query cost or batch duration. Estimates are fine if they are honest and you can explain how you measured them.

Is it worth linking to code or projects?

It can help if the code is clean, documented and relevant, such as an API or tooling project. Reviewers may or may not open links, so the resume should still stand on its own.