Find Jobs
Find Jobs Near You – Available Work in Your Location
Skip to job details
M
Masco
Technical Product Owner, Enterprise POS
Career Insights for Product Owner
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 Michigan data
Review key factors to help you decide if this role fits your goals. How is this calculated?
What they do
A Product Owner is a member of the product development team who writes user stories and defines the tasks needed for engineers to work using the Agile Development Framework.
$99,740 / year median in Michigan
+18% projected growth
Job Description
Role Summary The Technical Product Owner, Enterprise POS gathers POS demand and the owner of the prioritized Masco enterprise POS roadmap. This role translates business demand from Business Units, F unctions, Centers of Excellence and other partners into defined, prioritized epics the build teams deliver . The Technical Product Owner b ridg es the "what and why" of business need to the "how and when" within enterprise platform delivery . The T echnical Product Owner leads the intake , a cross-functional POS council, coordinates releases across the engineering and BI teams , and owns adoption of what ships. This role is central to ensuring the enterprise POS platform builds what the business needs most and provides transparency for where the enterprise platform is headed in the future. What You'll Own Demand Intake & Prioritized Roadmap Own the single structured intake for POS needs across Business Units, Functions, Centers of Excellence and other partners Own the prioritized enterprise POS roadmap, reconciling inbound demand with top-down enterprise and BU strategic priorities. Proactively originate roadmap candidates from usage patterns, retailer data developments, and observed capability gaps . Stakeholder Alignment Establish and lead the cross-functional POS council, arbitrating priorities and relieving leadership of ad-hoc intake. Represent all POS consumers across a variety of use cases and department-specific requirements. Publish the roadmap and communicate status, tradeoffs, and decisions with clear reasons . Escalate genuine priority deadlocks to the Data and Tech Leade r with a clear recommendation. Epic Definition, Acceptance & Design Handoff Define epics — problem statement, business value, and success criteria — and maintain their priority order for the delivery leads. Route prioritized work through the Enterprise Data Architect's design-authority checkpoint so approved work fits the enterprise model before build begins. Accept completed epics against their success criteria and formally close roadmap items. Release Coordination, Adoption & Change Communication Own the release calendar and cross- team go-live coordination for releases spanning data engineering and BI. Communicate master-data changes and historical restatements to consumers in advance, with clear "what will change and why" summaries. Drive adoption of enterprise assets through training coordination, change communication, and usage follow-through. Lead cross-team dependency and milestone management . Demand Team Leadership & Capacity Allocation Hire, develop, and manage the Business Data Analyst function within the demand organization. Allocate BDA capacity across Business Units and functions as a prioritized, visible resource. Act as project manager for work across the tech and data team to ensure accurate and timely delivery Set standards for requirements, user-story, and acceptance- criteria quality within the demand organization. Documentation & Knowledge Management Own the published roadmap, epic definitions, release calendar, and release/restatement communications. Maintain the POS council decision log so priority decisions are documented and durable. Establish intake documentation standards — what a request must contain to be triaged.