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

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

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

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

条件をクリア

検索結果: 14,087

← 検索結果に戻る

Senior Site Reliability Engineer (SRE)

Arctiq

リモート勤務

勤務地
Remote (United States)
勤務時間
Contractor
掲載日
2026年10月15日

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

仕事内容

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

Company Overview: Arctiq is a global, intelligence-driven technology services company delivering professional and managed services across Hybrid Cloud Infrastructure, Networking & Connected Experiences, Cybersecurity, Data & AI, Autonomous Operations & Intelligence, and Enterprise Service Management. We help organizations operate, secure, and modernize complex environments by unifying infrastructure, networking, data, security, automation, and observability under a single, integrated operating model. Our work focuses on helping customers reduce operational friction, improve resilience, and make better, faster decisions as their environments evolve. Arctiq builds on decades of industry expertise and a customer-centric ethos to deliver exceptional value to clients across diverse industries. Position Overview: In this role, you will support one of Arctiq’s clients in building an SRE Center of Excellence (CoE), working alongside other SRE leaders to establish standards, release discipline, and a consistent operating model across application teams. With Dynatrace already in place, the focus is on improving application reliability throughout the release lifecycle. You will define reliability standards, embed them into pipelines and Dynatrace, and work with teams through release and on-call. The SRE team will own SLOs, production readiness, release gates, reliability practices, and incident follow-through, while the Observability CoE and Platform teams continue to own observability standards and agent deployment. This is a 6-9 months contract opportunity (with potential extension). Responsibilities: Sit with two or three application teams in a wave. Leave behind templates they can run without you: tags, a small set of service-level objectives, synthetics, and a dashboard. Start from a user journey (for example, sign-in through account summary), not from CPU. Choose a few service-level indicators, set a target and a time window, and track the error budget. Build those objectives in Dynatrace and keep them as code, so non-production and production stay in step. Show compliance, burn rate, and status on a view an owner and an executive can both read. Page on error-budget burn, not on every latency spike. Route alerts through the existing Dynatrace to ServiceNow path, with a runbook link in the payload. Put production readiness in the delivery pipeline: a change is not ready for production until the synthetic passes, the reliability baseline has not regressed, and rollback has been tried. Prefer a blue-green release so the previous version can take traffic back. Report the wave with DORA: how often the team ships, how long a change takes, how often it fails, and how fast it is restored. Tie that report to the error budget, not to a tool count. Join the on-call rotation for the applications you embed with. During an incident, use Dynatrace and ServiceNow to find which journey is burning budget and which dependency is involved. After a breach, run a blameless review and turn the outcome into a runbook or a backlog item. Do not leave the lesson in a slide. Explain status in plain language: what was promised, what shipped, what is blocked, and what the next milestone is. App owners and leadership should not need a Dynatrace specialist to understand the update. Lead the Center of Excellence with the other SRE leaders: one golden path, one set of standards, one way a wave is judged. Then carry that into the teams you embed with. Set the reliability bar, train a champion on each team, and hold the error-budget review when a target is missed. You do not wait to be told the next step. What Success Looks Like: This work is delivered in defined waves, with clear outcomes and ownership. First 90 Days Establish one production-ready “golden path” for a critical application, including the user journey, SLOs, Dynatrace visibility, ServiceNow alerting, and pipeline release checks. Each Wave Enable application teams to independently promote changes using the established SRE framework and templates. Monthly Review error budgets and SLO performance with application owners. Report SLO compliance alongside key DORA metrics, including deployment frequency, lead time, change failure rate, and time to restore. Definition of Done A wave is complete when the application team can measure whether the user journey is meeting its reliability target and safely roll back a failed release, not simply when a dashboard is in place. Requirements: Strong SRE and reliability engineering experience, including SLOs, SLIs, error budgets, production readiness, and DORA metrics. Hands-on Dynatrace experience, including RUM, services, synthetics, SLOs, alerting, dashboards, and distributed tracing. Strong understanding of CI/CD, GitLab or similar tools, Infrastructure as Code, release controls, and automated reliability checks. Experience with Kubernetes, APIs, client-server architectures, and blue-green or similar deployment strategies. Strong knowledge of change management, incident response, on-call practices, ServiceNow, and production troubleshooting. Experience embedding reliability practices throughout the software delivery lifecycle, from development through production. Proven ability to lead engineers or SRE practices, establish standards, and drive adoption across application teams. Strong communication skills with the ability to work across engineering, application owners, and business stakeholders. An outcome-focused approach with experience managing clear milestones, deliverables, ownership, and timelines. What this role doesn't own: Installing OneAgent, RUM, or ActiveGate. Platform owns installs. ServiceNow CMDB build. Copying an existing Kibana or Splunk estate into Dynatrace one-for-one. New reliability work is a short list of journeys and objectives. Feature delivery. Application teams ship the product. The SRE makes the release safe to ship. Arctiq is an equal opportunity employer. If you need any accommodations or adjustments throughout the interview process and beyond, please let us know. We celebrate our inclusive work environment and welcome members of all backgrounds and perspectives to apply. We thank you for your interest in joining the Arctiq team! While we welcome all applicants, only those who are selected for an interview will be contacted. Originally posted on Himalayas

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

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

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

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

応募前の確認リスト

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

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

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

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

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

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

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

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

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

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

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