Project / Service Name
Problem: Brief description of the business/system problem.
Approach: Architecture decisions, data flow, patterns, trade‑offs.
Impact: Metrics: latency, throughput, success rate, cost, developer velocity.
Backend Engineer
I build reliable, low‑latency backends.
One line about your value. Example: “I design clean architectures and resilient APIs that stay fast at scale.” Replace with your own.
Requests/day
0
P99 latency
0
Uptime / SLO
0
Focus
Write 2–3 sentences about what you focus on (e.g., API design, observability, DDD, microservices). Keep it crisp and concrete.
Skills
Language / Go
Python
PostgreSQL
MongoDB
Redis
REST
gRPC
DDD
Microservices
Kafka
RabbitMQ
Docker
Kubernetes
AWS
Prometheus
Grafana
ELK
Case Studies
Platform Modernization
Problem: Legacy monolith constrained scalability and delivery speed.
Approach: Defined domains, split services, added messaging, observability, CI/CD.
Impact: Services ×N, P99 ↓, deploys/day ↑, incidents ↓.
Experience
- Job Title – Company · Dates · Location
- Owned service(s); delivered X with impact Y.
- Improved SLO/latency/cost by N% via Z.
- Previous Role – Company · Dates · Location
- Migrated monolith → microservices; set up CI/CD & observability.
Contact
Tip: export a PDF resume and host it in this repo, then link it here.