Sr Manager, Site Reliability Engineer; FedRAMP​/AWS GovCloud

Beyond Trust is a place where you can bring your purpose to life through the work that you do, creating a safer world through our cybersecurity SaaS portfolio.

Our culture of flexibility, trust, and continual learning means you will be recognized for your growth, and for the impact you make on our success. You will be surrounded by people who challenge, support, and inspire you to be the best version of yourself.

The SRE Manager is the operating leader of a new cross-product SRE team at Beyond Trust, standing up and running the AWS Gov Cloud environments that bring additional Beyond Trust products into our FedRAMP authorization. Reporting to the VP of Application Engineering, this role owns the reliability, change control, and continuous-compliance machinery for those environments so that product feature teams can stay focused on product delivery.

This is a player-coach role. The right person has staff-level technical depth: they can critically review Terraform, pipeline definitions, and architecture proposals, have personally built and operated this machinery, and can carry context in an incident. That depth is combined with real people-management experience: they have hired, grown, and run a small SRE or Dev Ops team, and they own the team's delivery, not just its architecture.

The engineering execution sits with the team; the manager stays close enough to the keyboard to lead it credibly.

The first-year mission is concrete: build and operate the AWS Gov Cloud environments that bring the covered products into our FedRAMP authorization, with the automation to keep them continuously compliant under FedRAMP 20x, where evidence is machine-readable, re-verified every few days, and reported monthly.

Our feature teams own product delivery. This role exists so they can focus on it. The SRE Manager takes permanent ownership of the shared operational work that would otherwise fall on feature teams as toil: the Gov Cloud environments, production operations, release and update machinery, and the compliance evidence pipeline for the covered products.

The team this role leads is an engineering team that owns operations, not an operations team. Its product is automation; operations is the input. Every manual procedure performed twice is a candidate for elimination, and the team's success is measured by the operational work it has made unnecessary, not the tickets it has closed. Hands-on operational work is capped at roughly half of team capacity;

the rest goes to engineering the work away. Defending that split against day-to-day pressure is the manager's job.

• Own the AWS Gov Cloud landing zone for the new product environments: multi-account structure, SCPs and guardrails, logging and security-tooling accounts, IaC-native provisioning
• Own the continuous-compliance evidence pipeline: collection, normalization, and reporting of FedRAMP 20x Key Security Indicators, built to the FedRAMP standard schema
• Own FedRAMP continuous monitoring obligations for the covered environments, keeping that operational load off feature team engineers; broader compliance obligation tracking and audit coordination are owned by central teams
• Own the CI/CD pipelines the Gov Cloud environments require (build, signing, artifact management, quality and security gates) and cloud cost visibility for the covered accounts

• Own the production change process, including change request governance, access controls, and approval standards, with auditable separation of duties between development and production
• Own release and update machinery for cloud fleets: mandatory security updates, staged and jittered rollout windows, cluster-coordinated installs,…