Senior Site Reliability Engineer (SRE)

Arctiq

About The Position

Arctiq is seeking a Senior Site Reliability Engineer to support a client building an SRE Center of Excellence (CoE). Working with other SRE leaders, the role will establish reliability standards, release discipline, and a consistent operating model across application teams. Dynatrace is already in place; the focus is on improving application reliability throughout the release lifecycle by defining standards, embedding them in delivery pipelines and Dynatrace, and supporting teams through releases and on-call. The SRE team owns SLOs, production readiness, release gates, reliability practices, and incident follow-through. The Observability CoE and Platform teams retain ownership of observability standards and agent deployment. The work is delivered in defined waves, with the goal of enabling application teams to independently apply the SRE framework and templates. This is a 6–9 month contract opportunity with potential for extension.

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 and ability to work with engineering teams, application owners, and business stakeholders.
Outcome-focused approach and experience managing milestones, deliverables, ownership, and timelines.

Responsibilities

Embed with two or three application teams in each wave and leave behind reusable templates for tags, service-level objectives, synthetics, and dashboards.
Define reliability measures based on user journeys; select service-level indicators, targets, and time windows, and track error budgets.
Build SLOs in Dynatrace and maintain them as code so non-production and production environments remain aligned.
Present SLO compliance, burn rate, and status in views that application owners and executives can understand.
Configure alerting based on error-budget burn rather than every latency spike, routing alerts through the existing Dynatrace-to-ServiceNow path with runbook links.
Embed production-readiness checks in delivery pipelines, including synthetic test success, an unchanged reliability baseline, and a tested rollback.
Prefer blue-green releases so the previous version can resume traffic if needed.
Report DORA measures, including deployment frequency, lead time for changes, change failure rate, and time to restore, and relate them to error budgets.
Join the on-call rotation for the applications supported.
Use Dynatrace and ServiceNow during incidents to identify affected user journeys and dependencies; conduct blameless reviews after breaches and turn findings into runbooks or backlog items.
Communicate status in plain language, including commitments, shipped work, blockers, and upcoming milestones.
Lead the SRE Center of Excellence with other SRE leaders by establishing a golden path, shared standards, and consistent wave evaluation.
Set reliability expectations, train a champion on each team, and lead error-budget reviews when targets are missed.
Establish a production-ready golden path for a critical application within the first 90 days, including the user journey, SLOs, Dynatrace visibility, ServiceNow alerting, and pipeline release checks.
Enable application teams to promote changes independently using the established SRE framework and templates.
Review error budgets and SLO performance monthly with application owners.