Skip to content
DXP Team Structure

DevOps Engineer

Layer: Operational

Scope: Account/Project

Track: devops

Mission

Section titled “Mission”

Own the CI/CD pipelines, infrastructure and delivery process that get each CMS solution safely and reliably to production.

Responsibilities

Section titled “Responsibilities”
  • Build and maintain CI/CD pipelines per platform.
  • Manage infrastructure/hosting configuration and environments.
  • Support release management, monitoring and incident response.
  • Apply security and performance best practices to the delivery pipeline.
  • Collaborate with Backend and Frontend on deployment requirements.

Objectives by level

Section titled “Objectives by level”
LevelWhat success looks like
OperationalPipelines, environments and releases run reliably and ship on time.

Reporting & management

Section titled “Reporting & management”
  • Reports to: Tech Leader
  • Manages: No direct reports.

Decides vs. escalates

Section titled “Decides vs. escalates”
  • Decides: Implementation details within assigned DevOps tasks and the agreed design.
  • Escalates: Design ambiguities, blockers, and scope or estimate risks.

Requirements

Section titled “Requirements”

Must have

Section titled “Must have”
  • CI/CD pipeline design (GitHub Actions or equivalent)
  • Infrastructure/hosting fundamentals
  • Observability (New Relic / Datadog)
  • Version control (GitHub)

Nice to have

Section titled “Nice to have”
  • Not specified in the source material yet.

By CMS

Section titled “By CMS”
  • aem-traditional: Adobe Cloud Manager (AEMaaCS/AMS pipelines), Jenkins/Azure DevOps for on-prem or legacy deployments, Dispatcher configuration.
  • aem-eds: GitHub Actions (native pairing), @adobe/aem-cli, Adobe Edge Delivery (Fastly-based) — no separate hosting to provision.
  • optimizely-cloud: Azure DevOps, Optimizely DXP deployment CLI/API, Optimizely DXP (managed PaaS on Azure).
  • contentful: Vercel/Netlify or GitHub Actions; frontend hosting on Vercel/Netlify/AWS/Azure/GCP (Contentful itself is SaaS — no content infrastructure to manage).
Section titled “Related documents”