DevOps Engineer
-
IT/Tech
Job Description & How to Apply Below
The Dev Ops Engineer builds and runs the delivery pipeline and the platforms it deploys to: CI/CD, infrastructure as code, environments, observability and reliability engineering. They coordinate releases with change management and own the on-call response for the platforms they run.
Reports to:
Engineering Manager
The Dev Ops Engineer builds and runs the delivery pipeline and the platforms it deploys to: CI/CD, infrastructure as code, environments, observability and reliability engineering.
- Build and maintain CI/CD pipelines and infrastructure as code
- Manage environments, deployments and release automation
- Implement observability, SLOs and reliability practices
- Participate in on-call and incident response for platforms
- Coordinate releases with change management
- Drive post-incident improvements and automation
Who this role reports to, who reports to them, and the peers they work with most.
Reports to Engineering Manager Works closely with Change and Release Manager Systems Administrator Security Analyst IT Operations Director How Smart Suite supports the Dev Ops EngineerThe Dev Ops Engineer builds and runs the delivery pipeline and the platforms it deploys to, and answers to the Engineering Manager and, for the platforms it runs, the IT Operations Director for releases that land cleanly and platforms that stay up. Smart Suite gives you release records, on-call ownership and change context in one place, so coordination stops living in chat.
Runthe pipeline, releases and platforms you own Releases with scope, approvals and environment status
Each release in Release Management carries its scope, timeline and dependencies, the approved changes it is linked to and its status across development, testing and production, so deployment readiness is a state you can see rather than a thread you have to read through.
Maintenance windows on a shared calendarPlanned maintenance, outages and releases sit on one operations calendar visible to stakeholders, so a pipeline or infrastructure change does not land on top of someone else's window.
On-call rotations with a clear ownerOn-Call Management holds rotations and escalation order, so every alert, maintenance window and outage has a named owner and the handover at shift change is recorded rather than assumed.
Connect to change, security and the engineers you deploy for Infrastructure changes with impact contextWhen you raise a change for infrastructure or pipeline work, the service and dependency map shows what is at risk, so the Change and Release Manager's review starts from impact rather than from a description.
Defects and incidents linked to work itemsIncidents on your platforms link to the stories, bugs and fixes the Engineering Manager's team is working on, so a post-incident action becomes prioritized engineering work rather than a note in a document.
Security findings routed with the releaseFindings from the Security Analyst attach to the release or change they affect, with approval gates recorded, so secure-development evidence for SOC 2 or ISO 27001 is produced as part of shipping.
Prove reliability and control to IT operations leadership Audit-ready history of every deploymentWho approved, what changed and when it was deployed is kept for every release and change, so the IT Operations Director can answer an auditor's change-management question without a reconstruction.
Post-event reviews that reduce repeatsOutcomes, follow-ups and improvement actions from each outage or failed deployment are captured against the event and tracked, so the same failure mode is less likely to appear in the next review.
Sprint progress and release status liveDashboards show sprint progress,…
(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).
View / Apply for Jobs
Matching My Jurisdiction