Staff Software Engineer - Databases
Posted by employer 2 years ago
First seen on Joblaze 6 months ago
Last verified on the company career page 13 hours ago
Skills & Technologies
Requirements
- Experience
- 12+ years
Not disclosed in this posting: compensation, work arrangement, visa sponsorship.
Joblaze summary
In the role of Staff Software Engineer at Databricks, the individual will focus on designing and maintaining a robust schema migration platform that ensures seamless data operations across a vast network of databases. Key skills include extensive experience with backend systems, particularly MySQL and TiDB, along with a strong background in CI/CD automation and developer tooling. This position is ideal for seasoned professionals with over 12 years in platform engineering who are passionate about enhancing developer experiences and ensuring data integrity. Databricks emphasizes innovation and reliability, making this a pivotal role in their mission-critical infrastructure.
Joblaze insights
Quick facts
- How much experience is required?
- At least 12 years of relevant experience for this Staff Software Engineer - Databases role.
- What's the tech stack?
- Joblaze extracted these technologies from the posting: CI/CD, MySQL, TiDB, backend systems, platform engineering, schema migration.
- What seniority level is this role?
- Databricks targets staff-level candidates for this position.
- Is this full-time or contract?
- Full-time for this Staff Software Engineer - Databases role at Databricks.
From the original posting
P-375
At Databricks, we build powerful infrastructure that accelerates innovation and enables data teams to deliver with confidence and scale. Our unified schema migration platform underpins automated, observable, and developer-friendly workflows—ensuring Databricks can continue evolving rapidly across thousands of databases and 60+ mission-critical services.
What You’ll Do
As a Staff Software Engineer, you’ll lead the design, development, and reliability of our global platform that manages schema and data changes at scale:
- Schema Migration Platform: Architecting and maintaining automated schema change infrastructure for MySQL and TiDB, while implementing versioning, rollback, validation, and auditing for safe, predictable, and fast migrations.
- Scale, Reliability & Test Harness: Ensuring the platform operates across thousands of global databases with zero downtime, enhancing resilience, observability, and recovery, and building a test harness for migration and deployment validation.
- Developer Experience & CI/CD Integration: Designing intuitive tools and APIs for seamless schema and data change management, and embedding migration workflows into CI/CD pipelines to increase velocity and reduce friction.
- Schema & Data management: Designing infrastructure for safe, large-scale schema and data operations like backfills and purging. This includes ensuring backfill operations are monitored, retryable, minimally disruptive, and automated to align with schema/data evolution and maintain data integrity.
Your role will be crucial in:
- Ensuring the scalability and reliability of schema and data operations across Databricks’ global footprint.
- Driving predictable deployments by architecting robust test harnesses and automation.
- Elevating the developer experience by building accessible, resilient tools that make complex migrations feel simple.
- Guaranteeing the integrity of both schema and data through safe, efficient backfill strategies.
What we look for:
- 12+ years of professional experience in backend systems or platform engineering.
- Experience in building platforms, infrastructure, or database engineering, especially with MySQL, TiDB.
- Track record of building and scaling mission-critical platforms supporting high-throughput, global services.
- Experience with schema migration frameworks, CI/CD automation and developer tooling.
- Champion of developer experience, creating clear, reliable, and user-friendly workflows.
About Databricks
BenefitsStandard company text repeated across Databricks's postings is omitted here.