Hi, I’m Vaibhav 👋

Harness was a very different kind of challenge — more platform, more reliability, more “make this system behave at scale”. I worked across backend services and infra-heavy components, hopping between TypeScript, Go, PostgreSQL and internal tooling.

A big part of my time went into the Gamechange initiative, where I built a clean and auditable trail for changes to donation limits. It sounds small, but it played a major role in SOC 2 compliance and helped the revenue team track “what changed, when and why” without digging through logs.

I also improved the front-end experience around Visa/Mastercard validations by making those API calls asynchronous using a queuing layer — shaving off delays and making things feel much snappier for users.

Overall: lots of ownership, lots of systems thinking, and a deeper appreciation for how companies keep things reliable behind the scenes.

My first real adventure in the tech world. I joined Fetch when it was a ~300-person startup and got thrown into the deep end in the best possible way. I worked closely with mobile engineers, designers and backend teams (and even directly under the CTO for a bit), building features, improving infrastructure and learning how high-scale systems behave in real life.

It’s where I really fell in love with backend engineering — clean APIs, observability, reliability, data-heavy flows and the “let’s figure this out” culture. For the details, feel free to check out my resume, but the short version is: I grew a lot here.

I spent a summer with the Alexa Shopping ASR team, diving into the world of speech, machine learning workflows and large-scale internal tooling. My work spanned analyzing utterances, identifying phonetically similar words, and building an end-to-end system that automated a manual process used by non-technical teams.

It was also my first exposure to large orgs, CI/CD pipelines, and the rhythm of shipping things that actually help people internally. A very cool chapter.

My very first internship — the place where I learned how maps, spatial data and backend services come together. I built a system that streamlined how GeoServers were managed, integrated Java-based APIs with underlying geospatial tooling, and created features like shapefile rendering and distance/label overlays.

Looking back, it was the spark that pushed me toward backend engineering.