Senior Delivery Operations Manager

About the Delivery Amplification Office:

The Delivery Amplification Office (DAO) is not a traditional PMO. We are an AI-native delivery function that makes engineering faster, clearer and easier to steer.

We run on the following two foundations.

Amplified Squads is our AI-native operating model. Small, goal-aligned squads with AI built into how they plan, track, report and ship. Agents and automation handle intake, hygiene and status, so people spend their time on decisions and delivery.

Our Delivery Intelligence Platform is the centre of everything we do. It is an always-on layer across Jira, Confluence, Slack and our people systems that turns delivery activity into live signal: squad health, risk, throughput, release status and executive briefs. Every squad, epic, release and report flows through it — and Delivery Operations keeps it true.

What You’ll Do:

The Senior Delivery Operations Manager owns the operating system of one or more Business Lines (BLs): the data, cadence, tooling and automation that Amplified Squads run on. Paired with a Senior Delivery Lead as daily working partner and growth-path mentor, you move from keeping the system accurate to redesigning it — on a deliberate path toward Delivery Lead.

1. Operating Model Stewardship
   • Own Amplified Squads health for 1–2 BLs: lifecycle adherence, goal coverage, squad lifespan and dissolution postponements.
   • Set and enforce operating conventions (naming, release versions, mandatory fields, dissolution checks), and document them in the DAO playbook.
   • Turn squad retrospectives and survey data into concrete changes to how squads form, run and close.
2. Delivery Intelligence Platform Ownership
   • Act as the operations voice of the platform: define business logic, data-quality rules and acceptance criteria, and run UAT with the Delivery Engineers who build it.
   • Drive adoption so squads, EMs and PMs work from the platform, not from side spreadsheets.
   • Turn its signals into early warnings that reach your Delivery Lead before a review does.
3. Automation and AI Agents
   • Maintain the ops automation backlog for your BLs: every recurring task with its frequency, effort and automation path (Jira rule, platform capability or AI agent).
   • Ship at least one automation per quarter that retires a recurring manual task, and report the hours returned.
   • Design and tune AI delivery agents for hygiene, summarisation and follow-up, with clear checks on their accuracy.
   • Contribute proven patterns to the DAO's Agentic Framework for cross-BL adoption.
4. Reporting and Delivery Insights
   • Own the quantitative layer of executive reporting and recurring delivery briefs for your BLs, reconciled to source.
   • Draft the first qualitative read — what moved, why, and what's at risk — for your Senior Delivery Lead to sharpen.
   • Track the metrics the operating model is judged on: throughput, cycle time, WIP and goal coverage.
5. Tooling and Workflow Governance
   • Own Jira configuration standards across your BLs: workflows, issue types, fields and boards.
   • Assess the impact of every workflow change request, align stakeholders on edge cases, and roll changes out without breaking reporting.
6. DAO-wide Ops Domain
   • Own one operations domain for the whole DAO, such as release and change management, cadence design, or the reporting data layer.
   • Define the standard other Delivery Operations follow in that domain, and spot-check their output.
7. Enablement and Team Leverage
   • Own the playbooks and onboarding that teach teams the Amplified Squads model and our tooling.
   • Review and coach the work of Delivery Operations peers.
   • Work against explicit Lead-readiness milestones agreed with your Senior Delivery Lead: run a BL review solo, lead a stakeholder alignment, own an escalation end to end with a recommendation.
   • Act as Delivery Lead backup for your BL during leave or peak load.

Who You Are:

• 4+ years in delivery operations, PMO, program coordination or Atlassian administration in a fast-moving technology company, including 1+ year owning operations for a team or BL rather than executing tasks.
• Expert in Jira: advanced JQL, dashboards, workflow and automation rules, and how field and screen configuration drive data quality.
• Proven automator: you have retired a manual process with Jira automation, scripts or AI, and can say how many hours it returned.
• Hands-on with AI tools (Claude, Cursor or equivalent) in operational workflows — demonstrated, not aspirational.
• Comfortable with data: you reconcile sources, spot anomalies, and read throughput, cycle time and aging.
• Influence without authority: EMs and PMs keep their work current because you made it easy, not because you chased them.
• You treat process debt the way engineers treat tech debt, and you write operating docs people actually follow.
• You want the path to Delivery Lead and can name your own gap to it.
• Scripting or SQL and BI tooling are a plus.