The technical person in the room - product engineering with Sean Roberts

Kent talks with Sean Roberts, engineer at PhotoShelter, about product engineering shaped by agency work and small teams: being the technical person in sales conversations early, planning with product judgment, and knowing when to speak up (and when to listen). They discuss why implementation skill still matters in the AI era, how to avoid "vibes-only" product calls, budgeting and sequencing work with business context, and why striking up real conversations (with customers or anyone) is a trainable muscle. 00:00 - Introduction to Product Engineering 02:11 - Agency work and customer conversations 08:47 - The technical person in the room 16:54 - Determining business goals 26:48 - Planning and the dark forest 35:10 - Relationships and positive feedback 40:21 - Homework: talk to someone new Sean's path is a familiar pattern for this season: years of agency and startup work where engineers sit close to customers, budgets are real, and the person writing code is often in the room when the problem gets defined. He describes learning to ask questions on sales calls as a junior developer, sometimes literally driving the founder to the meeting, and translating needs into feasible software on the spot. The middle of the episode turns toward planning inside a product company: helping teams separate solved problems from "dark forest" work, pushing back on specs that underestimate legacy complexity, and bringing beginner's mind even when you are senior. Sean is honest that much of his product sense today is still conversation-driven, and he wants better analytics to complement that, not replace it. Kent and Sean also touch the emotional side of the job: positive feedback when you save someone tedium, the risk of changing UX too often because you are bored, and why relationships matter if you want to hear "you made my life easier." The homework is deliberately low ceremony: talk to someone you do not normally talk to and practice curiosity. Homework Ask someone you do not normally talk to at work for 15 minutes: a salesperson, PM, support lead, or another engineer on a different team. Ask about their job, challenges, and customers; practice translating what you hear into software constraints without jumping to solutions too fast. If work feels awkward, practice the same muscle outside work (cashier, server, neighbor) - the goal is conversation comfort, not a formal interview. Resources PhotoShelter ( https://www.photoshelter.com/ ) Sean Roberts - GitHub ( https://github.com/seanroberts ) Guest: Sean Roberts Company: PhotoShelter ( https://www.photoshelter.com/ ) GitHub: @seanroberts ( https://github.com/seanroberts ) 𝕏: @sean_j_roberts ( https://x.com/sean_j_roberts ) Host: Kent C. Dodds Website: kentcdodds.com ( https://kentcdodds.com/ ) 𝕏: @kentcdodds ( https://x.com/kentcdodds ) GitHub: @kentcdodds ( https://github.com/kentcdodds ) YouTube: Kent C. Dodds (    / @kentcdodds-vids   ) Podcast: epicproduct.engineer ( https://epicproduct.engineer ) See on Epic Product Engineer ( https://www.epicproduct.engineer/the-... ) Become an Epic Product Engineer Episode 15 June 17, 2026 ★ Episode details: https://share.transistor.fm/s/3befb0d2 ★ Additional episodes: https://www.epicproduct.engineer/beco...