Technical Delivery Lead

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.
Open Teams exists to make ownership possible.
Founded by Travis Oliphant, creator of Num Py and Sci Py, and built by people with deep roots across the open-source ecosystem, including Num Py, Sci Py, 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.

Location: Washington, DC or Denver, CO preferred (hybrid). Highly qualified candidates outside these locations may also be considered for unclassified work.

Clearance: An active TS/SCI clearance 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

We're looking for a Technical Delivery Lead to own the end-to-end technical delivery of an AI/ML platform running in secure, regulated environments. This is a role for someone who has taken a system from a development environment into hardened production and knows how much of that job is not writing code.

The work runs across three fronts. You lead the deployment itself — a containerized, API-first platform moving from open development into locked-down production, across network boundaries and through whatever gates the environment imposes. You steer the system through security accreditation and authorization, which means owning that path rather than waiting on someone else to walk it. And you provide day-to-day technical leadership for a combined engineering and security team, including partner and subcontractor personnel.

This is hands-on leadership. You'll make the calls on architecture, security posture, and sequencing — and your team will judge those calls on the merits, which is a good thing. The people who thrive here have done this work themselves: the promotion between environments, the boundary crossings, the accreditation paperwork. Not managed it from a distance — done it.

• Own the end-to-end technical delivery of the platform across unclassified development and classified production environments
• Lead the promotion of platform releases into classified environments, including signed release packages, software bills of materials, cross-domain submission packages, and environment-parity validation
• Establish and maintain a recurring software-promotion cadence
• Lead the development and maintenance of the RMF body of evidence, including the System Security Plan, control implementations, Plan of Action and Milestones, and security test artifacts
• Drive the accreditation timeline in partnership with Government security officials and the Authorizing Official
• Position the program for a potential transition from a traditional ATO to a continuous ATO model
• Direct platform, Dev Sec Ops , and ML infrastructure engineers across unclassified and classified work streams
• Set technical priorities, remove delivery blockers, enforce engineering standards, and align technical execution with contract milestones
• Lead cybersecurity and systems engineering personnel responsible for RMF execution, system hardening, and classified‑environment integration
• Ensure security engineering is integrated into the delivery lifecycle and automated pipelines
• Manage subcontractor technical personnel as part of an integrated delivery team
• Track and elevate Government‑furnished information, access, equipment, personnel, and other dependencies that could affect delivery
• Document schedule risks associated with cross-domain…