Principal Product Manager, Agentic

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also must not create sections with filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes pay scale info: Base Pay Scale For This Position In Phoenix, AZ/ Chicago, IL / Washington, DC in USD per year is: $173,000 - $230,000. New York, NY/ San Francisco, CA in USD per year is: $207,000 - $242,000. Additionally, candidates are eligible for a discretionary incentive plan and benefits. So we have Pay info. Schedule? Not mentioned. There's hybrid work model mentioned: Positions located in Scottsdale, San Francisco, Chicago, or New York follow a hybrid work model to allow for a more collaborative working environment. That's schedule info? It's about work model, not schedule hours. Could be considered schedule? The instruction: include Schedule section only if posting actually states them. It does mention hybrid work model, which is a schedule type. Might be considered schedule. But we need to decide. The posting says "Positions located in Scottsdale, San Francisco, Chicago, or New York follow a hybrid work model". That's about work arrangement, not explicit schedule like full-time/part-time. Might be considered schedule info. However, they didn't give explicit schedule like "Full-time". I'd lean to not create Schedule section because it's not explicit schedule like hours. Safer to omit Schedule. Benefits: The posting includes a paragraph "Some of the Ways We Prioritize Your Health and Happiness Healthcare Coverage – Competitive medical (PPO/HDHP), dental, and vision plans as well as company contributions to your Health Savings Account (HSA) or pre-tax savings through flexible spending accounts (FSA) for commuting, health & dependent care expenses.401(k) Retirement Plan – Featuring a 100% Company Safe Harbor Match on your first 6% deferral immediately upon eligibility.Paid Time Off – Flexible Time Off for Exempt (salaried) employees, as well as generous PTO for Non-Exempt (hourly) employees, plus 11 paid company holidays and a paid volunteer day.12 weeks of Paid Parental Leave Maven Family Planning – provides support through your Parenting journey including egg freezing, fertility, adoption, surrogacy, pregnancy, postpartum, early pediatrics, and returning to work. And SO much more! We continue to enhance our program, so be sure to check our Benefits page here for the latest. Our team can share more during the interview process!" That's benefits content. So include Benefits section. About the role: The posting includes "Overall Purpose The Principal Product Manager at Paze is a senior individual contributor ..." plus description. That's about the role. So include About the role. Responsibilities: The "Essential Functions" list includes many bullet-like sentences. Those are responsibilities. So include Responsibilities. Requirements: There's "Minimum Qualifications" and "Preferred Qualifications". Also "Background and drug screen." Also "Candidates responding to this posting must independently possess the eligibility to work in the United States at the date of hire." That's a requirement. Also "This position is ineligible for employment Visa sponsorship." That's a requirement. So we can combine into Requirements section. Qualifications: Might be overlapping with Requirements. The instruction says use headings like Qualifications, Skills. We need to decide what to put where. Typically Requirements = minimum qualifications, Preferred Qualifications = preferred. Skills could be extracted from qualifications like technical fluency, etc. But we must not invent or summarize away detail. We need to preserve all substantive info. We could put Minimum Qualifications under Requirements, Preferred Qualifications under Qualifications, and maybe Skills under Skills? But we risk duplication. Better to follow typical pattern: Requirements = Minimum Qualifications + eligibility + visa ineligibility. Qualifications = Preferred Qualifications. Skills = maybe technical fluency, partner with engineering, etc. However those are already in Minimum Qualifications. Could split but risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Maybe we combine Requirements and Qualifications into one section? But headings are prescribed; we can omit sections if no real specific content. We could have About the role, Responsibilities, Requirements (covering min quals, eligibility, visa), Benefits, Pay. That's five sections. That seems reasonable. We'll not include Qualifications or Skills separately to avoid thin sections. But we must ensure we don't lose preferred qualifications content. We could include them under Requirements as well, labeling as "Preferred Qualifications". That's still part of requirements. So we can include both minimum and preferred under Requirements. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Now we need to format: Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to extract content and put into appropriate format. Let's parse the posting. First, remove boilerplate: The initial paragraph about Early Warning, etc. That's about company overview; could be part of About the role? Might be considered background but not required. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview is substantive? It describes the company; maybe it's part of About the role? The "Overall Purpose" section is more about the role. The earlier paragraph about Early Warning could be considered company description, not required for the role but could be considered part of About the role? The instruction says do not repeat job title as heading; we can include company overview in About the role as prose. It's substantive info about the employer. I'd include it. But we must also remove duplicated lines: There's repeated sentence "Candidates responding to this posting must independently possess the eligibility to work in the United States at the date of hire." appears twice (once early, once later). We should include only once. Also remove EEO etc at end. Now craft sections. About the role: combine company overview and overall purpose. Company overview: "At Early Warning, we’ve powered and protected the U.S. financial system for over thirty years with cutting-edge solutions like Zelle®, Paze℠, and so much more. As a trusted name in payments, we partner with thousands of institutions to increase access to financial services and protect transactions for hundreds of millions of consumers and small businesses. Positions located in Scottsdale, San Francisco, Chicago, or New York follow a hybrid work model to allow for a more collaborative working environment." Overall Purpose: "The Principal Product Manager at Paze is a senior individual contributor responsible for defining and advancing product strategy across a complex product, product group, or customer solution. The role establishes a clear product vision, translates customer and market needs into prioritized outcomes, and leads cross-functional alignment from discovery through commercialization and ongoing optimization. Operating with a high degree of autonomy in ambiguous and evolving conditions, the Principal Product Manager influences executives, technical teams, business partners, customers, and external stakeholders to make sound product decisions, manage risk, and deliver measurable customer and business value. The Principal Product Manager will lead the strategy and development of secure, trusted payment experiences for emerging AI-enabled and agentic commerce ecosystems. The role evaluates fast-evolving technologies and protocols, defines product opportunities and user journeys, and guides new capabilities from early-stage concepts and MVPs into scalable commercial solutions." We'll put that as prose (

  ). Could split into multiple paragraphs but okay. Responsibilities: list of Essential Functions. They are sentences each starting with a verb. We'll make each as

