Software Engineer Resume Example (2026 Guide)
Software 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.
Rohan Bhatia
[email protected] • (555) 013-4471 • Seattle, WA • linkedin.com/in/rohanbhatia
Professional Summary
Software Engineer with 11 years of experience designing and running distributed systems in Java and Python for payments, e-commerce and logistics platforms. Technical lead for a payments authorization platform of 14 microservices on AWS and Kubernetes that handles 38 million API requests a day at 99.99% availability. Cut p99 latency on the card authorization API by 42% and AWS spend by $1.1M a year through profiling, caching and right-sizing work led across three teams. Works through written design documents and careful code review, and mentors engineers toward owning their services in production.
Technical Skills
- Languages: Java, Python, Kotlin, SQL, TypeScript, Bash
- Backend & Distributed Systems: Microservices, REST and gRPC API design, event-driven architecture, Apache Kafka, idempotency and retries, distributed caching, Spring Boot, FastAPI
- Cloud & Infrastructure: AWS (EC2, EKS, Lambda, SQS, RDS, DynamoDB), Kubernetes, Docker, Terraform, Helm
- Data Stores: PostgreSQL, Aurora MySQL, DynamoDB, Redis, Elasticsearch
- Observability & Reliability: Datadog, Prometheus, Grafana, OpenTelemetry, SLOs and error budgets, incident response, load testing with k6
- Engineering Practices: Code review, design documents, CI/CD with GitHub Actions and Argo CD, test-driven development, trunk-based development, scalability planning, mentoring
Education & Certification
- Coursework focus: Distributed Systems, Operating Systems, Database Systems, Algorithms and Computer Networks; Dean’s List six quarters.
Work Experience
Staff Software EngineerMarch 2022 – PresentTidewell Payments, Seattle, WA
- Cut p99 latency of the card authorization API from 310 ms to 180 ms by profiling hot paths, replacing synchronous fraud-score calls with a Redis-cached lookup and tuning JVM garbage collection.
- Lead the technical design for a payments authorization platform of 14 Java microservices on AWS EKS that handles 38 million API requests a day at 99.99% availability.
- Reduced AWS spend by $1.1M a year by right-sizing 220 Kubernetes workloads, moving batch jobs to Spot capacity and retiring three duplicated data stores, with no change to SLOs.
- Eliminated duplicate charges during network retries by designing idempotency keys and an outbox pattern on Kafka, closing a defect class that had caused about 40 customer refunds a month.
- Migrated the ledger service from a shared MySQL instance to Aurora PostgreSQL using dual writes and shadow reads, cutting over 1.2 billion rows with zero downtime.
- Shortened incident detection from 11 minutes to under 3 by defining SLOs and error-budget alerts in Datadog for every tier-one service and writing the runbooks the on-call rotation uses.
- Mentor six engineers and run the weekly architecture review, where 30+ design documents a year are reviewed before build; two of those engineers have since been promoted to senior.
Senior Software EngineerMay 2018 – February 2022Harborview Commerce, Seattle, WA
- Scaled the order service from 900 to 6,500 requests per second for holiday peak by splitting a Java monolith into five Spring Boot microservices behind an API gateway.
- Replaced nightly batch files with a Kafka event pipeline that streams order, inventory and shipping events to 11 downstream consumers, cutting inventory sync delay from hours to seconds.
- Raised deployment frequency from weekly to 20+ times a day by moving the team to trunk-based development, GitHub Actions pipelines and feature flags.
- Lowered checkout error rate from 1.8% to 0.4% by adding circuit breakers, retries with backoff and contract tests between the cart, pricing and payment APIs.
- Shortened average code review turnaround from two days to six hours by writing the team’s review guide and reviewing 15 to 20 pull requests a week.
Software EngineerJuly 2015 – April 2018Cascadia Freight Systems, Portland, OR
- Delivered a shipment-tracking API in Python and PostgreSQL that served 2 million lookups a day to 300 carrier partners, replacing a nightly EDI file exchange.
- Cut route-planning batch runtime from 4 hours to 35 minutes by rewriting the job as parallel workers on AWS and indexing the three largest PostgreSQL tables.
- Halved production incidents in the billing module by raising unit and integration test coverage from 35% to 80% before a major refactor.
- Containerized eight services with Docker and wrote the team’s first Terraform modules for AWS, turning a new staging environment into a one-command setup.
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 puts the scale in one sentence: 14 microservices, 38 million API requests a day and 99.99% availability, which tells a hiring manager the size of system this engineer has owned.
- Each tool is tied to an outcome, as in "Cut p99 latency of the card authorization API from 310 ms to 180 ms by ... replacing synchronous fraud-score calls with a Redis-cached lookup," so Java, Redis and AWS read as proof rather than a list.
- Distributed-systems judgment is visible in specific bullets about idempotency keys, an outbox pattern on Kafka and a zero-downtime migration of 1.2 billion rows, not in adjectives.
- Technical Skills are grouped the way engineering postings are written (Languages, Cloud & Infrastructure, Observability & Reliability), so an ATS finds Java, Python, Microservices, Kubernetes and AWS at once.
- Seniority shows through progression from Software Engineer to Staff, plus mentoring six engineers and running a weekly architecture review in the current role.
Common Resume Mistakes
- Listing every technology without context; tie tools to outcomes.
- Generic bullets like "Wrote code" or "Worked on the backend"; be specific.
- Omitting metrics; even rough scale (e.g. "high-traffic", "low-latency") helps.
Keywords Recruiters Look For
- Java
- Python
- Microservices
- API
- AWS
- Kubernetes
- Distributed systems
- Scalability
- Code review
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 freeRelated roles
Related reading
- QA tester resume skills postings ask you to proveA data-backed guide to the QA tester resume skills employers name most, plus how to show the coverage, tools and test ownership behind them.
- Product manager resume skills postings ask you to proveSee which product manager resume skills appeared most in 30 postings, then turn roadmap, data, discovery and stakeholder work into proof-rich bullets.
- What is a good ATS score? Fix the right gaps firstThere is no universal good ATS score. Use a resume match score to find missing requirements, weak proof and wording gaps for one posting.