SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 175,000 - 185,000 / annual
Branch is a fintech company on a mission to empower workers with financial freedom by helping companies accelerate payments and providing working Americans with accessible financial services.
As a Senior Database Reliability Engineer, you will own and lead all production database systems to ensure high performance, availability, and security. The role focuses on MySQL 8.4 on Google Cloud Platform's CloudSQL and Google Cloud Spanner for globally distributed workloads.
Key responsibilities include:
- Lead and take ownership of core database systems, ensuring high performance, availability, and security
- Communicate critical data changes to the data warehousing team
- Work with engineering and data teams to shepherd schema changes from design through deployment
- Build and maintain automated test and deployment data pipelines at production scale with SRE and DevOps teams
- Proactively detect weak areas and incorporate them into automated monitoring and production alerting
- Document and automate recurring processes to improve efficiency
- Evaluate new database features and products to meet scalability and global uptime requirements
- Own database backup and recovery, establishing disaster recovery targets and practices
- Support, debug, and perform root cause analysis on production database issues; participate in incident response
Required qualifications:
- 5+ years managing MySQL/CloudSQL at scale
- Expert-level SQL and MySQL knowledge, including schema design
- Deep understanding of MySQL internals
- Solid knowledge of MySQL replication, SQL tuning, and database optimization while minimizing downtime
- Experience operating Google Cloud Spanner at scale, including schema design and query optimization
- BS in Computer Science or equivalent
Bonus experience includes payments industry background, GCP toolset expertise, infrastructure-as-code, Redis, and global multi-region deployments with sharding.
