[Hiring] Senior Infrastructure Engineer @iTmethods

Role Description

Reign is an AI governance platform for regulated enterprises. You take it from a deployment we run ourselves to one a client can install, operate, and keep running in their own environment.

Our clients run the platform in their own environment, on their own cloud, under their own controls. Some run managed Kubernetes on a public cloud. Some run on-prem clusters with no internet access. You make the platform deployable in all of those places, at scale, without help from our engineers.

The infrastructure is built from modular definitions that each client composes for their environment. You design those modules, maintain them as the platform changes, and manage how infrastructure and deployment changes reach each client without breaking what already runs.

• Design the reference deployment and make it portable across cloud providers and on-prem environments.
• Design the infrastructure as modules that clients compose for their environment, and maintain the definitions and modules as the platform changes.
• Manage infrastructure and deployment changes from proposal through review, rollout, and rollback, so each client environment stays predictable.
• Build the install, upgrade, and rollback path that a client operator can run.
• Make every layer of the platform highly available. Define the failure modes and prove each one with a test.
• Evolve the deployment and its maintainability as the client base grows, so each new client is cheaper to onboard and operate than the last.
• Own the environments and the pipelines that deploy them.
• Own the observability that ships with the platform and works with the client's own tooling.
• Own supply-chain security, including signed artifacts, vulnerability gates, and offline installs.
• Review architecture with the team, and bring the deployment and operations view in early so every design is one a client can run.

Qualifications

• You have designed systems that other people operate, and you have lived with the consequences.
• You name failure modes up front and prove recovery with a test.
• You keep designs simple enough to explain why each component exists.
• You treat install, upgrade, rollback, and security as part of the design, not an afterthought.
• You have run production workloads on Kubernetes across more than one cloud or on-prem environment.
• You can defend a design to engineers who disagree with it.
• You recognize code and infrastructure patterns, and you understand how architecture drifts over time and what it takes to correct it.

Requirements

• You have delivered software into air-gapped or sovereign-cloud environments.
• You have packaged software for clients to install and operate themselves.
• You have shipped into a regulated industry.
• You have run AI coding agents at scale.

Company Description