USA
Site Reliability Engineer / DevSecOps Engineer
About this role
Who We Are Every organization runs on intelligence: years of accumulated knowledge, decisions, and context. As AI takes on more of that work, companies face a choice: rent that intelligence from vendors who keep the data, the context, and the results, or own it. OpenTeams exists to make ownership possible. Founded by Travis Oliphant, creator of NumPy and SciPy, and built by people with deep roots across the open-source ecosystem, including NumPy, SciPy, PyTorch, and Jupyter, we help enterprises and governments build AI they control, govern, and evolve themselves.
If that sounds like your kind of work, we'd like to meet you. Site Reliability Engineer / DevSecOps Engineer Location: Washington, DC; Denver, CO; or Colorado Springs, CO preferred (hybrid). Highly qualified candidates outside these locations may also be considered for unclassified work. Work Authorization: U.S. citizenship required Clearance: An active TS/SCI clearance with CI polygraph is strongly preferred. Candidates without an active clearance may be considered for unclassified work but must be eligible to obtain and maintain a U.S.
security clearance. Salary Range: $145,000–$250,000 USD, dependent on experience level and location About the Role We're looking for a SRE/DevSecOps Engineer to build and own the secure delivery pipeline for an AI/ML platform deployed into tightly controlled environments. This is a role for someone who treats security as something you build into the delivery path, not something you inspect for at the end of it. You own the supply chain end to end — pipelines that produce hardened, signed release artifacts with a software bill of materials attached, with scanning, policy enforcement, and secrets handling built into the path rather than bolted alongside it.
That path has to survive promotion into isolated and limited-connectivity environments, which means it works when the network doesn't and can prove what it shipped when nobody can reach back to check. It also has to produce the compliance evidence — audit and accreditation artifacts that fall out of the build automatically instead of getting assembled by hand under deadline. Reliability comes with the territory. Once the platform is deployed, you're part of keeping it healthy: observability, alerting, and incident response are shared work on this team, and the person who built the release path is usually the one who can tell you what changed.