What a Product Engineering Lead Does, and When to Hire One
A product engineering lead owns a product from the first question to the running service. How it differs from a product manager and a tech lead.
"Product engineering lead" is my job title, and it often needs explaining. It sits between two roles most organisations already know, the product manager and the tech lead, and takes on a large part of both. This post explains what the role involves, how it differs from those two, and when it is the right hire.
The short version
A product manager decides what to build and why. A tech lead decides how to build it and leads the engineers who do. A product engineering lead does both for one product, and builds a good part of it too.
In practice, that means one person is accountable from the first conversation about the problem to the service running in production. The role is common in small teams, startups and charities, where there is not room for a separate product manager, tech lead and senior engineer on every product.
What the work looks like
On the platforms I have led, the work falls into four parts.
Finding the real problem. Sitting with the people who run the service, whether that is a charity's digital team, an education team or an operations team, and separating what they ask for from what they need. On a fostering profile platform, that meant working with the charity's digital team to understand what carers, social workers and children each needed from a profile.
Shaping the product. Deciding what comes first and what waits, in a way that fits the organisation's budget and pace. When a computing charity rebuilt its schools platform, much of the work was deciding what to leave out.
Building and shipping it. Planning the work, writing a large share of the code, reviewing the rest, and getting it into production. The difference from a product manager is that the plan and the code are held by the same person, so nothing is lost between them.
Keeping it running. Owning the service after launch: fixing what breaks, handling platform and device changes, and moving it onto better foundations without switching it off. Moving a business off InventoryBase while its staff kept working is the clearest example from my own work.
How it differs from a product manager
A product manager usually works across several engineering teams and does not write production code. Their strength is breadth: discovery, prioritisation and stakeholder management across a larger product area.
A product engineering lead goes deeper on one product. The advantage is speed and fidelity. When a service owner asks whether something is possible, the answer comes from someone who knows the codebase, and a decision in a meeting becomes a working change without being translated through several people.
The cost is range. One person can only hold so much, so the role fits one product or a small group of related ones.
How it differs from a tech lead
A tech lead owns technical decisions and the engineering team's delivery, but usually takes the product direction from someone else. A product engineering lead sets that direction with the people who own the service, then carries it through the engineering.
That makes the role more exposed. The lead has to be comfortable in a room with service leads and partners, as well as in a code review.
When to hire one
The role fits when:
- the product is small or medium, and cannot justify a separate product manager and tech lead;
- the problem is hard to understand without the technical detail, for example a data migration, an integration-heavy service or a platform that has grown for years;
- the organisation needs one accountable person from idea to running service;
- the team is small, and the lead will be building as well as deciding.
It fits less well when the product is large enough to need several teams, or when the organisation already has strong product management and needs engineering leadership only.
What to look for
Look for someone who can show both halves with real examples: a product decision they made and why, and a system they built and still understand. Ask how they worked with the people who own the service, and what happened after launch.
If you are hiring for a product engineering lead, technical product lead or product manager role, my CV has the detail, and I am happy to talk.