Part 0 · 2 chapters · ~12 min

What a Product Engineer Is

The product engineer as an engineer who owns outcomes, the six habits, how the role differs from a feature-factory engineer and from a product manager, where companies hire for it, and how it shows up in staff-level work.

1

Six habits

The difference between a feature-factory engineer and a product engineer is not skill with code; it is where their responsibility ends. One stops at "merged"; the other stops at "the problem is solved".

WHAT A PRODUCT ENGINEER DOES
the habits that distinguish one
asks whyFinds the user problem and theoutcome behind each ticket beforewriting code.scopes smallProposes the smallest version thatsolves the problem and teachessomething.measuresDefines success before shippingand instruments it in the same PR.meets usersReads support tickets, watchessessions, joins interviews, everyweek.cares about feelLatency, copy, empty states, errorstates and defaults are part ofdone.follows throughChecks after launch whether itworked, and iterates or removesit.
swipe the figure sideways, or tap expand for full screen
1/6
asks why
A ticket says "add a CSV export". A product engineer asks who needs it and for what: often an accountant reconciling monthly, who would be better served by an emailed monthly statement.
find the job behind the requestthe ticket is a guess at a solution
2

Product engineer, PM and staff engineer

product engineerproduct managerstaff engineer
ownsoutcome of what they buildoutcome of the product areatechnical direction and quality across teams
spends time onbuilding, with discovery and measurement built indiscovery, strategy, alignmentdesign, review, unblocking, mentoring
overlapall three ask "what problem, for whom, how will we know?"