Vivek Lalgondar

I'm a backend engineer. I like working on the layer where correctness and scale actually matter: API contracts, what happens when a dependency goes down, whether something holds up under real load. Right now that's Fidelity's Public Container Platform team, where I write Go and Python for the Kubernetes add-ons and cluster-management APIs that run across 700+ clusters firm-wide. I've owned REST endpoints end to end, from design through production, including the validation, idempotency, and failure handling that come with writing code other teams depend on.

I did two internships at Fidelity before joining full-time. The first summer I built a rules engine that automated compliance and quality checks across 50+ applications and took about 5 hours of manual review off the team's plate every week. The next summer I worked on Kubernetes migrations, building a Jenkins pipeline that automatically tracked over 1,200 of them and turned a 5-hour manual process into something that took under 2 minutes. Two different problems, same shape: find the manual, brittle part of a system and replace it with something that holds.

On my own time I build things that solve problems I actually have. LearnGraph came out of getting frustrated trying to learn a new technical field from disconnected tutorials. You give it a topic, it generates a prerequisite graph, figures out what you already know, and hands back a personalized learning path through the concepts you don't. Getting the reliability right meant building a FastAPI backend, a React frontend, Redis caching, and a multi-provider LLM layer with a circuit breaker and a database fallback. That kind of defensive engineering feels familiar from the day job.

Outside of work I play basketball and tennis, and I will never turn down a chess game. If you want to talk backend architecture, distributed systems, or swap TV recommendations, my inbox is open.