Great 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 instead of five years ago.
PlannedCompany size and company stage aren't the same measurement — where these jobs actually sit, by stage, regime, pay, and visa eligibility.
PlannedWhat recurs across 77 postings: product sense, ownership, speed. And three different things "AI" can mean in a posting.
PlannedArticle 2 showed one title hides eight jobs. This time I go archetype by archetype — including one pattern that only shows up outside Portugal.
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.
How engineers can expand their scope toward customer and business outcomes without leaving engineering.
PlannedA look at the older practices and movements behind the ideas now grouped under Product Engineering.
PlannedWhere engineers can focus as AI takes on more implementation work: judgment, evaluation, context and ownership.
PlannedThe fears and doubts engineers, me included, have about widening the job toward users and decisions, what the evidence says about each, and where the hope is.
PlannedFive different career paths, and what they suggest about how people arrive at this kind of work.
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.