Microservices engineer with 7 years of backend experience, 5 of them decomposing monoliths into event-driven services for retail and travel platforms. Split a 1.2M-line Java monolith into 34 services and cut lead time for changes from 3 weeks to 2 days. Brings domain-driven design, Kafka messaging and resilience patterns that hold up under peak traffic.
Experience
Senior Microservices Engineer, Wayfarer Travel Group (Orlando, FL)
Jan 2022 – Present
Decomposed a 1.2M-line Java booking monolith into 34 Spring Boot services using the strangler fig pattern
Cut lead time for changes from 3 weeks to 2 days by giving 8 teams independent deploy pipelines
Introduced Kafka with the outbox pattern for booking events, eliminating dual-write inconsistencies
Added circuit breakers, bulkheads and retries with Resilience4j, keeping search available during 2 supplier outages
Backend Engineer, Sunshine Grocers Digital (Tampa, FL)
Jun 2019 – Dec 2021
Built order and substitution services in Kotlin handling 150,000 grocery orders a day
Defined bounded contexts with product owners in event storming workshops
Education
B.S. Computer Science, University of Central Florida (Aug 2015 – May 2019)
Skills
Languages: Java, Kotlin, Go
Frameworks: Spring Boot, Spring Cloud, gRPC, Resilience4j
Messaging and Data: Kafka, RabbitMQ, PostgreSQL, Redis, outbox pattern
How to write a Microservices Engineer resume
A strong Microservices Engineer resume shows the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Put your most relevant recent role first and make every bullet show a result, not a duty.
Sections, in order
Summary
Experience
Projects
Skills
Education
Length: One page for most candidates; move to two only if every line is relevant.
Summary: Write two or three lines: your role, your strongest skills, and one result that proves them.
Skills to feature
Programming languages
System design
Cloud platforms (AWS, GCP, Azure)
CI/CD
Testing and code review
Databases and SQL
Observability
Security fundamentals
APIs and integrations
Technical documentation
Example bullet points
Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users
Introduced contract tests and staged rollouts, reducing production incidents by 45% in two quarters
Migrated 30 services to Kubernetes with Terraform, lowering cloud spend by $250k a year
Tips from recruiters
Group skills by category (for example "Languages: Go, TypeScript") so recruiters and ATS parsers find them quickly.
Link to a repository, demo or write-up for at least one project you can talk about in depth.
Name the stack inside each bullet; keyword matching happens at the bullet level, not only in the skills list.
Recommended templates
Classic (ATS-friendly): Jake's-style LaTeX classic: small caps and hairline rules
Tech (ATS-friendly): Developer style: mono headings and tags, sans body
Modern (ATS-friendly): Clean single column with accent headings and rules
Microservices Engineer resume FAQ
What should a Microservices Engineer resume include?
A Microservices Engineer resume should show the systems you built, the scale they run at, and the measurable effect on speed, reliability or cost. Use these sections in this order: Summary, Experience, Projects, Skills and Education. Put your most relevant recent role first and make every bullet show a result, not a duty.
What is the best resume template for a Microservices Engineer?
Classic, Tech and Modern work well for Microservices Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Microservices Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Microservices Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for Microservices Engineer roles are Programming languages, System design, Cloud platforms (AWS, GCP, Azure), CI/CD, Testing and code review and Databases and SQL.
How do I write strong Microservices Engineer resume bullet points?
Start with an action verb, say what you did, and end with a measurable result such as latency, uptime and deploy frequency. For example: "Rebuilt the checkout service in Go, cutting p95 latency from 900 ms to 180 ms for 2M monthly users."