Become an Epic Product Engineer

Use the product yourself - empathy, architecture, and PM partnership with Rita Kozlov

· Summarized

Share this episode
Anyone with this link can open it.
Share Link
Start at 0:00

Key takeaways

  • Engineers can differentiate themselves by deeply understanding user experience and proactively inserting themselves upstream in product discussions.
  • Ownership and accountability are critical; understand your code and the full system to make responsible, thoughtful decisions.
  • AI accelerates prototyping but does not replace the need for thorough understanding and responsibility for the final product.
  • Effective product management starts with defining the right problem, not just solutions, and involves close attention to real user needs through direct interaction.
  • Deep understanding of the product and primitives enables engineers to expand the 'art of the possible' and drive innovation.
  • Teams should constantly use and test their products early and often to uncover issues and improve quality before shipping to users.

Summary

Introduction and Professional Background of Rita Kozlov

The episode begins with Kent C. Dodds introducing Rita Kozlov, VP of Product at Cloudflare. Rita shares her background as a software engineer, and how this experience influences her work in product management, especially in building developer tools like Workers, KV, and Pages. Her engineering background helps her empathize with developers and understand the intricacies of product decisions, making her approach to product management holistic and detail-oriented.

Blurring Lines Between Product Managers and Engineers, Impact of AI

The conversation explores how AI has changed the dynamics between product managers and engineers. AI enables rapid prototyping, which is powerful but can tempt teams to push out prototypes as if they were finished products. Rita emphasizes that ownership and accountability remain crucial; engineers must understand the end-to-end system, not just ship features. The blurring of roles is also related to the iterative nature of modern software development, which allows for more disposable development cycles while maintaining responsibility.

The Importance of Empathy: Sitting in the User's Seat and Art of the Possible

A key theme is the importance of empathy in product and engineering. Rita advocates for engineers to get closer to the customer through direct interaction, such as participating in customer calls, to identify real user problems beyond their assumptions. She introduces the concept of the 'art of the possible,' highlighting that understanding system primitives and limitations can expand what’s feasible in product development. This deeper understanding fosters innovation and better problem-solving.

Making Trade-offs and Strategic Product Decisions

The episode discusses how teams balance competing demands, such as launching a free tier versus premium features. Rita explains that trade-offs are often influenced by larger company strategies, customer needs, and timing. Early-stage products may justify delaying features to build core relationships, while mature products must carefully manage customization without introducing excessive complexity. Cloudflare’s approach focuses on leveraging primitives and paving paths, which allows flexible, scalable solutions.

Role of Engineers in Influencing Product Strategy

Rita emphasizes that engineers should strive to influence upstream decision-making by understanding customer needs, participating in discussions, and conveying implications of their work. Deep involvement helps engineers see beyond their narrow tasks and contribute to shaping the product vision. She encourages engineers to challenge solutions, explore the 'art of the possible,' and bridge the gap between implementation and user experience.

The Deep Impact of Deep-Stack and Internal Developer Experience

In discussing internal product development, Rita notes that engineers working on foundational systems still impact users because these systems form the interfaces and primitives that customers ultimately interact with. She highlights the importance of understanding the flow from deep systems to end-user experience and how decisions made deep in the stack can ripple outward. Collaboration among diverse roles—like those who understand distributed systems and developer experience—is essential for building impactful products.

Actionable Advice: Use Your Own Product and Push Limits Before Shipping

The episode’s concluding advice is simple yet powerful: engineers and product teams should actively use and experiment with the products they build, including features just shipped. This hands-on approach reveals unanticipated issues and understanding that cannot be gleaned from specs alone. Rita advocates for a culture of continuous feedback, urging teams to test in various modalities and push their products’ limits to ensure better quality, usability, and ownership.

Sponsors

  • Cloudflare · Visit Cloudflare at https://www.cloudflare.com to learn more about their developer platform and products like Workers, KV, and Pages.

Show notes

If you ship a feature and never click through it yourself, this episode is for you. Kent talks with Rita Kozlov, VP of Product for Cloudflare's developer platform, about the line between product managers and product engineers, why ownership still matters when prototypes look real, and how far upstream an engineer should insert themselves.

They cover holding the pager vs throwing away a prototype, sitting in customer calls until someone will not click the button, primitives vs paved paths, and what to do when your PM is running a feature factory.

  • (00:00) - Meet Rita Kozlov
  • (01:36) - Engineering taste in a PM role
  • (04:05) - Where PM and product engineer blur
  • (07:53) - You are not holding the pager
  • (09:48) - What AI changed on both sides
  • (13:40) - Sit in the user's seat
  • (17:04) - The art of the possible
  • (18:53) - Trade-offs and why not both
  • (23:22) - Primitives vs paved cow paths
  • (26:43) - Insert yourself upstream
  • (29:40) - When the PM is a feature factory
  • (33:17) - Deep-stack work still reaches users
  • (37:58) - Homework: go use the product

Rita Kozlov is VP of Product for Cloudflare's developer platform - Workers, KV, Pages, and the rest of the stack Kent uses constantly. She started as a software engineer, and that background shows up in the details: taste for developer experience, intuition for patterns that do not sit right, and a refusal to treat implementation as someone else's problem.

A major theme is how AI blurred the PM and engineer line. Prototypes are worth a million words, and they create a temptation to ship the facade. Rita's reminder to her product team: you are not the one holding the pager. Accountability is not about having someone to call at 2 a.m. It is about living with the code for the next two years. Product engineers close that gap by translating implementation trade-offs, filling the holes a PRD will never list, and sitting in the user's seat - including the customer call where nobody clicks the button.

They also get into Cloudflare-shaped product judgment: most doors swing both ways if you wait; early customers are worth delaying a launch for; primitives can serve many jobs, and sometimes you still pave a cow path. Rita wants PMs to define the problem, not the solution. Engineers should get closer to customers, challenge a feature-factory PM with why, and remember that even work deep in the stack - cache, TTL, the interface between systems - is user experience.

Homework is basic on purpose: go use the product, including the feature you just shipped, and push it before you throw it over the fence.

Homework

  • Use the product you work on this week - not as a demo path, as a real user.
  • After you ship a feature, try it in the different modalities and push the limits before you hand it off.
  • Write down what you found that you would have missed from the ticket alone.

Resources

Guest: Rita Kozlov

Host: Kent C. Dodds

See on Epic Product Engineer

Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account

Couldn't load the audio. A blocker may be stopping the show's tracking links. Open the file