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.
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 Service Now 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 Service Now 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.
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, Service Now alerting, and pipeline release checks.
- Enable application teams to independently promote changes using the established SRE framework and templates.
- 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.
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…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).