From designing to building: The rise of product design engineering with David Siren Eisner
11/05/2026As AI makes it easier to turn ideas into working products, designers have an opportunity to rethink where their responsibilities begin and end. Lou talks with David Siren Eisner, author of the forthcoming Product Design Engineering: A Designer’s Guide to Building and Shipping Code with AI, about how AI is reshaping the boundaries between design and engineering.
David explains why traditional handoffs often create friction, lose valuable context, and slow product development. As roles blur, he sees opportunities for designers to take greater ownership of features from initial research through implementation, while teams rethink how they collaborate and maintain quality.
For designers wondering where to begin, David offers practical advice, which his book details: learn the fundamentals of engineering workflows, start with small coding projects, and build confidence through experimentation. Rather than turning designers into engineers, product design engineering extends the creative process, allowing designers to use code as another material for bringing their ideas to life.
David’s book arrives in November 2026.
What you’ll learn from this episode
- What product design engineering is and how it builds on traditional design practices
- Why maintaining context across design and development reduces friction
- How blurring roles are changing team structures and feature ownership
- Why faster development requires stronger quality standards and upfront alignment
- How designers can get started with coding, Git, and engineering workflows
- Why coding can be a creative extension of design rather than a separate discipline
Q&A with David Siren Eisner
Q: What is product design engineering?
A: Product design engineering extends the design process into building and shipping working software. Instead of treating implementation as the point where design ends and engineering begins, I see an opportunity for designers to carry their thinking further into the product itself. The goal is not to turn every designer into an engineer. It is to make code another creative material designers can use to bring ideas to life, alongside the methods and tools they already use. AI makes that possibility more accessible, but the underlying purpose remains the same: expressing design thinking through what we build.
Q: How is AI changing the relationship between design and engineering?
A: AI makes it easier to move from an idea to a working product. That gives us a reason to reconsider where design responsibilities begin and end, rather than simply applying new tools to the same division of labor.
For designers, the opportunity is to participate more directly in implementation. For teams, it is to rethink how design and engineering collaborate, share context, and maintain quality as building becomes faster. The important change is not just how much we can produce; it is how we organize ourselves to produce the right things.
Q: Why do traditional design-to-development handoffs create friction?
A: Traditional handoffs can separate the people implementing a product from the context behind its design. When work moves between roles, valuable understanding can be lost, and that creates friction in product development. A lot of the work we do benefits from someone who can maintain context across the process. When the thinking behind a feature stays connected to its implementation, there is less distance between understanding a problem and building a response to it. That continuity is one of the central opportunities in product design engineering.
Q: How can product design engineering preserve context from research through implementation?
A: Product design engineering gives designers an opportunity to take greater ownership of a feature, from the initial research through implementation. Rather than passing the work along at a fixed boundary, a designer can remain involved as an idea becomes working software. That does not mean one person should do everything. It means we should reconsider boundaries that interrupt useful continuity. The objective is to preserve the understanding developed during design while continuing to collaborate with the people needed to build well.
Q: Why does faster AI-assisted development make design alignment more important?
A: The faster we can build, the more important it becomes to make sure we are building the right thing. Increased output does not remove the need for design judgment; it makes that judgment more consequential.
If engineering output accelerates dramatically, teams need to keep their understanding of what should be built aligned with that speed. Upfront alignment and clear quality standards matter because the ability to produce more software is not, by itself, a reason to produce it.
Q: How can teams maintain design quality while building faster with AI?
A: Teams need to establish design quality standards and align before building. Faster development should not mean leaving the definition of quality until after implementation.
I see quality and speed as connected responsibilities. As the pace of building increases, teams need a shared understanding of what they are trying to achieve and the standard the work must meet. Product design engineering is an opportunity to rethink how that responsibility is maintained across design and implementation—not to bypass it.
About our guest
David Siren Eisner is VP of Product Design at Datadog and a product design leader with more than 25 years of experience working at the intersection of design and engineering. His work focuses on helping designers gain the skills to build more of what they design.
Previously, David held design leadership roles at Amazon, Amwell Healthcare, and Huge. He is also the founder of CraftAmplify (craftamplify.com), where he teaches designers how to build, test, and ship production-quality frontend code.
David holds a B.S. in Interactive Media from Carnegie Mellon University and an M.A. in Media Design from Keio University in Japan. A lifelong builder and explorer, he enjoys emerging technology and planning his next travel adventure.
He is also the author of Product Design Engineering: A Designer’s Guide to Building and Shipping Code with AI.
Quick reference guide
0:10 – Meet David and learn about his new book, Product Design Engineering: A Designer’s Guide to Building and Shipping Code with AI
4:18 – Maintaining context across design and development reduces friction
8:32 – Reducing context handoffs by rethinking design and engineering boundaries
11:48 – Redefining team boundaries around features rather than roles
14:25 – Establishing design quality standards and aligning before building
18:56 – Bloomberg LP’s UX team is hiring
20:08 – Getting designers started with coding through engineering fundamentals and hands-on practice
26:33 – Using code as a creative design tool, not just an engineering skill
29:58 – David’s gift for listeners
Resources and links from today’s episode:
Product Design Engineering: A Designer’s Guide to Building and Shipping Code with AI by David Siren Eisner
