Find Jobs
Find Jobs Near You – Available Work in Your Location
Skip to job details
M
Medica
Tech Product Owner IV
Career Insights for Cloud Product Manager
See where this job fits in the broader career landscape. Knowing your career path helps you see what's possible from here.
Scorecard
Based on Minnesota data
Review key factors to help you decide if this role fits your goals. How is this calculated?
What they do
A Cloud Product Manager is responsible for managing a strategy to develop and/or sell cloud services products. This may involve planning and assisting in the development, marketing and distribution of the product.
$157,930 / year median in Minnesota
+2% projected growth
Job Description
Tech Product Owner IV Medica 401(k) United States, Minnesota, Hopkins 401 Carlson Parkway (Show on map) Aug 24, 2026
Description Medica is a nonprofit health plan with more than a million members that serves communities in Minnesota, Nebraska, Wisconsin, Missouri, and beyond. We deliver personalized health care experiences and partner closely with providers to ensure members are genuinely cared for. We're a team that owns our work with accountability, makes data-driven decisions, embraces continuous learning, and celebrates collaboration - because success is a team sport. It's our mission to be there in the moments that matter most for our members and employees. Join us in creating a community of connected care, where coordinated, quality service is the norm and every member feels valued. This Technical Product Owner (TPO) for the Contact Center Knowledge Management Platform is responsible for defining, prioritizing, and delivering capabilities that enable agents, supervisors, and customers to access accurate, timely, and relevant knowledge through Salesforce-based solutions. The TPO serves as the bridge between business stakeholders, Contact Center Operations, Knowledge Management teams, and technical delivery teams to ensure the platform supports operational excellence, customer experience, compliance, and continuous improvement objectives. The Technical Product Owner (TPO) is the tactical owner of a team's backlog and capacity. While the Technical Product Manager (TPM) sets strategic direction at the capability level, the TPO ensures the team delivers the highest-value work in alignment with capability priorities. Acting as the single-threaded owner of the team backlog, the TPO bridges business, technology, and delivery execution, consolidating responsibilities traditionally split between a Product Owner and Scrum Master. The TPO champions MDF principles by fostering transparency, enabling disciplined delivery, and ensuring predictable flow of work. They shield the team from external disruptions, maintain clarity on priorities, and ensure commitments align with proven capacity Key Accountabilities Backlog Ownership & Grooming Translate prioritized capability epics (from TPM ) into clear backlog items (features, user stories, technical enablers)
Define acceptance criteria in partnership with the Technical Lead (TL) and ensure backlog items are "ready" for development
Maintain a healthy backlog sequenced based on value, risk, and dependencies
Reject or escalate any "backdoor" requests that bypass MDF intake Capacity & WIP Alignment Partner with the Delivery Leader to ensure backlog aligns to actual team capacity
Respect and enforce WIP limits so the team is never overcommitted
Actively remove work when urgent items are added per EDC governance Prioritization Integration Represent the team during prioritization sessions and ensure EAC and EDC decisions are reflected in the backlog
Ensure RTB (Run-the-Business) items, enhancements, and strategic initiatives are prioritized together within the backlog Sprint & Iteration Leadership Lead backlog refinement, sprint planning, and iteration reviews
Ensure team goals tie back to capability and enterprise priorities
Lead all Scrum Master activities, including facilitating ceremonies and promoting agile practices Execution Alignment Partner with the Technical Lead (TL) on delivery-the TPO owns the "what/why," at the feature level while the TL owns the "how"
Make trade-off decisions daily if necessary to keep delivery aligned with priorities
Coordinate dependencies with other teams and escalate blockers or capacity issues to EDC Stakeholder Engagement A point of contact for business stakeholders
Provide transparency into progress, risks, and delivery metrics
Ensure feedback loops with TPM, business users are fast and continuous to validate outcomes early Continuous Improvement & Metrics Capture learnings from retrospectives and incorporate them into future sprints
Track delivery metrics: say/do ratio, cycle time, throughput
Validate delivered stories/features against acceptance criteria and business outcomes
Report progress and risks to TPM, Delivery Leader, and stakeholders Accountabilities A single, transparent backlog for the team that reflects enterprise priorities
Backlog items are outcome-oriented, clear, and feasible before sprint planning
Sprint commitments align with proven capacity and are delivered predictably
Completed work delivers measurable business outcomes-not just features
Transparent communication with stakeholders-no surprises Role Partnerships in