Product-first vs code-first engineers

Michelle defines product-first and code-first engineers and why product-first suits startups solving user problems.

Play episode from 35:39

chevron_right

Transcript

chevron_right

Transcript

Episode notes

Brought to You By:

•⁠ Statsig ⁠ — ⁠ The unified platform for flags, analytics, experiments, and more.

•⁠ Linear ⁠ — ⁠ The system for modern product development.

—

Michelle Lim joined Warp as engineer number one and is now building her own startup, Flint. She brings a strong product-first mindset shaped by her time at Facebook, Slack, Robinhood, and Warp. Michelle shares why she chose Warp over safer offers, how she evaluates early-stage opportunities, and what she believes distinguishes great founding engineers.

Together, we cover how product-first engineers create value, why negotiating equity at early-stage startups requires a different approach, and why asking founders for references is a smart move. Michelle also shares lessons from building consumer and infrastructure products, how she thinks about tech stack choices, and how engineers can increase their impact by taking on work outside their job descriptions.

If you want to understand what founders look for in early engineers or how to grow into a founding-engineer role, this episode is full of practical advice backed by real examples

—

Timestamps

(00:00) Intro

(01:32) How Michelle got into software engineering

(03:30) Michelle’s internships

(06:19) Learnings from Slack

(08:48) Product learnings at Robinhood

(12:47) Joining Warp as engineer #1

(22:01) Negotiating equity

(26:04) Asking founders for references

(27:36) The top reference questions to ask

(32:53) The evolution of Warp’s tech stack