Shape scope and technical direction before implementation becomes expensive.
Product engineering · Open role
Principal Product Engineer
Own complete product slices across interface, application logic, services, data, and production—not a narrow queue of frontend or backend tickets.
This role is for an engineer who can turn an ambiguous product problem into a coherent production system. You will work directly with product, design, clients, and other senior engineers, moving between interaction details and architectural decisions without treating either as someone else’s problem.
Build accessible React and Next.js interfaces backed by well-designed services and data models.
Make sensible boundaries across Java and Spring Boot services, APIs, integrations, and cloud infrastructure.
Review work across the stack and raise the quality of product and engineering decisions around you.
Carry releases through testing, observability, production rollout, stabilisation, and handover.
Several complex products or critical workflows you personally helped take from ambiguity to production.
Strong judgement in TypeScript, React, application architecture, APIs, relational data, and distributed-system trade-offs.
The ability to read and improve Java code—or the depth to become productive in the JVM ecosystem quickly.
Clear written and spoken communication with technical and non-technical decision-makers.
A habit of reducing complexity while preserving the business rules that actually matter.
Probably not for you if
A senior title is the goal, but hands-on ownership is not.
- You want a role confined to one layer of the stack.
- You measure seniority by distance from implementation.
- You need every requirement resolved before you can move.
Show us how you think.
Send a short note, relevant work, and one difficult problem you personally owned. Skip the polished cover letter. Specific evidence is more useful.
Apply for this role ← Back to all roles