次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 6,472

← 検索結果に戻る

Sr Manager, Site Reliability Engineer (FedRAMP / AWS GovCloud)

BeyondTrust

勤務地
Anywhere
掲載日
2026年10月6日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

BeyondTrust 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 Role The SRE Manager is the operating leader of a new cross-product SRE team at BeyondTrust, standing up and running the AWS GovCloud environments that bring additional BeyondTrust 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 DevOps 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 GovCloud 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 GovCloud 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. What You’ll Do GovCloud build and FedRAMP delivery Own the AWS GovCloud 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 GovCloud environments require (build, signing, artifact management, quality and security gates) and cloud cost visibility for the covered accounts Production and change operations 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, and verification that a patch actually landed everywhere it was scoped to Own the incident management process, tooling, on-call design, and post-incident review cadence Drive the automated environment promotion path from development through staging to production Note on workload shape: our estates are appliance-model and single-tenant VM fleets alongside shared services, not purely cloud-native. Fleet upgrade orchestration, golden images, and staged rollout at hundreds-to-thousands scale are core, not edge cases. Intake and prioritization Run intake and prioritization for operational requests from feature teams and leadership, keeping a single trusted view of active work, owners, and risks Ensure the team is not overcommitted and that feature teams have a clear, responsive interface for operational needs Team leadership Lead a team of DevOps, SRE, and security automation engineers, providing direction, accountability, and operational clarity Partner with the VP of Application Engineering on workforce planning, hiring, role design, and onboarding for the function Build a culture of ownership, transparency, and reliable execution; set delivery rhythms, run planning cycles, and maintain visibility into team capacity and health What Success Looks Like The covered products live in AWS GovCloud under the FedRAMP authorization, with evidence produced by automation rather than by hand Production changes go through a defined, auditable process; uncontrolled changes do not reach production Patches and releases are verified as landed everywhere they were scoped to, as a system property rather than a manual check FedRAMP continuous monitoring obligations are met on time, every month, without feature teams being interrupted or senior engineers pulled from product work Better Together Diversity. Inclusion. They’re more than just words for us. They are the guiding values of how we build our teams, cultivate leaders, and create a culture where people feel connected. We take care of our employees so they can take care of our customers. Customers who come from all walks of life just like us. We hire incredible people from diverse backgrounds because when we are different together, we are stronger together. About Us BeyondTrust is the global identity security leader protecting Paths to Privilege™. Our identity-centric approach goes beyond securing privileges and access, empowering organizations with the most effective solution to manage the entire identity attack surface and neutralize threats, whether from external attacks or insiders. BeyondTrust is leading the charge in transforming identity security to prevent breaches and limit the blast radius of attacks, while creating a superior customer experience and operational efficiencies. We are trusted by 20,000 customers, including 75 of the Fortune 100, and our global ecosystem of partners. Learn more at www.beyondtrust.com.  #LI-BS1

検索して比較し、応募を準備しましょう

次の仕事で活かしたい職種やスキルから検索を始めましょう。勤務地と職種の条件を調整し、求人を開いて担当業務を比較してください。結果がない場合は、短い検索語を試すか、条件を一つずつ外してみましょう。

必須条件と歓迎条件を分けて確認し、勤務時間、報酬、勤務地が掲載されている場合は目を通しましょう。リモート勤務でも、居住国、就労資格、勤務時間帯が指定されることがあります。現在の募集状況と詳しい条件は企業に確認してください。

募集要件に関連する実際の経験を選び、自分の役割と貢献を説明しましょう。数値は根拠がある場合にのみ使ってください。企業の応募方法に従い、送信前に連絡先、内容、PDFの表示を確認しましょう。

応募前の確認リスト

仕事探しに関するよくある質問

英語の求人が表示されるのはなぜですか?

職種名や説明文は企業が作成したものです。条件や要件を変えないように原文を掲載しています。操作画面とこのガイドは日本語です。日本語の検索で見つからない場合は、「software engineer」のように、掲載言語の職種名やスキル名でも検索してみてください。検索語が自動翻訳されるわけではありません。

リモート求人なら、どの国からでも働けますか?

必ずしもそうではありません。居住国、就労資格、勤務時間帯が指定されている場合があります。元の求人ページで条件を確認してください。記載がない場合は、自分の居住地から応募できると判断する前に企業へ確認しましょう。リモートという表示だけでは、勤務地の制限がないことは分かりません。

検索結果が出ない場合はどうすればよいですか?

より一般的な職種名や一つのスキルで検索し、条件を一つずつ外してみてください。同じような仕事でも企業によって呼び方が異なります。特定の求人が見つからなくなった場合は、企業の採用ページで求人番号を探しましょう。検索条件を広げても、終了した募集が再開するわけではありません。

ResumizeAIから応募が送信されますか?

応募ボタンは外部サイトを開きます。企業または採用サービスの案内に従い、そのサイトで送信を完了してください。ResumizeAIで応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。