Backend & Distributed Systems · Go · gRPC · System Design
I build services meant to survive production, and solve problems in C++ for fun.
- I write Go for backend and distributed infrastructure: gRPC services, workflow orchestration, and real-time game servers.
- I learn system design by building it: control-plane / data-plane splits, DAG scheduling, Redis-backed state, and failure handling that actually gets exercised.
- Full-stack when a project calls for it, with TypeScript, React, and Turborepo monorepos.
- Competitive programming in C++ on LeetCode and CodeChef.
Day to day: Go, gRPC, Protocol Buffers, PostgreSQL and Redis.
| Languages | |
| Backend & Services |
|
| Data & Storage | |
| Tooling & Infra |
|
| Frontend |
- Distributed systems: consensus, fault tolerance, and execution semantics under partial failure.
- Retries and idempotency, and what "exactly once" actually costs.
- Production concerns: backpressure, observability, and graceful degradation.
- Go in depth: concurrency patterns, context propagation, and testing discipline.
Open to backend and distributed systems work. The fastest way to reach me is LinkedIn or harishnarote7@gmail.com.



