Become an Epic Product Engineer

Foundations, feedback, and agents — Dillon Mulroy on product at Cloudflare

Become an Epic Product Engineer

Show Notes

Kent talks with Dillon Mulroy, Principal Engineer at Cloudflare, about Agent Experience and dogfooding AI platform work: how Cloudflare closes the loop between builders and customers, why observability and support are product superpowers, and how to stay disciplined when agents tempt you to ship huge diffs overnight.

They go deep on watching users work, firehose social feedback, partnering with support, and why “make pain painful” aligns incentives for better software.

Dillon’s path runs from internal insurance tools to Vercel Domains to Cloudflare’s agent and dashboard work—always with the same through-line: care about the user, get real feedback, and invest in primitives so delighters don’t collapse under bad foundations. This episode covers metrics and paging as a product habit, learning from customer escalations, scoping small when AI speeds up coding, and building cross-functional relationships (support, sales, finance) as part of engineering judgment.

You’ll hear practical parallels with episodes on delighters and onboarding tension, plus why reviewing agent-written code still matters for system intuition when things break at 2 a.m.

Homework

Try hard and care a lot; more practically, focus on foundations and primitives. Put good feedback systems in place so you know what’s going on with your product and where it doesn’t feel good—alerting and metrics, customer journey signals, or customer interviews. If you have a customer support team, sit with them and watch them triage cases for your product; get to know support—they’re sitting on a gold mine of product signal—and empathize with them like you do with users. Kent’s shorthand for the mindset Dillon agreed with: make pain painful—if your users are hurting, you should feel it too.

Resources

Cloudflare — Developers Cloudflare Agents Dillon Mulroy — site Dillon Mulroy — GitHub

Guest: Dillon Mulroy

Company: Cloudflare GitHub: @dmmulroy 𝕏: @dillon_mulroy

Host: Kent C. Dodds

Website: kentcdodds.com 𝕏: @kentcdodds GitHub: @kentcdodds YouTube: kentcdodds-plus Podcast: epicproduct.engineer

See on Epic Product Engineer

More from Become an Epic Product Engineer

Oct 21, 2026

If you only get asked about feasibility, this episode is for you. Kent talks with Sam Julien - Director of Product at CopilotKit, author of Agentic GraphRAG - about moving past ticket-taking, collaborative product-engineering dialogue, and frameworks that help you push back with vocabulary. They cover leverage / neutral / overhead triage, Kagan's four big risks, communicating intent with AI agents, and why engineers need product models even when they have a PM.

Oct 14, 2026

If you ship features and never hear what users actually said, this episode is for you. Kent talks with Ben Vinegar - co-founder of Modem, formerly founding engineer and VPE at Sentry - about aggregating feedback, eliminating adoption barriers, and keeping human judgment in the loop as AI speeds up shipping. They cover FreshBooks-era product engineering, Modem's approach to capturing feedback across Slack, Discord, GitHub, and support tools, and why five real conversations beat a median LLM opinion.

Oct 7, 2026

If your backlog is full of tickets and zero customer contact, this episode is for you. Kent talks with Teresa Torres - product discovery coach, author of Continuous Discovery Habits, and host of Just Now Possible - about why engineers belong in discovery, what "just now possible" really means, and how curiosity beats solution advocacy. They cover opportunity solution trees, confirmation bias in decision-making, the Mom Test trap of pitching your solution, and homework that starts with one real conversation (or observing one).

Sep 30, 2026

If you still build for an audience of one and get defensive when users "use it wrong," this episode is for you. Kent talks with Mark Techson - staff developer relations engineer on Angular at Google - about empathy as a career differentiator, listening without defense, and why knowing what to build still beats vibe-coding forever. They cover internal tools as real products, a fitness-app failure that forced better questions, Google Developer Experts as a feedback loop, durable expertise in the AI era, and why attention is the scarce resource when anyone can ship. Mark Techson (legal name Mark Thompson) has spent about twenty years building software - teaching, senior engineering roles, a fitness startup, American Express fraud tooling, healthcare exchange apps, and now staff DevRel on Angular at Google. The views in this episode are his own; he notes he works for a major frontier-model provider. The through-line is empathy. Mark's number-one product-engineering skill is putting yourself in the end user's seat before you ship. Engineers who only implement tickets miss the concert of perspectives PMs, EMs, and builders bring when everyone aims at the best user experience. He compares great teams to a film set where talent still suggests a shoulder turn that makes the scene land. Listening without defense is the mechanism. Feedback means either you built it wrong or they cannot see how it works - both are actionable. Mark's hard lesson was a fitness app he built for himself: even his wife chose another app. Surveys flipped his assumption from "customize everything" to "just tell me what to do." At Google he leans on Angular GDEs and a simple reply to angry comments: tell me more. They also talk AI. Expertise is not going out of style - Mark uses a guitar-tuner analogy: auto-tune does not erase your ear. Knowing what to build, who to build for, and how to orchestrate agents matters more as code gets cheaper. Kent adds that human attention stays finite even if tokens get cheap. Mark closes against the "you're left behind" narrative: you do not have to live on the bleeding edge, but ignoring AI is the only wrong move. Homework: write a prompt for the first basic version of a product you have been postponing, run it in any AI tool, and notice what you failed to specify. Homework Pick a product idea you have postponed for lack of time or skill. Write a prompt that describes only the first basic version - not the million-dollar finished product. Run that prompt in any AI coding tool, then list what was missing from your prompt and iterate toward that first version. Resources Mark Techson Mark on X Mark on GitHub Mark on LinkedIn Angular Google Developer Experts Guest: Mark Techson Company: Google GitHub: @MarkTechson 𝕏: @MarkTechson Host: Kent C. Dodds Website: kentcdodds.com 𝕏: @kentcdodds GitHub: @kentcdodds YouTube: kentcdodds-plus Podcast: epicproduct.engineer Mark's views are his own. He notes he works for a major frontier-model provider (Google).

Sep 23, 2026

If execution got cheap and you still wait for someone to tell you what to build, this episode is for you. Kent talks with Joyce Er about five years owning features on VS Code, the jump to product at Cerebras, and why trust is the metric that tells you the work is working.

See all episodes →