I sat down with Mark Techson - staff developer relations engineer on Angular at Google - for Become an Epic Product Engineer. Mark has been shipping for about twenty years: teaching, American Express fraud tooling, healthcare exchange apps, a fitness startup, and Angular DevRel. His views are his own; he was clear he works for a major frontier-model provider.
His number-one product-engineering skill is empathy. Before you ship, ask how it would feel to use. Engineers who only clear tickets miss the concert of perspectives on a team that actually cares about the user experience. Mark's film-set analogy stuck with me: the best moments happen when writers, directors, and talent share one goal - not when everyone stays rigidly in their lane.
The practice that unlocks that is listening without defense. When someone says your UI is wrong, either you built it wrong or they cannot see how it works. Both are actionable. Mark learned that the hard way with a fitness app he built for himself - even his wife chose another app. User surveys flipped his assumption from infinite customization to "just tell me what to do." At Google he leans on Angular GDEs and a disarming reply to angry YouTube comments: tell me more.
We also talked about AI. Expertise is not going out of style. Mark's guitar-tuner analogy: auto-tune does not erase your ear for which string is sharp. Knowing what to build, who it is for, and how to orchestrate agents is the durable work. Even if tokens get cheap, human attention stays finite - you still have to pick what is worth building.
Mark's pushback on the "you're left behind" narrative: you do not have to live on the bleeding edge, but ignoring AI is the only wrong move.
Homework: pick a product you have been postponing, write a prompt for only the first basic version, run it in any AI tool, and notice what you failed to specify.
