Remote Systems Engineer

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.

Senior Infrastructure Engineer - AI/ML Platform

Location: U.S - Remote

Work Authorization: U.S. citizenship required

Clearance: An active clearance is not required at the time of hire. Candidates must be able to obtain and maintain a Secret security clearance, which includes a federal background investigation.

Salary Range: $85,000 - $120,000 USD, dependent on experience level and location

We're looking for a Systems Engineer to join our platform support team. This is a role for someone early in their infrastructure career who wants real ownership of production systems and is willing to earn it by being the person others can count on.

The work runs across two streams. Internal Platforms covers the systems Open Teams itself runs on — identity, cloud, internal applications, our website. You own that surface end to end, which means you're the first responder when something breaks and the one who fixes the underlying cause so it stops happening. Project Support means backing up our infrastructure engineers on the platforms we build and operate for customers, including government programs.

Both streams start at the front line. That's the entry point, not the destination - as you build real context, the scope grows toward environment builds, deployment configuration, and eventually owning pieces of a platform outright.

The two sides reinforce each other. Our internal systems run on the same open-source building blocks we ship to customers, so operating our own environments is how you become useful on a customer deployment. You will not be an expert in all of it on day one, and we don't expect you to be. We expect you to be curious, to write things down, and to ask before you break something.

This is a fully remote, U.S.

-based role working with a distributed team that relies heavily on asynchronous communication.

• Own the internal request queue: triage what comes in, resolve what you can, pull in help when you can't, and make sure nothing silently falls through.
• Administer Google Workspace and identity systems — accounts, groups, SSO integrations, security policy, and the onboarding and offboarding runbooks that keep access correct as people join and leave.
• Support the provisioning and maintenance of cloud infrastructure (AWS or equivalent): accounts, IAM roles, networking basics, resource tagging, and cost visibility.
• Deploy and operate internal applications on Kubernetes using Helm and ArgoCD, under the guidance of senior engineers. Understand what you're deploying, not just the command that deploys it.
• Maintain the internal Open Teams website - an Astro site backed by EmDash - including build pipelines, deploys, DNS, and content publishing support for the teams that use it.
• Build and maintain monitoring and alerting for the systems you own, and help reduce alert noise rather than adding to it.
• Handle security and access hygiene: patching, MFA enforcement, periodic access reviews, endpoint configuration, and offboarding.

• Handle incoming issues from customer teams: reproduce the problem, gather logs and context,…