Product Manager - Corporate Technology Operations

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have job description content: includes Job Summary, Job Responsibilities, Required Qualifications, Capabilities And Skills, Preferred Qualifications, Capabilities And Skills, About Us, About The Team. We need to map to sections: Possibly "About the role" (job summary), "Responsibilities", "Requirements" (maybe required qualifications), "Qualifications" (maybe preferred?), "Skills" (maybe capabilities?), "Benefits", "Pay", "Schedule". The posting mentions benefits and total rewards package, but not specific details like health care etc. It says "We offer a competitive total rewards package including base salary determined based on the role, experience, skill set and location. Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity... We also offer a range of benefits and programs to meet employee needs, based on eligibility. These benefits include comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more." Thus we have some benefits info. Pay: mentions base salary determined based on role, experience, skill set and location; possible commission-based pay etc. That's specific enough? It says base salary determined based on role, experience, skill set and location. That's somewhat generic but still mentions pay components. Should we include Pay section? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "base salary determined based on the role, experience, skill set and location." That's somewhat vague but still specific? It's not a placeholder like "varies". It says determined based on role, experience, skill set and location. That's still somewhat generic but maybe acceptable. However "Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity". That's more specific. So we can include Pay section summarizing that. Schedule: not mentioned. So omit Schedule. Benefits: we have specifics: comprehensive health care coverage, on-site health and wellness centers, a retirement savings plan, backup childcare, tuition reimbursement, mental health support, financial coaching and more. That's specific enough. Thus sections: About the role (job summary), Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (maybe capabilities?), Benefits, Pay. But we need to avoid duplication. The posting has "Required Qualifications, Capabilities And Skills" and "Preferred Qualifications, Capabilities And Skills". We could combine into Requirements (required) and Qualifications (preferred) and maybe Skills separate? However the instruction says use headings like Requirements, Qualifications, Skills. We could map Required Qualifications to Requirements, Preferred Qualifications to Qualifications, and maybe Skills to something else? But the Required section already includes capabilities and skills. Might be redundant to have Skills separate. Perhaps we can treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and we could omit Skills section because it's covered. Or we could create Skills section for capabilities like SQL, Excel, etc. But that would duplicate content. Better to follow: Use Requirements for required qualifications, Qualifications for preferred qualifications, and maybe Skills for capabilities like SQL, Excel, etc. But the Required section already includes capabilities and skills. However we can still extract specific skills from Required and Preferred and put them under Skills. But that would be summarizing/inventing? We need to preserve all substantive information, not invent or summarize away detail. If we extract skills, we are not inventing, just pulling out details. That's okay as long as we keep them. But we must not repeat content unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can move details into appropriate sections but must keep them. It's okay to reorganize. Thus we can have:

About the role

with job summary paragraphs.

Responsibilities

with

