I'm a 0-to-1 and 1-to-10 builder. Fields of View was 0-to-1: building a research company and the software behind it. At Flash.co I've done it twice more, across 2 pivots. The 1-to-10 side is Livspace: scaling infrastructure, CAC, and org complexity once the thing already worked.

I'm currently heading engineering at Flash.co, building AI-powered commerce and was one of the earliest people on the team. I own tech and AI strategy, hiring, budget, and delivery.

I've stayed hands-on throughout. Our industry is going through a massive change, and I believe AI amplifies what's already good. So I keep coming back to the fundamentals: writing things down, designing before building, testing properly, keeping it simple.

Head of Engineering

Flash AI

I run engineering end to end for Flash.co. We've scaled to about 1.3 million monthly users and shipped 2 pivots, the second in 6 weeks, while keeping the team small.

I was one of the earliest people on the team, and I run engineering end to end here: strategy, architecture, budget, hiring, delivery, all of it. We've scaled to about 1.3 million monthly users and shipped 2 pivots, the second a full rebuild in 6 weeks with 3 engineers.

Keeping the economics honest matters as much as the engineering. Tech is about 18% of what we spend acquiring a customer, and I've kept the infra deliberately boring: containers on ECS Fargate, GitHub Actions for CI/CD, so the team spends its time building instead of fighting the stack. Deploys run 2-3 times a day per engineer, 8-10 minutes from merge to production behind feature flags, with 5-minute rollbacks when something's off.

Underneath it all is an agent platform we built: it keeps 7.9K product lists freshly ranked (217K products across India and the US) at under a dollar a list, with LLM judges catching most mistakes before they publish. That same platform, the product catalog, pricing, context graph, and commerce graph it maintains, is what now powers selling over WhatsApp, which we're piloting as a key channel.

I was also part of a team of 2 that started Buffy, a B2B sales agent for Shopify stores. It worked, just not as a business, so we shut it down.

None of this needed a bigger team. I've held the budget flat for 4 years running, betting on density over headcount, and replaced most of the ceremony with written specs and design-first reviews. Idea to proof of concept takes a day or 2 now, not weeks; new hires are shipping to production inside their first week.

Head of Engineering

Flash AI

I stay hands-on across infra, agents, and UI at Flash.co. The second pivot, rebuilding flash.co as a marketplace agents run end to end, took 3 of us 6 weeks, on top of the platform I built that keeps 217K products ranked across 7.9K live lists.

I stay hands-on across infra, agents, and UI here. The second pivot, rebuilding flash.co as a marketplace where agents do what a storefront used to, took 3 of us 6 weeks. I built the WhatsApp agent we're now piloting as a growing channel for bringing people in, and rebuilt our email infrastructure: 50,000 addresses to about 1.5 million, cost per million emails down more than 70%.

The part I'm proudest of is the agent platform underneath it all: a pipeline that keeps around 7.9K product lists ranked and current (nearly 217K products), pulling from 5 research sources, validating with LLMs, running nightly supervisors to catch what slipped. Only about 1 in 4 flagged removals turns out to be right, which tells you the validators are doing real work, not rubber-stamping. Judges correct most builds before they go live, and automated fixes land right the vast majority of the time.

Under the hood, I moved the agent stack from an in-house harness to LangGraph and then to Mastra, after trying CrewAI and a few others, and built real durability on top of it: idempotent steps, heartbeat-based ownership, orphan recovery. We've pulled back over 300 runs across redeploys that would otherwise just be lost. I re-benchmark the model router every few months and pin tasks to whatever's cheapest and good enough; plenty of this doesn't need an LLM at all.

I've also kept the team small on purpose. Budget's been flat for 4 years, because I'd rather have a few people who are excellent than many who are fine. Specs over meetings, design before code: idea to working prototype takes a day or 2 now.

Livspace is where I learned to run a 1-to-10 org through real complexity. I was privileged to be part of the team when it turned unicorn, and picked up the Founders Award twice. VideoKen came before that, where I designed a stack for over 10 million API requests a day. Before that: 4 years building Fields of View, a company I co-founded, and research work at CSTEP.

Director of Engineering

Livspace

Owned the pre-fulfilment domain, about half of engineering, growing the org from 35 to 50 while leading EMs and Staff Engineers. Picked up the Founders Award twice, and shipped the products behind a 20% drop in CAC and faster country launches.

I owned the pre-fulfilment domain at Livspace (about half of engineering, roughly 50 people by the time I left, up from 35), reporting into the technology leadership, and picked up the Founders Award twice along the way.

The products we shipped moved real numbers: about a 20% cut in customer acquisition cost, a 17% rise in organic leads, 12% more conversion, and country launches that went from taking months to half that. The superapp, Fury for landing pages, Quotes, and Inkpot as a headless CMS all fed the same push. My teams owned the tech for every new country launch too.

Hiring was the other half of the job: I grew the org from 35 to 50, halved our time-to-offer, and got new engineers to their first production push inside 2 weeks. I also started the Livspace engineering blog, mostly because I wanted a place for the team to write about what we were actually building.

Director of Engineering

Livspace

Owned the pre-fulfilment domain (about half of engineering) and the platform underneath it: 99.99% availability, Java services handling 600 requests a second under 200ms, webapp load time from 15 seconds to 1.

At Livspace I owned the pre-fulfilment domain, leading EMs and Staff Engineers across about half of engineering. The work that stuck with me most was the platform underneath everything else.

We held a 99.99% availability SLO across our microservices, 99.999% for the services that really couldn't go down, and I refactored the core Java services to handle around 600 requests a second at under 200ms, per pod, with no extra scaling, benchmarked properly with k6 rather than taking anyone's word for it.

I also cut the consumer webapp's load time from 15 seconds to 1, and scaled the demand-generation stack to handle 3 million visitors a month without it falling over. The products riding on top of this (the superapp, Fury, Quotes, Inkpot) are the ones that moved the business numbers, but none of that works without the platform holding up underneath.

Lead Engineer

VideoKen

Full-stack lead for reporting, analytics, and integrations. Designed the stack to handle 10M+ API requests/day.

I led full-stack work on VideoKen's reporting, analytics, and integrations dashboard, and built the tracking pipeline behind their AI Player, a lightweight, queue-based system that processed viewing events within 2 seconds of them happening, so learning managers could see where people dropped off in near real time. I also designed the integrations layer every partner and third-party connection ran through, and built the stack to handle a production peak of about 3.5 million API requests a day, load-tested well past that to 10 million.

Co-Founder

Fields of View

Built simulation software for policy research. Clients include Govt. of India, Govt. of Karnataka, and TU Delft.

I co-founded Fields of View. I split my time roughly 70/30: building the simulation software and doing the research, with the rest going to grant funding, operations, and client delivery. I ran finance by the time I left.

We raised research grants from the Government of India, the Dutch Research Council for a joint India–Netherlands project, and the Government of Karnataka, and delivered simulation software to the Department of Science and Technology, the Government of Karnataka, and TU Delft.

Research Associate

CSTEP

GIS-based disaster management simulation for DRDO. Software development and research.

2014 — 2017

MS (by Research), Information Technology

IIIT-Bangalore

2006 — 2010

B.E. in Computer Science

Visvesvaraya Technological University