What is a product engineer, and how is that different from a programmer?

A product engineer is an individual who is responsible for ensuring a digital product functions properly and meets the business requirements, rather than merely coding the requested features. After understanding the business needs, defining the project scope, designing the solution, and writing code, they are accountable for the product's launch and ongoing maintenance. This contrasts with a programmer, who, by definition, follows a defined task and executes it effectively.

Founders frequently inquire about the distinction between these roles when considering hiring. Picking the incorrect role can lead to costly consequences, surpassing the errors made when selecting the wrong technology. The tl;dr version is that a programmer executes predetermined tasks, while a product engineer determines what should be built, constructs it, launches it, and assumes responsibility for the outcome.

In the absence of someone defining the product's initial version and what not to include, the role of a product engineer becomes essential. If a company already possesses a CTO or a technical lead who determines the product's direction, a proficient programmer is what is needed. Over-hiring also presents a problem. The essence of a product engineer's role is to be accountable for the product's existence, functionality, and continuous operation, as opposed to merely assigning tasks.

This responsibility begins prior to a task's creation, during discussions about what is deserving of development, and ends after the product has been in use among real users for several months, with someone having to decide on fixes, measurements, and future improvements. The role's uniqueness lies in the starting and ending points of responsibility, rather than the list of tasks.