02 Mar 2026
by Chris Southam

From web developer to product engineer: The shift no one explains

Over the years, I’ve interviewed a lot of developers. Many are bright, curious, and good at what they do. But when conversations turn to ownership, long-term impact, or how their work affects users, there’s often a pause. That isn’t a lack of ability. It’s a lack of exposure. 

I recognise it because I felt it myself earlier in my career. I cared deeply about writing good code, but when I moved into product-led teams I realised the expectations were broader than I expected. I was being asked not just how to build something, but why it existed, how it might fail, and what impact today’s decisions would have over time. No one had clearly articulated that side of the role. 

Years later, when I moved into hiring at Signable, I started noticing the same pattern. Talented developers with real potential, but without exposure to that broader way of thinking. That insight led me to start writing publicly through my Developer to Engineer LinkedIn newsletter, where I share the lessons I wish I’d had earlier in my own career. 

National Careers Week feels like a natural moment to zoom out. In tech, many early-career paths - from freelancing to agency roles - tend to focus heavily on technical execution, even though working in product-led teams requires a much wider skill set. We talk about “junior”, “mid-level”, and “senior” roles as though progression is about time served or technical depth, when in practice the real shift is perspective - understanding how your work connects to users, the wider business, and the long-term health of a product. 

You can see that shift in how people approach their work. In a product environment, success isn’t just about delivering what’s been asked for. It’s about taking ownership, being comfortable with uncertainty and making decisions that balance short-term needs with long-term consequences. 

Over time, engineers start asking different kinds of questions:  

  • Does this actually solve the user’s problem?  
  • What are we trading off by doing it this way?  

These aren’t elite skills. They develop through exposure and responsibility. The industry doesn’t suffer from a shortage of talented developers; it often suffers from a shortage of clarity about what growth really involves. 

Another shift that surprises many early in their careers is how central communication becomes. In interviews, the strongest candidates aren’t always those describing the most complex systems, but those who can articulate why decisions were made, what alternatives were considered, and what they would improve next time. 

So what’s worth taking away from this? 

If you’re early in your career, look beyond the task in front of you. Ask why something exists and what impact it has. When you finish a piece of work, reflect on what problem it solved and what might break if usage doubled tomorrow. Those small habits build perspective over time. 

If you’re hiring, supporting, or educating early-career talent, clarity matters. Are expectations clearly defined, or are they assumed? Showing what tech work really looks like - not just writing code, but collaboration, trade-offs, and long-term thinking - makes progression more accessible and fair. 

If we want a more inclusive and sustainable tech industry, we need to stop assuming that product thinking is something people will “just pick up”. We need to teach it deliberately, talk about it openly, and design career pathways that make those expectations visible. 

The transition from developer to product engineer isn’t about being more talented. It’s about broadening perspective and learning to think about impact. When we make that shift clearer and more deliberate, we give more people the confidence to grow into it. And when growth feels visible rather than mysterious, we build stronger teams and more sustainable careers. 


  TechTogether - Hubpage CTA

About the campaign

techUK’s TechTogether campaign, taking place throughout March, is a collection of activities highlighting the UK’s technology sector pursuit to shape a more equitable future. In 2026 we are exploring: Inclusive AI, investing in diverse founders and entrepreneurs, the power of allyship and mentorship, and empowering young people. 


Career related industry insights:


 

Skills, Talent and Diversity updates

Sign-up to get the latest updates and opportunities from our Skills, Talent and Diversity programme.

 

Here are the five reasons to join the Skills, Talent and Diversity programme

Download

Join techUK groups

techUK members can get involved in our work by joining our groups, and stay up to date with the latest meetings and opportunities in the programme.

Learn more


Women in Tech Widget Cards

Other opportunities to get involved:


Other related insights:


 

Authors

Chris Southam

Chris Southam

Head of Engineering, Signable

Chris Southam is Head of Engineering at Signable, where he leads the team responsible for building and running the platform - keeping it fast, secure and dependable for thousands of users. He works closely with product and customer teams to make sure the technology doesn’t just look good on paper, but actually solves real problems. With an extensive background in SaaS, Chris is passionate about building high-performing teams and creating software that behaves itself in the real world. Outside of work, Chris is outnumbered at home by his two daughters (11 and 14), which keeps him on his toes and provides a daily masterclass in perspective.