• list of responsibilities.

  Requirements

  with required qualifications (5+ years experience, advanced knowledge of product development lifecycle, proven ability to lead product life cycle activities, executive dashboarding and conversational analytics, advanced knowledge of product development lifecycle and requirements engineering, proficiency in backlog ownership, prioritization frameworks, experience with data products, hands-on experience with AI-powered conversational product workflows, analytical skills proficiency in data analysis using SQL, Excel, RStudio or BI tools). We'll list as
  .

  Qualifications

  with preferred qualifications (demonstrated prior experience in highly matrixed organization, discovery and research, stakeholder management, experience with enterprise data platforms, familiarity with data governance, knowledge of Jira/Azure DevOps, Confluence, SQL/BI platforms). We'll list.

  Skills

  maybe we could list specific technical skills: SQL, Excel, RStudio, BI tools (Tableau), Jira, Azure DevOps, Confluence, AI-powered conversational product workflows (Databricks Genie spaces), semantic/metric layer design, data contracts, governance, quality and lineage, etc. But these are already in required/preferred. Might be duplication. Perhaps better to omit Skills section to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine Required and Preferred into Requirements and Qualifications, and maybe not have Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now we need to strip boilerplate: About US, About The Team, EEO, etc. Remove those. We need to keep all substantive information: job summary, responsibilities, required qualifications, preferred qualifications, benefits, pay. We must not repeat job title as heading. Not include Job ID. Now produce HTML fragment. Let's craft. About the role: combine job summary paragraphs: "As a Product Manager in Corporate Technology Operations you are an integral part of the team that innovates new product offerings and leads the end-to-end product life cycle. As a core leader, you are responsible for acting as the voice of the customer and developing profitable products that provide customer value. Utilizing your deep understanding of how to get a product off the ground, you guide the successful launch of products, gather crucial feedback, and ensure top-tier client experiences. With a strong commitment to scalability, resiliency, and stability, you collaborate closely with cross-functional teams to deliver high-quality products that exceed customer expectations. You will serve as the voice of the customer, own and refine the product backlog, and partner closely with engineering to deliver high-quality outcomes. You will also lead the elicitation and validation of business requirements and apply analytics across diverse datasets. Hands-on ownership of executive dashboards and conversational analytics is essential. You will highlight the right KPIs, enable intuitive drilldowns, and craft clear narratives that support decision-making—with a strong focus on clarity, signal-to-noise ratio, and actionability." We can split into

  tags maybe one paragraph. Responsibilities: list items from "Job Responsibilities". The posting includes bullet-like sentences. We'll create

  • each. List: - Develops a product strategy and product vision that delivers value to customers - Manages discovery efforts and market research to uncover customer solutions and integrate them into the product roadmap - Owns, maintains, and develops a product backlog that enables development to support the overall strategic roadmap and value proposition - Builds the framework and tracks the product's key success metrics such as cost, feature and functionality, risk posture, and reliability - Product strategy and vision: Define and communicate a customer-centric vision and outcome-driven roadmap for an enterprise-wide Corporate Technology product; align priorities across a highly matrixed environment - Backlog ownership and delivery enablement: own, maintain, and prioritize the product backlog; write clear, testable user stories and acceptance criteria; lead refinement, sprint planning, and release planning with engineering and UX - Requirements and solution design: Lead the elicitation, documentation, and validation of business requirements; create process and data flow diagrams, and specifications - Data-driven decisioning: Utilize analytics to extract insights from large, heterogeneous datasets; quantify problem size, expected value, and success criteria; partner with UX/Design to feed insights into the roadmap - UAT and quality: Translate requirements into acceptance tests; support UAT planning and execution; triage defects; drive continuous improvement to reduce rework and production issues. Note some duplicates: first few items similar to later detailed ones. We'll keep all as given; maybe combine but preserve all. We'll keep them as separate li. Requirements: list required qualifications. From "Required Qualifications, Capabilities And Skills": - 5+ years of experience or equivalent expertise in product management or a relevant domain area - Advanced knowledge of the product development life cycle, design, and data analytics - Proven ability to lead product life cycle activities including discovery, ideation, strategic development, requirements definition, and value management - Executive Dashboarding and Conversational Analytics: Lead the lifecycle of dashboarding and executive reporting products— standardize metric definitions, ensure data quality and reliability, and deliver intuitive visualizations; manage change control and adoption with senior stakeholders - Advanced knowledge of the product development lifecycle and requirements engineering; proven leadership across discovery, ideation, strategic development, requirements definition, and value management - Proficiency in backlog ownership, prioritization frameworks (e.g., RICE, WSJF), and writing high-quality user stories and acceptance criteria - Experience working with data products, including semantic/metric layer design, data contracts and governance, quality and lineage - Hands-on experience with AI-powered conversational product workflows and interfaces such as Databricks Genie spaces - Analytical skills: proficiency in data analysis using SQL, Excel, RStudio or BI tools applied to diverse datasets Note some duplication (advanced knowledge appears twice). We'll keep as given. Qualifications: preferred qualifications. From "Preferred Qualifications, Capabilities And Skills": - Demonstrated prior experience working in a highly matrixed, complex organization - Discovery and research: working knowledge of discovery best practices to uncover problems and opportunities; synthesize customer, stakeholder, and data insights into epics, features, and iterations that maximize value - Stakeholder management and communication; ability to influence across product, engineering, data, design, risk/control, and operations in a complex, matrixed organization - Experience with enterprise data platforms and pipelines (e.g., data lake/lakehouse, data mesh, streaming), and familiarity with data governance, lineage, and privacy/compliance in large-scale environments - Working knowledge of one or more of the following: Jira or Azure DevOps, Confluence, SQL and/or BI platforms (e.g., Tableau) Benefits: from About US section. - Competitive total rewards package including base salary determined based on the role, experience, skill set and location - Those in eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity, awarded in recognition of individual achievements and contributions. - Comprehensive health care coverage - On-site health and wellness centers - Retirement savings plan - Backup childcare - Tuition reimbursement - Mental health support - Financial coaching - More benefits (as per text) But we separated Pay and Benefits. So Benefits section should list benefits excluding pay. Pay section will cover base salary, commission-based pay, discretionary incentive compensation. Thus Benefits: - Comprehensive health care coverage - On-site health and wellness centers - Retirement savings plan - Backup childcare - Tuition reimbursement - Mental health support - Financial coaching - (and more benefits) We can include "and more benefits" as a li. Pay: - Base salary determined based on the role, experience,