Backend Engineer Resume Example (2026 Guide)
Backend Engineer resume example
A complete sample in the Modern template FitMyRole exports. The person and employers are fictional; the structure, skills and bullet style are what to copy.
Nikolai Baranov
[email protected] • (555) 012-9460 • Boston, MA • linkedin.com/in/nikolaibaranov
Professional Summary
Backend Engineer with 7 years of experience building APIs, microservices and data pipelines in Go and Python for logistics, healthcare and ticketing products. Owns the shipment events platform at a parcel logistics company: nine Go services on AWS that ingest 25 million carrier events a day through Kafka into PostgreSQL and Redis. Cut tracking API p95 latency from 420 ms to 95 ms and raised platform availability from 99.5% to 99.95% over two years. Writes design documents before code, tests failure modes on purpose, and takes on-call for every service built.
Technical Skills
- Languages: Go, Python, SQL, Java, TypeScript, Bash
- APIs & Services: REST APIs, gRPC, Protocol Buffers, OpenAPI, microservices, event-driven architecture, rate limiting, OAuth 2.0 and JWT
- Data & Messaging: PostgreSQL, Redis, Apache Kafka, Amazon SQS, DynamoDB, change data capture with Debezium, query optimization
- Cloud & Infrastructure: AWS (EKS, ECS, RDS, Lambda, S3, Athena), Kubernetes, Docker, Terraform, GitHub Actions
- Reliability & Observability: Prometheus, Grafana, OpenTelemetry, PagerDuty, SLOs, load testing, failure drills, scalability planning
- Engineering Practices: Design documents, code review, test-driven development, contract testing, on-call ownership
Education & Certification
- Two co-op terms in backend development; coursework focus: Distributed Systems, Database Design, Networks and Algorithms.
Work Experience
- Cut p95 latency of the public tracking API from 420 ms to 95 ms by adding a Redis read-through cache, rewriting three PostgreSQL queries with covering indexes and moving to Protocol Buffers.
- Own the shipment events platform, nine Go microservices on AWS EKS that ingest 25 million carrier events a day through Kafka into PostgreSQL and Redis.
- Raised platform availability from 99.5% to 99.95% over two years by adding consumer autoscaling, dead-letter queues and replayable Kafka topics, and running quarterly failure drills.
- Scaled event ingestion from 4,000 to 15,000 messages per second ahead of peak season by partitioning topics by carrier and batching database writes, with no added database capacity.
- Reduced AWS cost by $34K a month by moving cold event history from PostgreSQL to partitioned Parquet on S3 queried through Athena, shrinking the primary database by 6 TB.
- Designed rate limiting and OAuth 2.0 client credentials for the partner API, onboarding 120 retail customers without a noisy-neighbor outage.
- Write and review design documents for the backend guild, review 10 to 15 pull requests a week and share a one-week-in-six on-call rotation.
- Built a Python FastAPI service that normalizes lab results from 40 hospital feeds into FHIR resources, processing 1.5 million records a day for clinical analytics customers.
- Cut nightly ETL runtime from 5 hours to 50 minutes by replacing row-by-row inserts with PostgreSQL COPY batches and parallel workers fed by Amazon SQS.
- Reduced deployment time from 40 minutes to 8 by moving four services from EC2 virtual machines to Docker on ECS with Terraform, which also made same-day rollbacks routine.
- Caught 30 breaking schema changes before release in the first year by introducing contract tests between the ingestion and reporting services.
- Implemented row-level audit logging and encryption at rest for patient data, closing two findings in the company’s first SOC 2 Type II audit under HIPAA requirements.
- Prevented double-booked seats during on-sales of up to 30,000 tickets in 10 minutes by building the seat-hold service in Go with Redis-based locks and expiry.
- Reduced checkout API errors by 60% by making payment requests idempotent and adding retries with backoff around the payment provider.
- Wrote REST endpoints and PostgreSQL migrations for the venue management dashboard used by 200 venues to set prices and seat maps.
- Added Prometheus metrics and Grafana dashboards to six services, giving the team its first view of latency and error rates by endpoint.
Want yours to read like this? Upload your resume and a job posting, and FitMyRole rewrites it for that job in this template.
Tailor my resumeWhy This Resume Works
- The summary names the whole stack and its load in one sentence: Go services on AWS ingesting 25 million events a day through Kafka into PostgreSQL and Redis, which covers most of the keywords in a backend posting.
- The latency bullet gives before and after (420 ms to 95 ms) and the three techniques used, so the claim is specific enough for an interviewer to dig into.
- Reliability is measured, not asserted: availability from 99.5% to 99.95%, dead-letter queues and failure drills, and ingestion scaled from 4,000 to 15,000 messages per second.
- Cost awareness shows in the $34K a month saved by moving cold event history to S3 and Athena, a detail that separates a senior backend engineer from someone who only ships features.
- Technical Skills are grouped by layer (APIs & Services, Data & Messaging, Cloud & Infrastructure), and the Confluent Kafka and AWS certifications back up the two technologies the resume leans on most.
Common Resume Mistakes
- Vague "built backend services" without scale or tech details.
- Omitting database, messaging, or cloud keywords.
- No performance or reliability metrics.
Keywords Recruiters Look For
- API
- Microservices
- PostgreSQL
- AWS
- Go
- Python
- Kafka
- Redis
- Scalability
Get more interviews. Tailor your resume automatically
Want to tailor your resume to the job you want? Use FitMyRole to analyze your resume and rewrite it for the role. Before sending your next application, run your resume through FitMyRole to tailor it to the job description.
Try FitMyRole free