DevOps Engineer

Smartsuite; Newport Beach (CA); On-site; USD 110,000 - 150,000; Full time

Job summary

Capitolis is seeking a DevOps Engineer to build and run the delivery pipeline and the platforms it deploys to, including CI/CD, infrastructure as code, environments, and observability. You will own on-call response for the platforms you run and coordinate releases with change management.

You will report to the Engineering Manager and collaborate with Change and Release Managers, Systems Administrators, Security Analysts, and IT Operations leadership to maintain reliability and drive improvements

Responsibilities

• 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

Job description

IT service delivery

SmartSuite for the DevOps Engineer

The DevOps 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

What you own

The DevOps 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

Reporting lines

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 SmartSuite supports the DevOps Engineer

The DevOps 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. SmartSuite gives you release records, on-call ownership and change context in one place, so coordination stops living in chat.

Run the 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 calendar

Planned 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 owner

On-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 context

When 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 items

Incidents 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 release

Findings 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 deployment

Who 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 repeats

Outcomes, 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 live

Dashboards show sprint progress, velocity and release status live, and the AI Assistant in a SmartDoc field drafts the sprint summary and release notes from the work records, so the delivery picture you give leadership is current rather than compiled.

Release deploy. Tracks releases and deployments with scope, approvals, environment status and rollback records.

Monitoring event. Links observability alerts to on-call rotations and incident records.

Incident. Runs platform incidents with timelines and post-incident actions.

Change. Raises and tracks changes for infrastructure and pipeline updates.

Products this role uses most

IT Release Management

Plan and deploy releases with release calendars, change approvals, environment tracking, and dashboards across systems and environments.

On-call Management

Manage on-call schedules, alert routing, and escalation workflows so the right responder is notified and incidents are handled within target times.

Event & Alert Management

Ingest and act on actionable alerts with automated routing, incident triggers, and real-time visibility across systems and services.

IT Incident Management

Detect and resolve IT incidents quickly with structured workflows, SLA tracking, and real-time visibility across systems and service operations.

Change Management

Plan, approve, and implement changes with workflows, risk controls, and a current view across systems and services.

Industry reference

ITIL 4's deployment management and software development practices, Google's SRE practices and the DORA delivery metrics define the discipline. Pipelines are now control points: NIST's Secure Software Development Framework (SP 800-218) and Executive Order 14028 shape expectations for suppliers to US government, SOC 2 CC8.1 and ISO/IEC 27001:2022 Annex A 8.25 to 8.32 cover secure development and change, PCI DSS Requirement 6 covers payment software and DORA covers ICT change at EU financial entities. The DORA metrics themselves are change lead time, deployment frequency, change fail rate, failed deployment recovery time and deployment rework rate, and Google's SRE practice caps operational work at half of an engineer's time so that the rest goes to engineering.

Related roles

Engineering Manager

Explore Further

Guides and definitions from the GRC Knowledge Center and the What-is glossary, chosen for this role.

Frequently asked questions

The DevOps Engineer builds and runs the delivery pipeline and the platforms it deploys to: CI/CD pipelines and infrastructure as code, environments, deployments and release automation, observability, SLOs and reliability practices, and the on-call and incident response for the platforms they run. They coordinate releases with change management and drive post-incident improvements and automation. The pipeline is now a control point under SSDF, SOC 2 CC8.1 and ISO 27001 Annex A 8.25 to 8.32, so the records around it matter as much as the code.

Release Management tracks each release and deployment with its scope, the approved changes behind it and its status across environments, so the DevOps Engineer has a record of what went where and who approved it, without maintaining it by hand in a wiki. The pipeline keeps doing the deploying; SmartSuite is the record of the release that the Change and Release Manager, the Engineering Manager and an auditor can read. Post-release issues tracked against the release make the recovery-time conversation after a failed deploy factual.

Event & Alert Management links observability alerts to on-call rotations and incident records, so an alert that needs a human reaches the engineer on call in On-Call Management and, if it becomes an incident, the incident record starts with the alert attached. The DevOps Engineer sees which alerts fired, who was paged and what was done, which is the raw material for tuning noisy alerts and improving SLOs. The Systems Administrator and the Security Analyst work from the same alert and incident records.

IT Incident Management runs platform incidents with a timeline and post-incident actions, so the DevOps Engineer records what happened, when and what was done during the incident, and the improvements agreed afterwards are tracked as actions rather than left in the retrospective notes. The timeline gives the DORA recovery-time measure a source, and the post-incident actions, whether automation, alert tuning or a reliability fix, carry an owner and a status until closed. Repeated incidents on the same platform become visible across records.

Change Management lets the DevOps Engineer raise and track changes for infrastructure and pipeline updates in the same change records the Change and Release Manager uses, so an infrastructure change goes through the same approval and scheduling as an application release instead of around it. The IT Operations Director and the Engineering Manager see planned changes alongside releases and open incidents, which is where conflicts are caught. For regulated environments such as PCI DSS or DORA, the change record is the evidence.

SmartSuite is the system of record for releases, changes, alerts, on-call and incidents, not a replacement for the pipeline, the infrastructure-as-code tooling or the observability stack that produce them. A team starts by recording releases and changes in SmartSuite as they happen and running on-call and incidents from it, so operations and engineering share one record. The build and deploy tooling keeps running where it is; what changes is that the approvals, release status and post-incident actions are in one place.

See SmartSuite for your role

Start a free trial, or book a demo and we will walk through your role's workflows in SmartSuite.