Moorepay is transforming. We are a trusted leader in UK Payroll and HR solutions, and we are now rebuilding our platform from first principles — not as a reskin, but as a genuinely new product designed around how SMEs actually work. We're building a team to deliver a sophisticated, intelligent environment that transforms how businesses handle complex compliance tasks, making them simple and intuitive.
We are seeking an experienced UX / Product Designer to join our growing UX chapter, responsible for delivering excellent, pod-embedded design across two product pods. The UX chapter is newly established, the design system is being built, and the pods are live. This is a hands-on design role — you will own the design of real, complex features and ship them well.
You'll work one sprint ahead of engineering across your two pods. When one pod is in build, you're designing for the other. The Senior Product Designer leads the chapter — owning the design system, running design crits, and setting the quality bar — while the Head of UX leads the people side: your line management, growth, and progression. You'll work within that system, contribute to it, and benefit from having a professional community behind you.
This is a full time, permanent role working 3 days per week in Manchester.
Why This Role Is Unique
Most product design or UX roles at this level in enterprise software are spent implementing patterns someone else decided on, inside products someone else designed. This is different.
- Domain depth over rotation. You'll be assigned to either the HR or Payroll domain and build genuine expertise in it. The model is deliberately structured to prevent designers being rotated away just as they become useful — your domain knowledge is an asset we'll protect.
- A chapter with a spine. You won't be the only designer. Shared standards, design crits, and a Senior Designer invested in your development mean pod work doesn't mean working alone.
- Work that matters at scale. Your designs will be used by thousands of UK businesses managing payroll and HR compliance. The stakes are real, and the standard of execution has to match.
- Leadership pipeline. As a founding member of this new function, you'll grow into formal leadership as the team scales. Designers who build domain depth and demonstrate good judgement here will be the natural candidates for senior roles. When senior roles open up on this team, they go to the people already doing the work — we're not looking to hire over you.
- Scale with stability. You get the meaningful problems and greenfield design work of a startup environment, backed by the distribution, domain expertise, and resources of a 500+ person company backed by Zellis Group.
The AI & Tooling Stack
We use a stack of tools that buy us speed and quality. What we care about most is your mindset and your exposure to each category of tool — not whether you've used the exact same product we have. Most AI tools within a category operate in broadly similar ways, and we'd rather hire someone genuinely curious about working this way than someone who happens to share our specific tool list.
- Design (including AI-assisted design): Figma is the foundation of our work, so advanced fluency in Variables and Dev Mode is essential. Alongside Figma, we use Figma Make and Claude Design for rapid ideation and initial design generation before finalising a direction in Figma. Experience with Google Stitch, Galileo AI, Uizard, or Lovart sits squarely in the same category.
- Prototyping (including AI-assisted prototyping): We use Cursor and Claude Code to build functional, high-fidelity prototypes when a static Figma file can't carry the idea on its own. Experience with Lovable, v0 by Vercel, Bolt, Google Antigravity, Windsurf, or any similar AI assisted prototyping tool transfers cleanly.
- Usability testing: Remote, unmoderated testing with real users before code is written. We're still evaluating the right long-term platform, so experience with Lyssna, UserTesting, Maze, UsabilityHub, Useberry, or any similar tool is directly relevant — and your perspective may help shape that decision.
- Behavioural analytics: Microsoft Clarity is live on our platforms and used for pod-level research and pattern validation — session recordings, heatmaps, and rage-click detection. Equivalent experience with Hotjar, FullStory, LogRocket, or Smartlook is just as relevant.
- AI for synthesis and writing: Claude is installed locally and used across the product and UX team for research synthesis, specification writing, and rapid iteration. Comfort with ChatGPT, Gemini, or other large language models in design and research workflows is just as relevant.
What we're really looking for is the mindset: someone who reaches for a prototype rather than a deck, validates with users before committing to code, and treats AI tooling as a multiplier on judgement rather than a replacement for it.
Key Responsibilities
Pod-Embedded Design
- Own the design of features within your two pods, from early exploration through to engineering-ready specifications. You'll work in a trio with the Product Owner and Tech Lead.
- Translate research evidence and product briefs into interaction designs that make complex HR and Payroll workflows feel manageable for non-technical users.
- Design across all meaningful feature states — happy path, empty, loading, and error — so features arrive at engineering complete.
- Own the micro-copy in your flows. In-product language is a design decision, not a copywriting hand-off.
- Design for trust. Payroll is high-stakes work, so reassurance, clear feedback, and error prevention are real features — not polish.
Specification and Handoff
- Co-author feature specifications with your trio before a sprint begins — covering user journeys across all states, interaction rules, content standards, and accessibility requirements.
- Define edge cases and failure modes explicitly within every specification. In a compliance product, undefined error states become support tickets and regulatory risk.
- Meet WCAG 2.1 AA as a baseline. Accessibility is designed in from the first iteration, not retrofitted.
- Aim to hand work to engineering ready to build that's what keeps the sprint-ahead model moving.
Design System Contribution
- Work fluently within the established design system. Lean on existing components and patterns first — there's rarely a reason to re-solve a problem the system already handles.
- When pod work surfaces a genuine gap in the system, bring it to the Senior Designer with context and a proposed direction rather than working around it quietly. Your pod work is a source of real-world evidence about what the system needs.
- Maintain Figma library discipline: use variables correctly, apply Dev Mode accurately, and leave files in a state the team can navigate.
Pod-Level Research and Evidence
- Run lightweight heuristic evaluations and pattern validation within your pods to complement the UX Researcher's formal studies.
- Review session recordings, behavioural analytics, and support ticket themes for your domain. Know the friction points your users experience, not just the jobs they're trying to do.
- Know when a question in your pod needs formal research before it can be answered, and flag it early. Raising that flag is a sign of good judgement.
Who You Are
- Experienced practitioner: Proven product design or UX design experience in B2B SaaS or a similarly complex, workflow-driven product. You've shipped real features to real users in a cross-functional team — not just produced concepts.
- Detail-driven: Strong interaction design across all feature states. You take the work seriously through to the error case, the empty state, and the recovery path.
- Self-directed: The sprint-ahead model means you plan your own time across two concurrent pod commitments. You're comfortable setting your own priorities without being told what to do next.
- Systems-literate: You work within design systems with discipline and contribute to them constructively. You're not expected to build one, but you know how to use one well and understand why it matters.
- Clear communicator: You write clearly. Calm, precise micro-copy for a complex confirmation screen or a statutory calculation error message is part of the design work itself.
- Collaborative without being passive: You're comfortable in trios. You advocate for your design direction, listen to push back from Product and Engineering, and either update your position based on good evidence or hold it and explain why. You hold a position when the evidence supports it, and you change your mind when it doesn't.
- Domain agnostic: You don't need prior HR or Payroll experience, but you should be excited to tackle high-stakes, compliance-adjacent domains where getting things wrong has real consequences for real businesses.
- Interaction specialist: Experience designing conversational flows, progressive disclosure patterns, or human-in-the-loop automation interfaces is a distinct advantage.
Part of the Zellis Group, Moorepay is a team of over 500 friendly professionals across four offices in Swinton (Manchester), Sheffield, Birmingham and Kochi (India). We’re passionate about making Moorepay a fantastic place to work for every single one of our colleagues. The average length of service at Moorepay is 12 years, which speaks for itself!
To help make Moorepay such a great place to work, we focus on three things in our company culture: mental health support, maintaining a healthy work/life balance, and equal opportunities and inclusion for all.
Here’s what you’ll gain if you join our team:
- A career packed with opportunity, in a stable and growing company.
- A comprehensive programme of learning and development.
- Competitive base salary.
- 25 days annual leave, with the opportunity to buy more. You’ll even get your birthday off as well!
- Private medical insurance.
- Life assurance 4x salary.
- Enhanced pension with up to 8.5% employer contributions.
- A huge range of additional flexible benefits across financial & personal wellbeing, lifestyle & leisure.
