Gaurav Misra

Early employee at Snap where he led the design engineering team; built Captions into one of the most successful consumer AI products with over 10 million users and $100M+ in funding Their core argument: Ship fast — a feature every week, embrace technical debt as strategic leverage. The evidence is specific: Every engineer at Captions ships a marketable product every week. Furthermore, two parallel roadmaps: public (user requests, table stakes) and secret (conviction bets, competitive advantage). Technical debt runway as a mental model: too much debt means 80-90% of time goes to paying interest. In Gaurav Misra's own words: "Our engineering goal is every engineer should ship a marketable product every week." (Describing Captions' core engineering philosophy.)

Early Snap employee who led the design engineering team; co-founder and CEO of Captions, a consumer AI product with over 10 million users and $100M+ raised Their core argument: Maintain two parallel roadmaps: a public one driven by user requests and a secret one driven purely by conviction bets. The evidence is specific: Captions' eye contact feature: built with Nvidia, first to market, went viral globally, now copied across the industry. Furthermore, company-wide quarterly brainstorming sessions that include non-product staff to source secret roadmap ideas. In Gaurav Misra's own words: "We have what we think of as the public roadmap. This is basically what people have asked us for. There's all these surface areas where we receive user feedback, but these are all features that every competitor knows about. If a user is asking us for it, they're asking everybody for it." (Introducing the public vs. secret roadmap concept.)

Early Snap employee who led design engineering, now runs Captions with 10M+ users and $100M+ raised -- operating at the frontier of consumer AI where the pace of technological change makes traditional roadmapping insufficient. Their core argument: Have two roadmaps: one public (from user feedback) and one secret (conviction-based bets). The evidence is specific: Eye contact feature: Captions was the first to build AI-powered eye contact correction for video creators, working with Nvidia who initially did not understand the use case -- it went massively viral and was copied by every competitor. Furthermore, captions does quarterly company-wide brainstorming where everyone (engineering, recruiting, marketing) contributes ideas and votes, feeding the secret roadmap. Q4 is dedicated infrastructure quarter: the team deliberately accumulates technical debt all year for shipping speed, then pays it back before the new year. In Gaurav Misra's own words: "We have what we think of as the public roadmap. This is basically what people have asked us for... And then they have the secret roadmap, which is completely not informed by users or data - it's just them making bets on where the world is going." (The two-roadmap approach separating reactive from proactive work.)

Gaurav Misra spent years at Snap reporting close to Evan Spiegel and now runs Captions with an explicit attempt to replicate the centralized-taste model. His claim is that Spiegel had an unmatched understanding of the user that nobody else at the company could match, even the rest of leadership. The canonical example is Snap declaring itself a 'camera company' — a decision everyone mocked externally that turned out to be the single call protecting Snap against Instagram. Because Snapchat opened straight to the camera, when users wanted to capture a moment they didn't open Instagram first. Instagram couldn't copy it without tanking their own engagement metrics. At Captions, Gaurav now maintains a deliberately founder-curated 'secret roadmap' insulated from feedback machinery. In Gaurav's own words: "I do remember at Snap for example, I think one of the most unique things about Snap and the CEO Evan Spiegel was that he had an unmatched understanding of the user... He would come up with ideas that everybody would disagree with and we would launch them and there would be hits, just hits after hits. And nobody would understand why." (Describing why Snap's centralized taste model worked.)

Misra's argument for keeping design small is built on a specific operating model: every engineer at Captions should ship a marketable feature every week. That tempo is physically incompatible with a large design org — review layers, design crits, research phases, and handoffs make weekly shipping impossible. His counterintuitive move is that when time is compressed, you don't cut quality, you cut scope. Most teams cut the wrong thing: under pressure, PMs, engineers, and designers quietly lower the polish bar when they should instead be removing whole pieces of the feature. His process loops back through scope-cutting until what's left is small enough to ship in a week at high quality. Scaled orgs default to cutting quality because scope is politically locked in. In Gaurav's own words: "The way to cut down on time, and I think this is a mistake people make a lot of the time, is when time is being pressured downward, a lot of times engineers, PMs, designers, they will cut on quality rather than cutting on scope. And actually you can cut on scope." (The core scope-vs-quality argument that keeps a small team from needing to scale.)

Gaurav has the most extreme and fully-articulated version of the debt-as-feature thesis in the archive. His logic: bigger companies don't take on tech debt because they can't — they pay it off immediately or spend all their time paying back debt from when they were a startup. That asymmetry is precisely the exploitable edge for a small team. If a startup refuses to incur debt, it gives up its one structural advantage. But he gives a precise interest-rate model. Every piece of debt costs 1-2% of your time daily in bugs, restarts, maintenance. Accumulate enough and you're paying 80-90% interest just to keep the lights on. The heuristic isn't 'take on unlimited debt' — it's 'you have a technical debt runway, and you have to deliver enough value before that runway runs out.' Captions dedicates Q4 as 'infrastructure quarter' — a planned, predictable paydown cycle. In Gaurav's own words: "Every piece of debt that you take on you have to pay interest on. So if there is debt that you've taken on, there's 1% or 2% of your time that is going to be taken away every day in maintaining bugs and issues and restarts and crashes... If you take on enough debt, you'll be paying 80 or 90% interest and you'll not have any time to do anything new. You'll just be paying interest." (The explicit interest-rate model.)