I’m a backend engineer who spends most of his time working on systems, infrastructure, and the layers that sit behind applications. I’m interested in how software actually behaves in production — how it scales, where it breaks, and how to make it easier to operate. Most of what I build or study is around Kubernetes, distributed systems, and developer tooling. I prefer understanding things from first principles instead of relying on abstractions I don’t fully get.
Languages
- Go (primary), TypeScript/JavaScript, Python(Learning)
Frontend
- HTML(5), CSS, TailwindCSS, ReactJs, NextJs, Web Security, GraphQL
Backend
- Golang, PostgreSQL, REST API's, Redis, Kafka
Infrastructure
- Kubernetes, Docker, Terraform, CI/CD systems, Linux, Prometheus, Grafana, Datadog
- Tried implementing the original MapReduce paper in Go to understand how distributed computation actually works. Here's the repo - https://github.com/ShivamJha2436/go-mapreduce
Kubernetes-native monitoring and autoscaling system.
- Custom Resource Definitions (CRDs)
- Controller-based reconciliation loop
- Metrics-driven scaling decisions
https://github.com/ShivamJha2436/kubehalo
Structured logging and workflow tracking for developers.
- Focus on execution traceability
- Debuggable system design
https://github.com/ShivamJha2436/kiroku
- Portfolio → https://shivamjha.in
- GitHub → https://github.com/ShivamJha2436
- LinkedIn → https://www.linkedin.com/in/shivamkj1/
- X → https://x.com/Hi_Shivam_
If you're working on backend systems, infra, or something interesting in distributed systems — feel free to reach out.