What I learned talking to the people at DOJO AI about "Product Engineer"
I talked directly with people at a company that hires Product Engineers, and treated those conversations as research.
Read the field noteGreat products happen where human needs, working technology, and a viable business meet.
The Product Engineer brings all three into focus—and turns the overlap into something real.
Explore the field guideStart with a signal, then with what people who do the work say, and the definition that comes out of it.
I talked directly with people at a company that hires Product Engineers, and treated those conversations as research.
Read the field noteFifteen public sources, one path that keeps coming back, and a working definition of the Product Engineer where those findings meet.
Read the field noteWhat the market is asking for: the roles, the companies, the expectations, and the different jobs hiding under one title.
77 postings titled Product Engineer, read against the definition that came out of the people who do the work: about half ask for all of The Product Engineer Path, and the step that goes missing is Learn.
Read the field noteFinancial pressure, flatter teams, and AI-assisted work — why this question is showing up now and not ten years ago.
Read the field noteThe same title covers very different work. What companies actually ask for, and how to tell a Product Engineer job from the usual software job with a new name.
PlannedConnect the evidence to the wider story: how engineers grow into the role, what changes with AI, and what the work looks like in practice.
Customer Development, Lean, Design Thinking and Agile each tried to bring tech, product and design together. What they got right, and why the silos stayed.
PlannedWhere engineers can focus as AI takes on more implementation work, the fears that come with widening the job, me included, what the evidence says about each, and where the hope is.
PlannedFive different career paths, and how engineers expand their scope toward customers and business outcomes without leaving engineering.
PlannedBring the research together in a practical model for building software around customer needs, sound engineering, and meaningful outcomes.
A proposed model connecting engineering craft, product judgment, customer understanding, design, business context, experimentation and ownership.
PlannedDesign gives it meaning.
Technology makes it real.
Business makes it matter.
Field Notes is a newsletter on Product Engineering: what practitioners do, what companies ask for, and the data behind each claim. Subscribe and get each new note by email.
Enable JavaScript to subscribe, or get in touch by email.