Backend engineer building distributed systems that operate under real-world scale, latency, and failure constraints. If you're building something ambitious and care about strong backend foundations, I'd love to connect:
- ⚙️ Designing distributed backend services (500K+ requests/minute scale)
- 🔁 Building resilient transaction pipelines with automated failover
- 🧠 Modeling complex state machines (subscriptions, entitlements, risk flows)
- 🗄️ Optimizing PostgreSQL (20TB+ datasets, partitioning, archival strategies)
- 🛡️ Production hardening: circuit breakers, monitoring, traffic routing
- 🚀 Zero-downtime migrations from monolith → microservices
- 🧩 Owning services end-to-end: design, scalability, observability, and production stability
{
"languages": ["TypeScript", "SQL", "Python", "C/C++", "Bash"],
"databases": ["PostgreSQL", "MySQL", "MongoDB", "Redis"],
"messaging": ["Kafka", "BullMQ"],
"cloud": ["AWS", "Azure"],
"containerization": ["Docker", "Kubernetes"],
"ci_cd": ["Jenkins", "ArgoCD", "GitHub Actions"],
"infra_patterns": [
"Circuit Breakers",
"Failover Routing",
"Rate Limiting",
"Caching",
"Partitioning & Archival",
"Zero-Downtime Deployments"
]
}- Measure before optimizing
- Prefer clear abstractions over clever hacks
- Build systems that degrade gracefully
- Design for failure, not just for throughput
- Leave the codebase better than you found it
I’ve handled live production incidents early in my career and learned to think in terms of:
- p95/p99 latency, not averages
- Blast radius containment
- Backpressure & cascading failures
- Observability before guesswork
- Cost-aware architectural decisions
- 👨💻 Owner & Maintainer → https://github.com/coding-cpp
- 🛰️ Ex-Coordinator → https://github.com/astroclubiitk
- 🤖 Ex-Team Member → https://github.com/AerialRobotics-IITK