Episode Summary
Executive Summary: Michelle describes her path from early tech internships to becoming Warp’s founding engineer and now founder of Flint. She argues that smaller, product-centric teams create more ownership, that founding engineers should embrace unattractive but critical work, and that reference checks on founders matter deeply. The episode also explores how AI and Rust are reshaping developer tools and how autonomous websites may redefine marketing and the web.
Main Topics: From internships to startup ownership: Michelle explains how moving from large companies to smaller teams increased her sense of ownership and clarity of impact, ultimately pushing her toward founding roles. Choosing Warp as engineer #1: She recounts joining an early, unproven terminal startup despite safer options, driven by strong product conviction, founder quality, and the chance to learn directly from a seasoned technical leader. Product engineer vs founding engineer: Michelle distinguishes product-first engineers from code-first/infrastructure engineers, and clarifies that founding engineer is about timing and scope while product engineer is about mindset and user orientation. Hiring, negotiation, and founder reference checks: She shares tactics for evaluating founders, negotiating equity, and assessing whether a startup will treat early employees fairly and support growth. Why Warp rewrote in Rust: The team scrapped an initial TypeScript stack and rebuilt in Rust for performance, developer expectations, and long-term product credibility in terminal software. AI tools and autonomous websites at Flint: Michelle describes Flint’s vision: websites that dynamically generate, personalize, and optimize themselves using AI, including agent-to-agent interactions and on-brand page generation. Doing the unglamorous work to grow: She emphasizes that founding engineers should volunteer for critical but unattractive tasks—like marketing, community, and enterprise-sales work—to learn the business and earn larger responsibilities.
Key Arguments: Ownership tends to increase as company size decreases; smaller teams create a tighter line of sight between work and user impact. Joining an early-stage company can be rational when the product is deeply compelling and the founder is exceptional, even if safer offers exist. Founding engineers should judge founders not just by vision, but by whether they invest in junior talent, share upside, and think about employee outcomes early. Reference checks should probe whether you would want to work with the manager again and whether they genuinely mentor young engineers. Product engineering is best understood as solving user problems end-to-end, not as a synonym for front-end work. For early startups, product instinct matters more than specialization because the team needs people who can fill gaps across the business. Rust was chosen at Warp because terminal software demanded high performance and because the developer audience valued low-level, efficient tooling. AI tools are increasingly becoming part of the everyday engineering workflow, with pair-programming-like benefits and productivity gains. Founding engineers should expect to do non-engineering work if it helps the company grow, because those tasks often reveal business opportunities. Flint’s thesis is that websites will become autonomous systems that react to market data, customer context, and agent visitors in real time.
Data Points: Internship company size progression: 12,000 → 1,200 → 300 - Michelle says she moved through internships at progressively smaller companies and felt more ownership each time. Slack headcount at the time: 1,200 people - She joined Slack when it still felt startup-like to her. Robinhood headcount at the time: 300 people - Her Robinhood internship helped her find her product sweet spot. Warp founding team size threshold: First five or so people within the first few months - Michelle’s definition of a founding engineer. Initial Warp stack: TypeScript, later rebuilt in Rust - The team scrapped the initial repo 2–3 months in and rewrote for performance and speed. Offer options: 3 compensation options - Michelle received a spreadsheet with increasing salary and decreasing equity. Startup stage options she passed on: 15–20 person teams, Series A, $10M ARR companies - She had safer alternatives before choosing Warp. Slack outage period: Summer 2018 - She cites Slack outages during enterprise expansion as evidence of terminal/CLI tooling impact. Facebook University boot camp length: 2 weeks - She learned app-building and collaboration there before being placed into a pod. Terminal stress test: 1,000 rectangles - At Warp, she tested performance by drawing many rectangles and scrolling. AI pricing: $150 per month starting pro pricing - Mentioned in the StatSig sponsor segment. Notion experimentation scale: 300+ experiments per quarter - Used as a sponsor example of experimentation at scale. Notion features behind flags: 600+ features - Sponsor example of shipping safely with feature management.
Pivotal Quotes: "Every time I went down roughly an order of magnitude, I felt way more ownership." — Michelle: Explaining why smaller companies appealed to her more than large ones. "I was willing to go extremely low on cash." — Michelle: Describing how she negotiated for equity over salary when joining Warp early. "You don't leave companies, you leave managers." — Michelle: Her rationale for checking references on Zach before joining Warp.
Implications: For engineers, the episode suggests that startup success depends on product judgment, founder quality, and willingness to do unglamorous work. For the industry, AI is pushing both software creation and websites toward more autonomous, continuously optimized systems.