Technology Product Manager, Workforce Data

We need to output HTML fragment with sections: About the role? Actually the posting includes intro paragraph about joining MetLife's Global Technology team. That could be "About the role" or maybe. Then "The Opportunity" maybe as a heading? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use only when posting has real specific content. So we need to decide sections. We have content: - Intro paragraph: "When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group..." This is about the role. Could be "About the role". - Then "The Opportunity" paragraph describing role accountability. Could be considered "About the role" as well, but maybe we keep as part of same section. - Then "Key Responsibilities" list. - Then "Required Qualifications" list. - Then "Preferred Qualifications" list. - Then "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." That's schedule info. So we can create a Schedule section. - Then "The expected salary range for this position is $144,100 - $213,100. This role may also be eligible for annual short-term incentive compensation." That's Pay section. - Then "Benefits We Offer Our U.S. benefits address holistic well-being..." That's Benefits section. - Then "About MetLife" paragraph about company. Could be "About the company" but not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not create a heading for that; we could incorporate into About the role? But it's about company, not role. The instruction: "Prefer a few substantive sections over many thin ones." We could omit About MetLife entirely? But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Since we cannot create a heading not in list, we could put it as a

under maybe "About the role" or just as a generic paragraph without heading? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use

for section headings (e.g. About the role...). It might be okay to have other headings but they'd be non-standard. Safer to stick to allowed headings and put the About MetLife content under a generic

