Who we are

Domino Data Lab powers model-driven businesses with its leading Enterprise AI platform trusted by over 20% of the Fortune 100. Domino accelerates the development and deployment of data science work while increasing collaboration and governance. With Domino, enterprises worldwide can develop better medicines, grow more productive crops, build better cars, and much more. Founded in 2013, Domino is backed by Coatue Management, Great Hill Partners, Highland Capital, Sequoia Capital and other leading investors. For more information, visit www.domino.ai

What we are building

The Release Engineering & Vulnerability Remediation team is building the infrastructure and automation that lets Domino ship hardened, auditable software to our most security-sensitive customers—federal agencies, financial institutions, and healthcare organizations operating in regulated or air-gapped environments.

Concretely, we are building:

• A hardened release pipeline that produces container images meeting strict scan thresholds, with reproducible builds and minimal attack surface
• An automated vulnerability triage system that ingests scanner output, deduplicates findings across images and releases, routes to owners, and tracks SLA compliance—without manual triage
• Provenance and exploitability tooling that generates SBOMs and VEX statements on every release, so customer security questions are answered from standing artifacts rather than one-off investigations
• A scalable remediation practice that uses AI and automation to keep pace with the volume of findings, rather than throwing engineers at each CVE individually

This is foundational work. The tooling and runbooks you build will define how Domino operates in regulated markets for years to come.

What your impact will be

In your first year, you will

• In your first year, you will own the hardened image pipeline for our most demanding deployments and cut time-to-remediate for critical and high findings to a published, defensible SLA.
• You will replace one-off vulnerability firefighting with an automated path from scan to fix, including SBOM and exploitability statements generated on every release.
• You will make "we are not fixing this, and here is why" a documented engineering position backed by evidence, rather than a conversation repeated with every customer.
• You will set the technical direction and tooling that the next engineers on this team build on.