寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 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 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。