I talked with Sean Roberts about product engineering shaped by agency work and small teams: sitting close to customers, budgets that are real, and learning when to speak up.
Sean is an engineer at PhotoShelter now, but much of his product sense came from years where the person writing code was often in the room when the problem got defined. He described 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.
Planning with product judgment
The middle of the episode is about 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. That felt realistic. Product engineering is often a mix of lived context, relationships, and whatever signal you can get from data when it exists.
Conversation is a trainable muscle
Kent and Sean also touched 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. That is product engineering work even when no code ships.
