About this role
Tabby creates financial freedom in the way people shop, earn and save by reshaping their relationship with money. Over 25 million users choose Tabby to stay in control of their spending and make the most out of their money. The company’s flagship offering allows shoppers to split their payments online and in-store with no interest or fees. Over 70,000 global brands and small businesses, including Amazon, Noon, IKEA, and SHEIN use Tabby to accelerate growth and gain loyal customers by offering easy and flexible payments online and in stores. Tabby generates over $18 billion in annual transaction volume for its partner brands and is the highest-rated, most-reviewed, largest, and fastest-growing FinTech in the GCC region. Tabby launched in 2019 and has since raised +$1 billion in equity and debt funding from global and regional investors, and is now valued at $6,5 billion. We’re looking for a Senior Database Administrator to join our Infrastructure team. You’ll work on high-impact projects in a high-growth environment, alongside a world-class remote engineering team spread across 20+ countries. Own the reliability and performance of our production ClickHouse clusters, whether self-hosted on Kubernetes or running on managed ClickHouse services. Design a standard architecture and tooling that let us grow to dozens of multi-node clusters without the operational work growing at the same pace. Manage the whole cluster lifecycle as code: provisioning, configuration, scaling, upgrades, and migrations. Build monitoring and alerting that catch problems before users notice them. Own backups and disaster recovery, and test restores regularly. Keep clusters secure by default. Plan capacity and keep infrastructure costs under control. Be the go-to person on ClickHouse for developers, DevOps engineers, other DBAs, and engineering leadership, from schema design and data ingestion to query performance. Handle routine database requests and automate as many of them as you can. Step in during rare production emergencies, including outside business hours. Afterwards, lead the root-cause analysis on the database side and contribute to the postmortem. Keep documentation and runbooks up to date, and share what you know with the team.