Product Engineer

London / remote (UK) hybrid Post Date:
September 28, 2026

We're building the next generation of our behavioural finance platform, while continuing to support the current platform for existing enterprise clients.

As a Product Engineer, you'll play a crucial role in our user and product experience, owning larger, less-defined problems and shaping what should be built as well as how. Whilst you may have a natural inclination towards the backend or frontend, we expect you to have real breadth across the entire stack. You'll delve into all aspects of our tech stack and product portfolio, having meaningful impact on our customers, and the overall success of the business.

This isn't a full stack developer role in the old sense of "can write JS and PHP." It's about owning outcomes, not just implementing tickets. You'll work directly with the people who define what the product needs to do, product, research, and occasionally clients, rather than receiving fully specified requirements and building to spec. At this level, you're also expected to be a source of judgement for the rest of the team, not just for your own work.

• Building features end to end: API and service design on the backend, UI and component work on the frontend, connected together through our own middle layer
• Making judgement calls that shape entire feature sets, not just details within them, from architecture decisions to how ambiguous requirements get resolved
• Working with cloud infrastructure as part of normal delivery, not as a specialism
• Making heavy use of AI coding tools (code assistants, AI pair-programming tools) as a normal part of how you build, not as an occasional shortcut, we expect this to meaningfully raise how much you can ship
• Flagging when a requirement doesn't hold up, or when there's a simpler or better way to solve the underlying problem
• Working closely with a small team where there's no large product layer between engineering and decisions, you'll often be the one asking "does this actually solve the problem" rather than someone asking it of you
• Scoping work clearly enough that it can be handed to freelancers or contractors when we need extra capacity, writing the brief, defining the boundaries, and reviewing what comes back

Tech stack:

• Backend:
  Laravel/PHP, microservices architecture, BFF (Backend for Frontend) pattern
• Frontend:
  React, SPAs
• Cloud: AWS (Lambda, Glue, S3, Bedrock, Cloud Front)
• Data:
  Power BI, AWS data lake, Hub Spot (CRM)
• Tooling:
  Jira, Confluence, Git Hub

• Genuinely strong coding ability across the stack. This isn't a role where AI tools substitute for being a good engineer, it's one where a good engineer uses them to work faster, so you need to be someone who'd be strong here with or without them
• Real fluency with AI coding tools as well, and an expectation that using them well is core to the job. We move fast, and we're looking for people who can turn that speed into shipped, well-considered work, not just more output
• Real thinking about abstractions when you build: what belongs where, what should be reusable, what will bite us later if it's done the fast way now. AI can write code quickly, we need people who still think about the shape of the system underneath it, and who can tell when what it's produced is actually right
• A track record of owning larger, less-defined problems, this might show up as owning a feature from idea to production, pushing back on a spec that didn't make sense, or shaping a solution rather than just following one
• Comfort with genuine ambiguity, at this level you'll often be the one deciding what should be built, not just how
• Genuine curiosity about the product and the users, not just the code
• We're less…