• . List them: - Define and communicate product vision, strategy, roadmaps, and investment priorities for a complex product, product group, or customer solution, balancing customer value, business impact, risk, and technical feasibility. - Lead product work across the full lifecycle, including discovery, concept development, prioritization, requirements, delivery, launch, commercialization, performance management, and continuous improvement. - Build alignment and coalitions across Product, Engineering, Design, Marketing, Sales, Analytics, Operations, Legal, Risk, Compliance, Fraud, and other stakeholders to advance product strategy and execution. - Serve as a senior voice of the customer by synthesizing research, behavioral data, partner feedback, market signals, and experimentation into insights, product decisions, and differentiated experiences. - Translate complex customer, business, and technical needs into clear product requirements, outcomes, success measures, and decision frameworks that enable cross-functional teams to execute effectively. - Partner closely with technology leaders and engineering teams to evaluate solution options, manage dependencies and tradeoffs, and evolve products from initial capabilities into scalable, reliable solutions. - Establish and monitor product performance measures, including adoption, customer experience, financial, operational, and risk outcomes; use results to adjust priorities and improve product performance. - Influence executive and external stakeholder decisions by simplifying complex product topics, communicating tradeoffs and recommendations, and creating shared understanding across competing priorities. - Define and communicate the product vision, strategy, roadmap, and success measures for agentic commerce solutions. - Lead 0-to-1 product development and commercialization agentic commerce capabilities, operating through significant market and technical ambiguity. - Evaluate emerging protocols, ecosystem models, and industry trends to identify product opportunities, requirements, risks, and user journeys. - Partner closely with Engineering to evolve MVP capabilities into scalable, secure, and reliable product solutions. - Collaborate with financial institutions, payment networks, merchants, and ecosystem partners to define trusted commerce experiences. - Use customer research, concept testing, analytics, and experimentation to validate emerging use cases and continuously improve product-market fit. That's all. Requirements: include Minimum Qualifications, Preferred Qualifications, eligibility, visa ineligibility, background/drug screen. Minimum Qualifications list (each as bullet): - Typically has 12 or more years of progressive experience or demonstrated portfolio consistent with experience required of the role. - Bachelor’s degree or equivalent combination of education and experience. - Demonstrated experience defining product strategy, roadmaps, priorities, and measurable outcomes for complex customer-facing products or platforms. - Proven experience leading products through discovery, development, launch, commercialization, and ongoing optimization in a cross-functional environment. - Demonstrated ability to operate independently through ambiguity, make product tradeoffs, and drive major initiatives across organizational boundaries. - Demonstrated experience translating customer insights, market signals, data, and business needs into product requirements and product decisions. - Strong technical fluency and demonstrated ability to partner effectively with engineering and architecture teams on complex product solutions. - Demonstrated knowledge of payment processing, fraud prevention, digital commerce ecosystems, or related trusted-transaction capabilities. - Demonstrated ability to evaluate emerging technologies and translate uncertain or evolving capabilities into product strategy, requirements, user journeys, and scalable solutions. - Experience in payments, financial services, digital commerce, or another regulated technology environments. - Background and drug screen. Preferred Qualifications list: - Experience working across financial institutions, payment networks, merchants, technology partners, or ecosystem participants. - Experience defining product approaches for new industry protocols, interoperability models, trust frameworks, or other emerging commerce standards. Eligibility: "Candidates responding to this posting must independently possess the eligibility to work in the United States, for any employer, at the date of hire." Also "This position is ineligible for employment Visa sponsorship." We'll include those as bullet points maybe. We'll combine all into a single
  under Requirements. Benefits: list of benefits as bullet points. From paragraph: - Healthcare Coverage – Competitive medical (PPO/HDHP), dental, and vision plans as well as company contributions to your Health Savings Account (HSA) or pre-tax savings through flexible spending accounts (FSA)