Head of Engineering, Rewards

Who You Are

• Direct-to-consumer product engineering at scale. You have built and shipped products used directly by large consumer audiences, and you understand what moves engagement and retention. This is the defining requirement of the role.
• Genuine front-end and mobile depth. You have led or personally built consumer-facing mobile and web experiences. A backend-only background, however strong, is not what this role needs.
• Experimentation and growth engineering. Hands-on experience running A/B tests, feature flagging, and measurement frameworks, and using the results to drive product decisions rather than to justify them.
• At least 5 years of experience managing managers — leading an engineering organisation through other engineering leaders, not a single team.
• Hands-on technical leadership. You are still close to the code. We expect a meaningful proportion of hands-on engineering time and technical credibility with the engineers you lead.
• 10+ years of overall software engineering experience, with at least 5 years leading engineering teams through growth phases.
• Comfort with our backend environment — Java and Spring Boot — and the ability to lead backend engineers credibly, even if it is not where your own depth sits.
• Experience building and scaling an engineering organisation from a small base, including hiring and developing Engineering Managers.
• Strong collaboration with commercial stakeholders — growth, marketing and sales — and the ability to translate business objectives into engineering work.
• Rewards, loyalty, gamification, personalisation or growth platform experience is a strong advantage but is not required.
• Fintech or payments experience is an advantage, not a requirement.

Cultural Alignment

As well, we assess every candidate across eight dimensions that define how great leaders operate at Moniepoint. We look for evidence of all eight throughout the process, not just in a single conversation.

• Customer Obsession: Build deep empathy for users. Solve problems intuitively, and fix root causes, not just tickets.
• Craft: Master the fundamentals. Reason from first principles, make trade-offs explicit, and raise the bar on quality.
• Systemisation: Turn repeating decisions into scalable mechanisms. Reduce cognitive load and raise engineering quality.
• Urgency: Move with disciplined speed. Act autonomously within scope, remove friction, and escalate risks early.
• Ownership: Treat the platform as your own. Take initiative across boundaries and follow through without reminders.
• No Ego: Put the mission first. Share credit, welcome debate, and never protect status over team outcomes.
• Candour: Surface uncomfortable truths and risks early. Intelligent failure is welcome; concealment is not.
• Integrity: Stay truthful and ethically consistent. Refuse toxic behavior. Performance without integrity is unacceptable.