What Is Product Engineering

Product engineering is the intersection between product management and software engineering. It is not neccessarily a job title (though it can be) but a role played by product builders who operate across the entire product development lifecycle.

The Lifecycle of Product Development

In order to build a successful product that solves a real problem for some users, several activities need to happen together. From understanding and researching a problem, designing a product solution, validating that solution, writing code, iterating on that code, and then supporting the product in production. Typically, organisations that build software products have assigned different human beings to each step in this process. Understanding the problem and designing a potential solution was seen as one of the core activities of a product manager. Writing code and supporting it in production was seen as the responsibility of software engineers. Product Engineering brings these activities together, enabling every member of a product engineering team to own and be held accountable to the success of every stage.

Removing The "Handover"

Under an operating model in which validation, discovery, and product design are the responsibility of product managers alone, changes or new features in a product are captured into words and handed over to software engineers. An epic, a product requirements documents, or a specification, are all examples of artifacts that attempt to capture the changes required in a product in high enough fidelity that the work can be picked up by software engineers and turned into working code. A Product Roadmap is often use as the mechanism for communicating a set of changes (or "initiatives") that make their way from product management to engineering. The responsibility of product managers is to create a well scoped and defensible roadmap, the responsibility of software engineers is to execute that roadmap relibably and predictably.

Product Engineering removes this handover step.

By enabling every individual on a product engineering team to operate across the entire lifecycle, engineers can research, propose, design and then execute their own solutions to user problems. Product managers can use coding tools such as Claude Code to remove the reliance on engineering teams to turn an idea into working code. The inidividual skills are still important of course (a product manager with Claude Code will often still need a software engineer to produce reliable production software, a software engineer will still lean on product managers for strategy, guidance and customer insight) but by blurring the line in this way every individual can become empowered to deliver change in a product.

Consultation Not Reliance

Under a Product Engineering model, expertise is seen as a resource not a blocker. A software engineer researching an idea for a solution to a user problem can consult and utilise expertise from product managers who understand the problem deeply, whilst retaining the owership of the solution themselves. Equally a product manager who has a well understood idea for a change in the software can utilise the expertise of software engineers who deeply understand how the code works, without neccessarily waiting for permission in order to submit a pull request. By working together, product managers, software engineers, and those with the hybrid "Product Engineer" job title can all become empowered to drive change without being blocked by sign-off steps and handovers.