CI Engineer

Metabase is the easiest way for people to get insights from their data, from tiny startups who get up and running quickly to major corporations with tens of thousands of users. That's why people love us.   We bring data tools with the elegance and simplicity of consumer products to the crufty world of enterprise business intelligence. We provide an opinionated open source starting point for how companies should measure, analyze and share their data, which is used by tens of thousands of companies. Our engineering team of ~70 people is fully distributed across the globe, and we work hard to build an async-friendly, shipping-focused engineering culture.   About the Role   We're seeking CI Engineers to join our engineering team and help keep our testing and release infrastructure healthy, fast, and reliable. This is a critical role — our CI and testing systems are complex, deeply relied upon, and continuously evolving.   You won't be writing product features, and you won't be expected to author new test coverage. Instead, your job is to own the health and reliability of our CI systems end to end. That means supporting the engineers who are writing tests, but it also means taking initiative — spotting problems before they become outages, identifying patterns in flakiness before they erode confidence in the test suite, and proactively improving the release process rather than waiting for things to break. We want someone who feels a genuine sense of ownership over these systems and acts accordingly.   This is a great role for a self-directed engineer who takes pride in the reliability of the infrastructure others depend on, and who can both identify problems as well as solve them. What You'll Do

Own and proactively improve our GitHub Actions-based CI pipelines — not just fixing what breaks, but anticipating bottlenecks and reliability issues before they impact the team

Triage and resolve flaky tests across a large, multi-layered test suite spanning unit, integration, and end-to-end tests — identifying systemic patterns, not just one-off fixes

Support ongoing releases and take ownership of improving the release process over time

Act as a first responder to emergent CI infrastructure issues, diagnosing and resolving them quickly and independently

Support product engineers who are writing tests using Cypress, Jest, and our home-grown Clojure-based test frameworks

Manage test infrastructure across a wide matrix of databases — we test against nearly all major transactional and analytical cloud databases including PostgreSQL, MySQL, Snowflake, BigQuery, Redshift, and more

Document and communicate clearly and asynchronously across a globally distributed team — and keep the broader engineering team informed about the state of CI health without being asked, as well as communicating and demonstrating best practices.

What We're Looking For

Demonstrated experience working with CI/CD systems in a professional engineering environment — you don't need to be a 10-year veteran, but you need to have done this work, done it well, and owned it

A proactive, ownership-driven mindset — you notice things that are heading in the wrong direction and fix them without waiting to be asked

The independence to manage your own priorities and operate effectively without close supervision across a globally distributed team

Solid understanding of GitHub Actions or comparable CI platforms

Experience with JavaScript testing tools, particularly Cypress and/or Jest

Comfort with containerization (Docker) — our database test matrix depends on it

Solid shell scripting skills (Bash)

Experience diagnosing and fixing flaky tests in large test suites

Strong async written communication skills — this is a remote-first, globally distributed team

Curiosity and a systematic approach to debugging unfamiliar systems

Nice to Have

Familiarity with Clojure and TypeScript

Experience testing against or operating cloud data warehouses or analytical databases

Experience building and supporting software release pipelines

Why This Role

You'll have real ownership over systems that directly affect the productivity of a 70-person engineering team

You'll work on infrastructure that supports widely used open source software

Fully remote, any timezone — we're serious about async-first culture

You'll have the autonomy to identify and drive improvements rather than just work a ticket queue