> Markdown version of [/jobs/ext/3199217-dev-ops-process-change-software-architect-digital-product-engineering](https://www.wearedevelopers.com/jobs/ext/3199217-dev-ops-process-change-software-architect-digital-product-engineering). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Dev Ops/Process Change - Software Architect - Digital Product Engineering

- **Company:** W3Global Inc
- **Location:** London, UK
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Confluence, JIRA, Continuous Integration, DevOps, Systems Development Life Cycle, Release Management, DevOps Tools - Open-source, Gitlab
- **Published:** September 22, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=322a7032f72bb931

## About the Role

Eligibility - 5 years unbroken residency / Minimum 5 years of continuous UK residency, Strong DevOps/SDLC background - CI/CD pipeline design, branching strategy, release management, environment management.

 * Experience assessing and improving existing engineering processes within a delivery team (not just building new pipelines from scratch).
 * Stakeholder engagement - able to work embedded with delivery teams to understand current-state process, build trust, and land change.
 * Understanding of what AI-ready DevOps looks like (e.g. how process friction - slow CI, manual gates, poor branch hygiene - blocks AI coding assistants and agentic workflows from adding value).
 * Familiar with common CDS delivery toolchain (GitLab, JIRA, Confluence) or equivalent enterprise DevOps tooling.
 * The DevOps/Process Change role works directly with CDS delivery teams to understand their existing DevOps processes, identify process debt, and address it so those teams can get genuine value from AI-assisted delivery - not applying AI on top of broken process and expecting it to compensate.

## Description

*
Embed with individual CDS delivery teams to assess current DevOps practice - CI/CD, branching, release cadence, testing gates, review process.

 * Identify process debt that limits the value of AI coding/delivery tools (e.g. slow feedback loops, manual approval bottlenecks, inconsistent environment management).
 * Work with teams to remediate process debt in a practical, incremental way - not a big-bang process overhaul.
 * Advise teams on how to structure process so AI-assisted development.