UK remote
Operational Resilience Lead
About this role
Hello. We’re Teya. Teya was founded on a simple belief: local businesses deserve better. They are the cafés, restaurants, salons, shops and entrepreneurs that bring character to our high streets, create jobs and keep communities moving. Yet for too long, financial services has made life harder for them - with clunky tools, poor support and complexity that gets in the way of running a business. Teya exists to change that.
We’re building a financial platform for local businesses across Europe - one built around simple tools, thoughtful design and real human support. Our Members rely on us to help them run their business with confidence, and that responsibility shapes the way we work. We move fast. We care about quality. We stay close to the detail. And we believe great performance and genuine hospitality should go hand in hand. If you want to build meaningful products, solve real problems and make a genuine difference for local businesses, we’d love to hear from you The Operational Resilience Lead is responsible for building and running Teya's operational resilience capability within the first line of defence, ensuring Teya can prevent, adapt to, respond to, recover from, and learn from operational disruptions affecting its important business services.
This is a role for someone who designs and implements at pace, with an AI-and-automation-first mindset. The goal is a resilience programme that scales as Teya grows without becoming a manual, spreadsheet-heavy overhead. You'll own the operational execution of the framework across the business, including the identification of important business services, impact tolerance setting, mapping, scenario testing, self-assessment, and lessons learned from incidents.
You'll work closely with Technology, Information Security, Business Continuity, Product, Payment Operations, Compliance, and Operational Risk. Key Objectives: - Design and implement the operational resilience framework AI-first — automating evidence gathering, mapping refreshes, monitoring, and reporting wherever possible, and rejecting manual solutions where automation will do the job. - Ship a working v1 of new processes and iterate.
You'd rather have a lightweight framework live and generating insight in month one than a perfect framework live in month twelve. - Own and maintain the register of important business services, keeping classifications, impact tolerances, and supporting resource mappings current through automated data feeds rather than manual owner surveys. - Build the mapping capability end-to-end — people, processes, technology, facilities, data, and third parties — with a clear preference for pulling data from systems of record over collecting it by hand.