What if product managers, designers, and even VPs of Engineering are "pure overhead"? Martin, VP of Engineering at Zen Educate, makes the provocative case that engineers could technically build and maintain a product without anyone else—so every other role needs to prove they're accelerating engineering, not blocking it. His journey from building VFX pipeline tools in the film industry to leading product-led teams at Intercom shaped his conviction: engineers who love solving real user problems (and just happen to use technology) are the ones who sometimes solve problems by not building anything at all.
In this episode, we explore why "problem shapers" beat "ticket takers," how Zen Educate transformed from a world of PM-assigned tickets to engineers partnering directly with commercial leaders, and why a team of six engineers working on six different problems isn't a team—it's just people sitting together. Martin doesn't hold back on the trade-offs, the challenges of getting engineers to believe they're allowed to do this, and the practical steps for anyone trying to make this shift.
---
GUEST
Martin Östlin - VP of Engineering at Zen Educate
Martin started his career in the film industry building pipeline tools for visual effects teams before discovering product-led development at Intercom. Now he leads engineering at Zen Educate, a British startup tackling the global challenge of education staffing. He's leading the transformation from ticket takers to problem shapers across a distributed team of 40+ people.
Find Martin:
- LinkedIn: https://www.linkedin.com/in/martinpp/
- Zen Educate: https://zeneducate.com
---
TIMESTAMPS
00:00 Introduction and Welcome
01:51 Martin's Journey Through Film Industry and Tech
04:16 Before Product-Led: The World of Feature Requests
06:16 Frustrations of Being a Ticket Taker
08:43 The Aha Moment at Intercom
13:06 Leadership's Role in Fostering Product Mindset
18:35 Problem Shapers Not Ticket Takers - What It Means
23:10 Measuring Collaboration and Team Health
26:11 How Teams Are Structured at Zen Educate
28:02 A Typical Week for Engineers
30:48 How Problem Shaping Works in Practice
33:47 Handling Handoffs Between Roles
36:34 The Impact of AI Tools on Their Workflow
43:51 Challenges in the Transformation Journey
48:06 Scaling This Approach as the Company Grows
51:24 Practical Steps to Start Implementing Product Engineering
56:01 Where to Find Martin
---
KEY TAKEAWAYS
1. Engineers are the only required role - you can build and maintain a product without PMs, designers, or VPs. Everyone else is "pure overhead" that must prove they accelerate engineers rather than slow them down.
2. Problem shapers vs ticket takers - engineers at Zen Educate define problems with the team, challenge assumptions, and contribute solutions. They're not waiting for PM-written tickets or asking for sign-off before shipping.
3. Product engineers solve problems by NOT building - the best definition: "Someone who loves solving real problems for users and just happens to be skilled at leveraging technology." Sometimes the answer is zero lines of code.
4. Teams need focus to be teams - six engineers working on six different problems aren't a team, they're just people who sit together. Real teams rally around shared problems with clear accountability.
5. Three steps to implement this: (1) Internalize why you want this (not just because it sounds cool), (2) Write it down with clear trade-offs, (3) Find champions who get it and amplify their wins publicly. Start small or go big depending on your context.
---
RESOURCES MENTIONED
- Intercom (Martin's previous company)
- Lovable (AI prototyping tool)
- Figma (design tool)
- Marty Cagan's article on "product builders"
- Developer experience surveys
- Session replays and product metrics tools
- Extreme programming concepts
---
CONNECT WITH PRODUCT ENGINEERS
Host: Peppe Silletti
LinkedIn: https://www.linkedin.com/in/peppesilletti/
Product Engineers Community:
Website: https://productengineers.com
LinkedIn: https://www.linkedin.com/company/product-engineers
---
SUPPORT THE SHOW
If this episode challenged how you think about roles and ownership, share it with an engineering leader who needs to hear it. Drop a comment below with your biggest takeaway or tell us about your own transformation from ticket taker to problem shaper.
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit
Fler avsnitt av The Product Engineers Podcast
Visa alla avsnitt av The Product Engineers PodcastThe Product Engineers Podcast med Peppe Silletti finns tillgänglig på flera plattformar. Informationen på denna sida kommer från offentliga podd-flöden.
