VP, Technology
The frontend hiring loop and the rubric we interview against. Architecture reviews, RFCs, framework upgrades. 1:1s, direction, and getting things out of people's way.
I've been at Tracxn since 2015. I joined as an engineer and I run part of technology there now. Most weeks I'm still writing code.
Bengaluru.
Public work since 2013.
Replies in IST: slowest in March, fastest on Sundays.
Eleven years at Tracxn while the industry moved every eighteen months. Wind the press back and the years come off one at a time.
The frontend hiring loop and the rubric we interview against. Architecture reviews, RFCs, framework upgrades. 1:1s, direction, and getting things out of people's way.
A browser-extension build pipeline across Chrome and Firefox. And a hand-rolled AST codemod that migrated a button component across a frontend that had been alive for eight years.
Multi-team architecture. Translating product asks into engineering work, reviewing the queue, escalating what needed escalating.
Most of this doesn't show up in commits.
I wrote the internal React component library. The team has built on it for the decade since, which makes it the most useful thing I've made and the least visible. Also the first Node service and the Webpack, Babel, ESLint and Storybook stack everyone inherited.
First commit on day one. The landing page, the dashboard, feeds, the signup flow. Then the mobile app on React Native and Redux, when both were new.
The frontend for eezyconnect.com. Then the UI for invenzone.com, a social network for researchers, and for early arya.ai. My first public repos date from here. They're still up there.
Tracxn is a private-market data platform. Companies, the legal entities behind them, investors, funding rounds, acquisitions, cap tables, founders, sectors — millions of records across fifty-odd countries, cross-referenced. The assistant answers questions over all of it, and works out which parts a question needs.
It lives inside the API documentation portal, which generates itself from the OpenAPI spec. A router picks the model per question. A skills layer covers what it can do. Prompts are versioned behind an eval harness. Document export runs server-side, and the logs are auditable.
Then an MCP server on top. Read-only connectors behind OAuth, so coding clients reach the API without pasting a key. The team co-owns it now.
Shipped it, then kept hardening it while running the rest of the engineering queue.
106 word-sized chart types for React, small enough to sit inside a sentence or a table cell. Zero runtime dependencies, accessible by default. Entirely my own time.
A CSS button library. Product Hunt picked it up in 2016 and it's still in people's projects. Most of those stars came from a week I wasn't expecting.
Ten years on, it is still the thing strangers write to me about.
A tracker for India's Sovereign Gold Bonds. Every series on one page, ranked by what a buyer actually earns at today's price rather than the coupon printed on the face value.
A scraper on a cron, one JSON file on S3, four years of iteration. Still up, still mine.

Travel and photography, mostly together. Soccer, badminton, the occasional video game. English, Hindi, Kannada.
I still write code most weeks. The AI tooling made it fast enough to get from an idea to something real that I came back to the keyboard.
BE, Computer Science · RNSIT, Bengaluru · 2011–2014
College football team
Spoke at TinyConf 2, Bangalore · 2019 — Virtualised infinite scroll, drawing on react-delightful-scroller.
Hiring, mentoring, architecture, open source. Replies in IST: slowest in March, fastest on Sundays.
vsg.inbox@gmail.com