From Engineering to Product Leadership
An engineering background as a product advantage.
Summary
Using a software engineering background to make better product decisions, bridge technical and commercial stakeholders, and move from implementation ownership toward product and organisational leadership.
Context
My path did not start in product. It started in code — as a developer, a frontend engineer, and then Head of Frontend — before moving into product management and product leadership. That history is not a footnote; it is a large part of how I work.
The challenge
Carry the value of an engineering background into product leadership without staying stuck in implementation — using technical judgement to lead, not to micromanage.
My role
- Bringing engineering judgement into product decisions
- Bridging communication between technical and commercial stakeholders
- Moving from implementation ownership toward product and organisational leadership
Approach
Judgement, not control
Used technical understanding to ask sharper questions and make better trade-offs — while leaving the how to the engineers who own it.
Translate both directions
Acted as a bridge between technical and commercial stakeholders, so feasibility and business intent could actually meet in the middle.
Widen the scope deliberately
Moved from owning implementation toward owning product direction and organisational structure, expanding responsibility rather than clinging to the code.
Key decisions
Let go of the keyboard
Chose to lead through people and decisions rather than by staying the person who builds — the hardest and most important shift in the transition.
Keep the technical honesty
Held onto the engineering habit of pressure-testing feasibility and quality, and brought it into product conversations where it was often missing.
Outcome
- →Product decisions that hold user value, business value and technical reality together.
- →Smoother communication between technical and commercial stakeholders.
- →A move from implementation ownership toward genuine product and organisational leadership.
What I learned
An engineering background is a superpower in product — right up until it becomes a comfort zone. The value is in the judgement it gives you, not in staying the person who writes the code.
Next case study — 01
Building a Product Organisation
Want to talk through a problem like this? Get in touch