This is not your typical Product Owner role - Moorepay is transforming. We are rebuilding our HCM solution offering from the ground up — combining HR, Workforce Management, and Payroll into a single, AI-native system that will redefine how UK employers manage their people. This is a genuine greenfield opportunity: new architecture, new ways of working, and a product team that is rethinking every assumption about how software gets built.
You will join us at the moment the blueprint becomes reality. The platform strategy is set. The operating model is defined. And we are now building the pods that will bring it to life.
This is the kind of product work that most people only get to read about.
The Opportunity
We are building our product organisation around an AI Pod model — small, autonomous, cross-functional delivery units, including Engineering, QA, UX and of course Product, each accountable for measurable outcomes rather than feature output. As a Product Owner, you will sit inside one of those pods as a full delivery member, not as a liaison between the business and engineering.
You will work within an AI-first software development lifecycle. That means engineers generating code from structured specifications you help create, AI tools accelerating build cycles that would previously have taken months, and a delivery cadence that demands clarity, precision, and genuine product thinking — not process management.
Your role is to translate the strategy and workstreams set by the Product Manager into AI-executable outcomes — defining what gets built, why it matters, and exactly what done looks like — and then driving it to delivery inside your pod.
The Environment
You will be based in our St Julian's office in Malta, working alongside a talented and growing product and engineering team in a collaborative, largely office-based environment. St Julian's is one of Malta's most vibrant areas — a short walk from the seafront, with a strong technology community and a quality of life that is genuinely hard to match. You will also interact with AI Pods in the UK both for payroll and our broader product suite.
This is not a remote-first role. We believe the kind of collaborative, fast-moving product work we are doing is best done together as a Pod — in the same room, on the same problems, building the kind of shared understanding that PRD documents and Slack threads cannot replicate.
Occasional travel to UK offices for workshops and team events will be required.
Why This Role, Why Now?
Most product roles ask you to manage a backlog inside a product that already exists. This one asks you to help build something that does not exist yet — a unified, AI-native HCM platform that will change how UK employers manage their people.
You will not be inheriting someone else's decisions. You will be making them. The context hierarchy you contribute to will outlast your first workstream and inform every pod that works in your domain after you. The outcomes you deliver will be measurable. The platform you help build will be genuinely new.
If you want to work on a product that matters, in a team that is serious about building it well, at a moment when the opportunity is still wide open — this is the role.
What You Will Do
Own outcomes, not stories - You are accountable for a measurable behaviour change in the product, not a list of completed tickets. You will define the outcome your pod is delivering, set the success signals that determine whether it has been achieved, and validate that the change is real — in production, with real users.
Define design intents with your UX Designer - Before any specification is written, you will work with your pod's embedded UX Designer to define the user journeys, interaction principles, and edge cases that govern the feature. Design intent is a hard constraint on the build — not a late-stage review.
Author executable specifications (PRPs) - In our AI-first delivery model, features are specified as Product Requirement Prompts (PRPs) — structured, machine-readable documents that engineers feed directly into AI code generation tools. You will co-author these with your Senior Engineer, ensuring they contain the context, intent, acceptance criteria, and constraints that the AI generation process needs to produce correct, architecturally coherent output. A well-written PRP is the single biggest lever on delivery quality.
Maintain workstream context - You will work within a structured context hierarchy — Platform, Domain, and Workstream Context Documents — that gives engineering the accumulated knowledge of the platform before a single line of code is generated. You will contribute to and maintain the workstream-level context for your pod's area of the product, keeping it current and accurate as delivery progresses.
Be the quality gate - You will review AI-generated output against the acceptance criteria you defined. You will validate that the feature behaves as intended — not just that it passed automated tests. You will sign off delivery before it ships.
Close the learning loop - After every release, you will measure whether the outcome was achieved. Findings feed back into the context documents, the backlog, and the next cycle. This is how the system gets smarter — and how your work compounds.