Delivery Operations Manager
Compensation
Salary undisclosedDescription
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:
Delivery Operations Manager is the operational backbone of a Business Line (BL). You run the day-to-day machinery of Amplified Squads, keep the Delivery Intelligence Platform accurate, and make sure Engineering teams decide on data they trust. Paired with a Delivery Lead, you own the daily operating rhythm — and automate the parts of it that shouldn't need a human in the first place.
- Amplified Squads Operations
- Stand up new squads: members, consultants, boards, filters, release versions and communication channels.
- Keep every squad tied to its goal and initiative; route missing goals, initiatives and PRDs to the Delivery Lead with the specific gap named.
- Track each squad's lifecycle from formation to dissolution, and confirm or re-date every dissolution with stakeholders before the day.
- Maintain squad membership and allocation data as people join, rotate and roll off.
- Delivery Intelligence Platform Stewardship
- Treat the platform as the single source of truth for your BL: complete, current and reconciled to Jira.
- Act on the signals it raises — stale epics, missing dates, slipping squads — before they reach a review.
- Test new platform capabilities and report edge cases with reproducible examples.
- Log every recurring data gap as a rule, validation or automation candidate, so the platform gets smarter each quarter.
- Release and Change Communication
- Run daily release management: confirm planned deployments landed, validate components on the release ticket, and verify release notes with owners.
- Publish release announcements that engineering, product and client-facing teams can act on without follow-up.
- Keep release records traceable — what shipped, when and from which squad — as our healthcare clients expect.
- Workflow Hygiene
- Run daily checks on the work hierarchy: components, epic-to-goal links, past-due and approaching-due epics.
- Hold zero past-due epics as a standing bar, driving date updates or closure with the accountable owner.
- Field Jira workflow, field and board change requests; implement the agreed ones and keep the configuration consistent across squads.
- Cadence and Ceremonies
- Set up and maintain recurring Product Line and BL syncs; coordinate ad-hoc initiative meetings.
- Publish decisions and minutes to Confluence and Slack promptly after each meeting, while they are still fresh and actionable.
- Recommend ceremonies to shorten or retire, using attendance and decisions taken as evidence.
- Reporting and Insights Data
- Gather and validate the quantitative layer for executive reporting, recurring delivery briefs and ad-hoc leadership requests.
- Make accuracy your signature: every number reconciles to source before the Delivery Lead adds the narrative.
- Knowledge and Enablement
- Maintain the playbooks, runbooks and FAQs that explain how squads, releases and tooling work.
- Onboard new squad members, engineers and consultants to the Amplified Squads model and our tooling.
- Answer day-to-day "how do we…" questions so teams spend their time building, not navigating process.
- Automation and AI Agents
- Use the platform, Jira automation and AI assistants (Claude or equivalent) in your daily work.
- Operate and tune the AI delivery agents that run hygiene checks and summaries, and catch where their output is wrong.
- Keep a running list of your manual tasks with frequency and time cost; automate or retire at least one per quarter.
- 2+ years in delivery operations, PMO, project coordination, release coordination or Jira administration in a technology company.
- Advanced Jira user: JQL, boards, quick filters, components, versions and bulk operations; working knowledge of Jira automation rules.
- Fluent in Confluence and Slack as working tools, not just channels.
- Detail-obsessed without being slow: you catch the blank field and the wrong component on the first pass.
- Disciplined follow-up: you chase owners persistently and politely, and close loops without escalating everything.
- Hands-on with AI tools in daily work — you can show an example, not describe an intention.
- Your first question about a repetitive task is "why is a human doing this?"
- Clear writer: your release notes, runbooks and announcements need no follow-up questions.
- Scripting (Python, Apps Script or SQL) is a plus.
- Background in AdTech, HealthTech or data-intensive SaaS is a plus.
Stack
- Posted
- Mar 12, 2025
- Last seen
- Oct 22, 2026
- First seen
- Oct 22, 2026


