I build software that doesnβt just work β it scales, survives load, and behaves well in production.
I started out in web development, building full-stack applications and shipping features end-to-end. Over time, I got more curious about what happens behind those APIs β why systems slow down, how they scale, and what makes them reliable.
That curiosity pulled me toward backend engineering and infrastructure.
Now, I like working on problems around:
- βοΈ System performance & reliability
- π Distributed systems & networking
- π§± Backend architecture
- π Observability & debugging in production
Core: Python β’ JavaScript/TypeScript β’ Java
Backend: Node.js β’ Express β’ FastAPI β’ REST APIs
Infra & Systems: Linux β’ Docker β’ AWS β’ GCP β’ CI/CD
Databases: PostgreSQL β’ MongoDB β’ MySQL
I also occasionally work with ML systems, especially when they need to run efficiently in production.
A deep dive into networking where I built a TCP-like protocol from scratch.
- Handles packet loss, retransmissions, and congestion control
- Explores tradeoffs between performance and reliability
π This is where I really got into low-level systems thinking
- Trained a model to generate docstrings from code
- Built a backend service to serve it in real time
- Focused heavily on latency, memory, and deployment
π Not just ML β but making ML usable in production
- Built a system to track behavior of multiple agents
- Monitored performance, failures, and cost
- Added visibility into what systems are actually doing
π This pushed me toward infra + monitoring mindset
- πΌ LinkedIn: https://linkedin.com/in/bhaveshghanchi
- π§ Email: bhaveshghanchi27@gmail.com
Right now, Iβm leaning deeper into infrastructure + backend systems β understanding how large-scale systems are designed, deployed, and kept reliable.
If you're working on something in that space, I'd love to collaborate.
β Always building. Always learning.
