type Engineer struct {
Name string // Narvdeshwar
Role string // Backend Engineer — Golang
Experience string // 3+ Years
Focus []string // Distributed Systems, High-Throughput APIs, Microservices
Location string // Noida, India — Remote/Hybrid Open
}I design and ship production-grade backend systems — from high-throughput REST/gRPC services to event-driven pipelines on Kubernetes. I care deeply about correctness, observability, and systems that don't break under pressure.
Core
Infrastructure
Secondary
| Impact | |
|---|---|
| ⚡ Throughput | Engineered Golang services handling 10,000+ RPS at sub-100ms p99 latency |
| 🚀 Optimization | Reduced API response times by 70% via Redis caching, query tuning & goroutine concurrency |
| ☸️ Orchestration | Deployed microservices on EKS/GKE with HPA autoscaling & zero-downtime rollouts |
| 🌊 Event-Driven | Built async pipelines with Kafka & RabbitMQ — idempotency, DLQ patterns, guaranteed delivery |
| 🔒 Security | Implemented JWT/OAuth2, rate limiting, structured logging & input validation at scale |
| 🏛️ Architecture | Enforced Hexagonal/Onion architecture across teams for testable, maintainable Go codebases |
Engineered a production-ready microservices platform in Go — REST + gRPC communication, Kafka event bus, JWT auth, PostgreSQL + Redis persistence, Dockerized with K8s manifests. Handles 10k+ RPS.
Built a real-time log streaming pipeline in Go — goroutine-based ingestion, Kafka transport, structured JSON output. Designed for high-throughput observability infrastructure.
Scale is earned, not assumed.
Observability is not optional.
Complexity is a liability — simplicity is the goal.
A system is only as good as its failure handling.
I write code that's boring in production and interesting on paper — optimized for correctness, performance, and long-term maintainability over cleverness.
- 🔭 Distributed task scheduler in Go (similar to Temporal/Celery internals)
- 📚 Deepening: System Design, AWS Solutions Architecture, DSA (LeetCode)
- ⚙️ Exploring: eBPF for observability, NATS JetStream as Kafka alternative
Open to: Senior Backend Engineer · Backend SDE II/III · Platform/Infrastructure Engineer · Go + Full-Stack (Go/React)

