LaTeX resume example
Golang Resume
A single-column LaTeX resume for Go backend engineers, with Go bullets, skills and a project already filled in. Copy the LaTeX below, or upload your own resume to have it rebuilt in this layout.
kevin.chandra@email.com • +1 (665) 597-5231 • github.com/kevinchandra • linkedin.com/in/kevin-chandra
Languages: Go (Golang), C++, SQL (PostgreSQL), Bash, Python
Frameworks: gRPC, Gin, Echo, Protocol Buffers, Gorm, Cobra
Tools: Kubernetes, Docker, Kafka, Redis, Terraform, AWS, Prometheus
- Architected a high-throughput telemetry ingestion service in Go, handling 650k requests per second while maintaining a P99 latency under 20ms.
- Optimized memory allocation patterns using sync.Pool, reducing garbage collection overhead by 35% and saving $120k in annual cloud compute costs.
- Built a custom distributed rate-limiting library using Redis and the Token Bucket algorithm, preventing cascading failures across 15 downstream microservices.
- Migrated a legacy Java-based payment processing worker to Go, resulting in a 5x improvement in startup time and a 3x reduction in memory footprint per container.
- Developed a robust event-driven pipeline using Kafka and Go consumers to process 10TB of daily log data for the content delivery network team.
- Developed a distributed, strongly consistent Key-Value store implementing the Raft consensus algorithm to manage state across five nodes.
Convert your resume to this format
Upload your current PDF and see it rebuilt in this layout, with feedback on your Go bullets.
Drop your resume here
or choose a PDF (max 10MB)
Preparing your resume
Go bullets, before and after
Each rewrite names the service, the number and the Go mechanism behind it.
Before
Used Go to build microservices and fixed bugs in production.
After
Re-engineered three core microservices in Go, reducing P99 latency from 400ms to 45ms and eliminating a race condition that caused 2% of daily transaction failures.
Names the problem (a race condition) and the latency change, which shows concurrency experience.
Before
Responsible for writing unit tests and maintaining the API documentation.
After
Increased backend test coverage from 55% to 92% by implementing table-driven testing in Go, reducing the monthly production incident count by 30%.
Ties testing work to fewer production incidents.
Before
Scaled the backend to handle more users.
After
Optimized database connection pooling and Go routine management to support a 4x increase in concurrent users (from 20k to 80k) without increasing infrastructure spend.
User counts and the unchanged infrastructure spend show the scale you worked at.
Frequently asked questions
Four questions Go candidates ask.
Should I list C++ or Java on a Go resume?
Yes, if the role touches systems work. C++ shows you have dealt with memory and pointers directly, which carries over to Go performance work.
What Go skill should the resume show most clearly?
Concurrency. Say what you ran with goroutines and channels, and what broke: a deadlock you found, a worker pool you sized, a race you fixed.
Does layout matter for senior Go roles?
A little. Staff engineers skim, so a single-column layout that parses cleanly in ATS software is enough. Fancy design adds nothing.
How do I show Go experience if I came from another language?
Point to a Go project you shipped or contributed to, such as a CLI tool or a small distributed system, and describe a problem you solved in it.