Trova la tua prossima opportunità

Cerca offerte per professione, competenza e località. Controlla i requisiti prima di preparare la candidatura.

Una ricerca utile non si ferma a un titolo interessante. Confronta mansioni, requisiti e condizioni con la tua esperienza. Questa guida ti aiuta a selezionare le opportunità, preparare documenti pertinenti e verificare dove inviare ogni candidatura.

L’interfaccia è in italiano. I titoli e le descrizioni delle aziende rimangono nella lingua originale di pubblicazione, che può essere l’inglese.

Cancella filtri

Risultati: 14.087

← Torna ai risultati

Senior Site Reliability Engineer (SRE)

Arctiq

Lavoro da remoto

Località
Remote (United States)
Orario
Contractor
Pubblicato
15 ott 2026

Prima di candidarti, verifica sul sito dell’azienda che la posizione sia ancora aperta e leggi le condizioni complete.

Descrizione della posizione

L’interfaccia è in italiano. I titoli e le descrizioni delle aziende rimangono nella lingua originale di pubblicazione, che può essere l’inglese.

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

Cerca, confronta e prepara la candidatura

Inizia da una professione o competenza che desideri utilizzare. Regola i filtri di località e professione e apri le offerte per confrontare le responsabilità. Se non trovi risultati, prova un termine più breve o elimina un filtro alla volta.

Distingui i requisiti indispensabili dalle preferenze. Controlla orario, retribuzione e località quando sono indicati. Un lavoro da remoto può comunque richiedere la residenza in un paese, un’autorizzazione al lavoro o orari compatibili. Conferma la disponibilità e le condizioni complete con l’azienda.

Scegli esempi reali della tua esperienza che rispondano ai requisiti della posizione. Spiega il tuo contributo e usa numeri solo quando puoi dimostrarli. Segui le istruzioni dell’azienda e controlla i contatti, il contenuto e il PDF prima di inviare la candidatura.

Prima di inviare la candidatura

Domande sulla ricerca di lavoro

Perché alcuni annunci sono in inglese?

Le aziende scrivono i propri titoli e le proprie descrizioni. Conserviamo questi testi per non alterare requisiti o condizioni. La navigazione e questa guida sono in italiano. Se una ricerca in italiano non restituisce risultati, prova anche il ruolo o la competenza nella lingua dell’annuncio, per esempio “software engineer”.

Un lavoro da remoto permette di lavorare da qualsiasi paese?

Non necessariamente. L’azienda può limitare i paesi di residenza, richiedere un’autorizzazione al lavoro o stabilire orari precisi. Controlla l’annuncio originale. Se queste informazioni mancano, chiedi conferma all’azienda prima di presumere di poter lavorare dalla tua posizione.

Cosa posso fare se non ci sono risultati?

Prova un titolo più generale o una sola competenza e rimuovi un filtro alla volta. Le aziende usano nomi diversi per ruoli simili. Se un annuncio specifico è scomparso, cerca il suo riferimento nella pagina carriere dell’azienda: ampliare la ricerca non riapre una posizione chiusa.

La candidatura viene inviata tramite ResumizeAI?

Il pulsante per candidarti apre un sito esterno. Segui le istruzioni dell’azienda o del fornitore di selezione e conferma l’invio su quel sito. Preparare un CV in ResumizeAI non equivale a inviare una candidatura. Se il collegamento apre solo il sito aziendale, cerca prima la posizione.

Come adatto CV e lettera di presentazione?

Collega i requisiti a progetti, attività e risultati che puoi spiegare. Evidenzia l’esperienza pertinente senza inventare competenze o successi. Nella lettera, spiega il tuo interesse con un esempio concreto. Rispetta la lingua e il formato richiesti e rileggi entrambi i documenti prima dell’invio.