Experience required:- 6+ years MySQL / MariaDB in production
1. Purpose of the role
Our client-facing and administrative portals are the system of record for client onboarding, funding, and introducing-broker (IB) rebates. The database schema has grown alongside the product rather than under a dedicated data owner. This role establishes that ownership.
Four specific pressures make the hire necessary now:
- The client and admin applications share one operational database whose migration history now exceeds 165 change files, several of which rewrite client identity and tenancy keys on live tables.
- The One Portal programme consolidates the client portal, the IB portal and a recent in-house CRM onto a single multi-entity data model, and moves reporting,
dashboard and AI-assistant reads onto read replicas and redacted views.
- Funding currently dual-writes to external instant-funding and payment-provider databases while the portal-side ledger becomes authoritative. The cutover requires reconciliation that someone owns end to end.
- No one currently rehearses database restores, owns index and capacity strategy, or reviews schema changes before they reach production. Because the data includes client money movement and KYC records, this is a compliance exposure as well as an engineering one.
2. Key responsibilities
2.1 Availability and recovery
- Own backup, point-in-time recovery and retention across every production data store, proven by scheduled restore rehearsals with measured recovery point and recovery time objectives.
- Own replication topology, failover behaviour and replica-lag budgets for multi-availability-zone MariaDB and its read replicas.
- Write and maintain runbooks
📌 Database Administrator (Salem)
🏢 Hyring®
📍 Salem
Reply to this offer
Impress this employer describing Your skills and abilities, fill out the form below and leave Your personal touch in the presentation letter.