Backend engineer with 7 years of experience in Go and Java building high-throughput services for ad tech and IoT platforms. Rebuilt a bidding service to handle 220K queries per second under a 40 ms deadline while cutting server count by 35%. Focused on performance, reliability and clean service boundaries.
Experience
Backend Engineer, Signalmark Advertising (New York, NY)
Nov 2021 – Present
Rebuilt the real-time bidding service in Go to handle 220K queries per second within a 40 ms deadline, cutting servers by 35%
Designed a ScyllaDB-backed frequency-capping store with p99 reads under 3 ms
Introduced load tests in k6 and capacity dashboards, preventing two forecasted peak-season outages
Led the gRPC migration of 9 internal APIs, reducing payload size by 60%
Performance: Profiling with pprof, load testing with k6, capacity planning
How to write a Backend Engineer resume
A strong Backend 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
Backend Engineer resume FAQ
What should a Backend Engineer resume include?
A Backend 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 Backend Engineer?
Classic, Tech and Modern work well for Backend Engineer roles. They are single-column with standard headings, so applicant tracking systems (ATS) parse them reliably.
How long should a Backend Engineer resume be?
One page for most candidates; move to two only if every line is relevant.
Which skills should a Backend Engineer put on a resume?
Prioritize the skills named in the job posting. Common ones for Backend 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 Backend 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."