without heading? But then we lose structure. Perhaps we can treat it as part of "About the role" (since it's about the company context). Might be acceptable. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, accommodation, drug-free workplace, Massachusetts lie detector law, posting duration. Those are boilerplate; we should remove them. Also remove "For more information regarding MetLife’s U.S. benefits, please click here." That's application instruction? It's a link; we can remove. Also remove "All incentives and benefits are subject to the applicable plan terms." That's part of benefits? Might be considered boilerplate but it's about benefits; maybe keep? It's generic; but we can keep as part of benefits paragraph. We need to preserve all substantive information: responsibilities, qualifications, preferred qualifications, location expectation, salary range, benefits description, intro, opportunity, about MetLife. We need to format lists with

• . Let's extract sections: About the role (intro + opportunity). Combine: Intro: "When you join MetLife’s Global Technology team, you’ll be part of a forward-thinking group dedicated to shaping the future of digital solutions for customers worldwide. You’ll develop, maintain and support technology applications and delivery, leveraging AI, automation, and contemporary ways of working to enhance experiences and drive business outcomes. Your work will simplify complex processes, improve tech resiliency, and ensure high-performing, seamless solutions that power life’s most important moments. In this dynamic environment, you’ll collaborate with talented peers across teams and functions, expanding your skills in impactful ways. Ready to push boundaries and set new industry standards? Join us and help drive the future of technology forward." Opportunity: "The Opportunity The Technology Product Manager for Workforce Data is accountable for shaping and advancing the product strategy, roadmap, and measurable outcomes for enterprise workforce data capabilities. The role connects workforce needs, user problems, data opportunities, and technology delivery into a clear product direction that improves access to trusted workforce information and enables analytics, reporting, operational processes, and responsible AI use cases. Working across HR, Technology, Data, Architecture, Risk, Privacy, Legal, and delivery partners, this role will lead through influence rather than direct people management. The product manager will define problems and outcomes, make evidence-based priority decisions, align stakeholders around trade-offs, and help multidisciplinary teams deliver scalable data products and platform capabilities." We can combine into one paragraph or two. Responsibilities: list items from "Key Responsibilities". Each bullet starts with a verb. We'll extract each sentence. Let's list: - Own the Workforce Data product vision, strategy, and multi-horizon roadmap, translating workforce priorities and user needs into clear outcomes, capabilities, sequencing, and investment choices. - Lead discovery with workforce stakeholders and data consumers to identify high-value problems, define target users and use cases, test assumptions, and establish measurable product outcomes. - Define and manage the product portfolio spanning trusted workforce data, curated data domains, reusable data products, analytical and semantic layers, reporting enablement, archival needs, and AI-ready consumption patterns. - Create transparent prioritization and decision frameworks that balance business value, user impact, risk reduction, data quality, regulatory obligations, architectural integrity, operational health, delivery capacity, and cost. - Partner with architecture, data engineering, analytics, integration, security, privacy, risk, and platform teams to turn product intent into feasible capabilities, release plans, acceptance criteria, and production-ready outcomes. - Establish and maintain a clear product backlog and outcome-based roadmap, ensuring work is sufficiently defined, dependencies are visible, trade-offs are resolved, and teams understand the purpose and expected value of each increment. - Drive stakeholder alignment across HR and Technology by communicating product choices, dependencies, risks, readiness, and progress in concise business and technical language appropriate for senior audiences. - Define product health and value measures, including adoption, data quality, timeliness, reliability, usability, risk reduction, cycle time, and value realization, and use evidence to refine priorities. - Champion workforce data governance, privacy-by-design, security, lineage, access controls, retention, responsible AI, and ethical use of employee data throughout discovery, design, delivery, and operation. - Guide change, adoption, and product operating practices by clarifying ownership, decision rights, engagement models, release communications, feedback loops, and ongoing lifecycle management. - Serve as a trusted product thought partner and subject-matter leader, bringing strong judgment to ambiguous problems and influencing across organizational boundaries without relying on formal authority. Requirements: Actually "Required Qualifications" list. We'll treat as Requirements section? The allowed headings include Requirements and Qualifications. Could use Qualifications for required, and maybe Skills for preferred? But we have both Required and Preferred Qualifications. We could make a Qualifications section for required, and a Skills section for preferred? But preferred qualifications are more like qualifications too. However we can follow instruction: Use headings as appropriate. We could have "Required Qualifications" as a heading? Not in list but similar to Qualifications. The list includes Qualifications as a possible heading. So we can use

  Qualifications

  for required qualifications. And maybe

  Skills

  for preferred qualifications? Or we could combine both under Qualifications with subheadings? But we must not create headings with filler text. Better to have two sections: Qualifications (required) and Skills (preferred). However preferred qualifications include experience, certifications etc. Could be considered Skills. Let's extract required qualifications bullets: - 7+ years of progressive experience in technology product management, data products, enterprise data platforms, workforce technology, analytics, or a closely related discipline, with experience leading complex products through influence rather than formal authority. - Demonstrated ownership of product strategy and roadmaps for enterprise technology or data capabilities, including discovery, prioritization, delivery partnership, adoption, measurement, and lifecycle decisions. Adept at connecting data product investments to measurable outcomes. - Strong understanding of modern data product concepts, including source-to-consumption flows, data domains, data quality, metadata, lineage, semantic models, APIs or data services, analytics consumption, and platform thinking. - Experience translating complex workforce, HR, regulatory, analytical, or operational needs into user-centered product outcomes and clear delivery requirements. - Proven ability to make and communicate difficult trade-offs across value, risk, architecture, cost, time, quality, and stakeholder priorities. - Experience partnering effectively with data engineering, architecture, analytics, integration, security, privacy, risk, operations, and business teams in a complex enterprise environment. - Ability to define outcome measures and use qualitative and quantitative evidence to assess product value, adoption, health, and areas for improvement. - Excellent executive communication, facilitation, negotiation, and influence skills, with the ability to create clarity from ambiguity and build alignment across diverse stakeholders. - Working knowledge of Agile and product operating practices, including discovery, backlog management, iterative delivery, planning, dependency management, release readiness, and feedback loops. - Bachelor’s degree in technology, data, analytics, business, human resources, or a related field, or equivalent practical experience. Preferred qualifications bullets: - Experience with workforce or HR data, including effective-dated data, organizational structures, worker lifecycle data, historical data, security-sensitive attributes, and downstream reporting or analytics. - Experience with Oracle HCM or a comparable enterprise HCM platform and its data, reporting, integration, and security considerations. - Exposure to modern cloud data and analytics ecosystems such as Azure, Databricks, SQL, Power BI, data lakes or lake houses, data virtualization, or related platform services. - Experience product-managing data modernization, legacy retirement, archival, integration simplification, governed self-service analytics, or enterprise data product adoption. - Practical understanding of AI and advanced analytics use cases, AI-ready data, responsible AI controls, and the risks associated with workforce data. - Product management, Agile, data management, analytics, cloud, or HR technology certifications. Location Expectation: "Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office." That's schedule. Pay: "The expected salary range for this position is $144,100 - $213,100. This role may also be eligible for annual short-term incentive compensation." Benefits: paragraph about benefits. We also have "All incentives and benefits are subject to the applicable plan terms." Could be included in benefits paragraph. We need to remove boilerplate: EEO statement, accommodation, drug-free workplace, Massachusetts lie detector law, posting duration, "For more information regarding MetLife’s U.S. benefits, please click here." Also maybe "All incentives and benefits are subject to the applicable plan terms." is not boilerplate but it's a qualifier; we can keep. Now produce HTML fragment:

  About the role

  ... combined intro and opportunity ...

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Schedule

  Location Expectation: This is a hybrid role requiring a minimum of 3 days per week in office.

  Pay

  The expected salary range for this position is $144,100 - $213,100. This role