Technical Delivery Manager — DataOps
Business Analytics & Technology (BAT) Team
- Golden State Medical Supply
________________________________________
The role
The Technical Delivery Manager owns the execution and on-time, on-quality delivery of all work moving through the BAT DataOps function — data engineering, QA, BI & Data Analytics. They are accountable for how and when work ships: tracking it, unblocking it, holding people to their commitments, and giving leadership a reliable picture of where delivery stands.
Two Things Sit At The Center Of This Role
- Owner and SME of the Data-Driven Scrum (DDS) process. This person becomes the authority on how DDS runs for BAT — the one who knows the framework cold, operates it day to day, coaches the team on it, and keeps it disciplined and consistent. They don't just work within DDS; they own it.
- Owner of DataOps delivery discipline and continuous improvement. They hold the team to the operational standard and keep raising it — consistency, quality, and predictability across the teams. They do not author the technical DataOps framework itself (that's owned by architecture and engineering); they make sure the discipline is held, enforced, and continuously improved.
This is a delivery-accountability and operational-discipline role, not a coding or architecture role. They don't design data models or write pipelines, they make sure the work the architects scope and the product owner prioritizes actually gets built, tested, and delivered, and that the function operates to a consistent standard. They need enough technical fluency to hold a credible conversation with a data engineer and tell the difference between work that's genuinely hard and an estimate that's padded.
________________________________________
What they'll do
Own the DDS process
- Be the SME and operational owner of Data-Driven Scrum at BAT — run the cadence, enforce it consistently, and coach the team on it.
- Own intake, sizing, item flow, and estimate review/sign-off within the DDS framework.
- Establish and enforce a consistent, repeatable approach to estimating DataOps work so forecasting is reliable.
Own DataOps delivery discipline & continuous improvement
- Hold the team to the operational standard and quality bar, enforcing adherence consistently across in-house and offshore teams.
- Drive process and technical-debt improvements as first-class tracked work; run retrospectives that produce real change.
- Continuously raise delivery predictability and quality — note that the technical DataOps framework (pipeline standards, CI/CD, quality gates) is authored by architecture/engineering; this role ensures it's followed and improved, not invented.
Own delivery
- Own delivery of all committed DataOps work from ready-to-build through done, against agreed timelines and acceptance criteria.
- Be the single accountable owner for whether commitments are met — chase, unblock, and escalate rather than report after the fact.
- Hold the teams accountable to their commitments, estimate accuracy, and quality gates.
- Manage dependencies between DataOps and the BI/Analytics and App Dev tracks so hand-offs don't stall delivery.
- Coordinate the delivery side of the Microsoft Fabric migration as tracked, estimated, accountable work.
- Maintain a current, trustworthy view of what's in flight, blocked, and at risk in Jira, and produce a reliable weekly delivery snapshot for leadership.
- Define and manage the team's weekly delivery KPIs.
________________________________________
Expectations
- DDS runs consistently and well, with one clear owner who knows it cold and keeps the team disciplined on it.
- DataOps delivery gets measurably more disciplined, consistent, and predictable over time.
- Delivery commitments are met reliably, and when they're at risk, leadership knows early — not after the miss.
- Estimates get more accurate over time and become something we can plan against.
- Blockers get cleared fast.
- Teams deliver to the same standard.
- Leadership gets a dependable weekly read on delivery without anyone having to chase status.
________________________________________
Skills & Experience
- 5+ years owning technical delivery for data, analytics, or software teams, including coordination of offshore/vendor teams.
- Deep command of an agile delivery framework and the ability to be the SME and process owner for it — ideally Data-Driven Scrum or a comparable non-time-boxed model.
- A track record of raising the delivery discipline of a team — standards adherence, estimation discipline, quality, and continuous improvement.
- A track record of owning delivery outcomes — timelines, throughput, quality — not just facilitating process.
- Strong working command of Jira and agile delivery in a data context.
- Enough technical literacy to talk credibly with data engineers — understands ETL/ELT, data warehousing, and pipeline work well enough to judge complexity and call out padded estimates. Does not need to write code.
- Demonstrated ability to manage dependencies and remove blockers across multiple teams.
