J.P. Morgan Wealth Management - Vice President Product Owner

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must include only sections with real specific content. Let's parse job description. Content includes: - About the role: description of role (first paragraph). So we can have

About the role

with

containing that description. - Responsibilities: list of responsibilities (bulleted). So

Responsibilities

with

• each. - Required qualifications, capabilities, and skills: includes required qualifications. Could be split into Requirements, Qualifications, Skills? The instruction says use headings for those categories if content exists. We have "Required qualifications, capabilities, and skills::" then list of items. Also "Preferred Qualifications". So we can have sections: Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (maybe skills). But we need to avoid thin sections. Let's see content: Required qualifications, capabilities, and skills:: - Demonstrated hands-on experience using AI productivity tools (e.g., GitHub Copilot, Claude, ChatGPT, or similar) to build documentation, knowledge bases, prototype product concepts, or accelerate product delivery workflows - 7+ years of product management, product ownership, or business analyst experience with a strong analytical background. - Intellectually curious with a demonstrated passion for product craft, actively follows product industry thought leaders, engages with product communities, and stays current on evolving best practices and frameworks - Experience working closely with user experience designers and software engineers in an Agile/Scrum environment - Ability to work in an environment with a high level of ambiguity and adapt accordingly - Execution focused and able to organize, prioritize, and manage multiple streams of work simultaneously - Strong partnership record and ability to build effective business relationships - Strong verbal communication and presentation skills Preferred Qualifications: - Experience with self-directed brokerage, investment account opening, or wealth management digital platforms - Track record of building or implementing AI-augmented workflows, knowledge management systems, rapid prototyping practices, or intelligent documentation practices - Familiarity with prompt engineering, AI-assisted code review, or AI-driven product analytics - Active participation in product management communities, conferences, or publications (e.g., Mind the Product, Lenny's Newsletter, SVPG, Product-Led Alliance); contributions such as blog posts, talks, or mentorship a plus - Project management experience would be a strong plus Also eligibility: authorized to work in US, no sponsorship. About Us: description of Chase, benefits, etc. This could go under About the role? Actually "About Us" is separate but could be considered "About the role"? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (already). Benefits: there is description of benefits in About Us paragraph: "We offer a competitive total rewards package...". That's benefits content. So we can have Benefits section. Pay: not specified explicitly; they mention base salary determined based on role, experience, skill set and location, commission-based pay, discretionary incentive compensation. That's some pay info. It's not specific numbers but it's substantive. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state compensation info: "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...". That's pay info. So we can include Pay section with that paragraph. Schedule: not mentioned. So omit Schedule. Qualifications vs Skills: We have required qualifications and preferred qualifications. Could map required to Requirements, preferred to Qualifications? Or we could have Requirements (required), Qualifications (preferred), Skills (maybe the skill list). But we have skill list within required. Might be better to have Requirements (required qualifications), Qualifications (preferred qualifications), Skills (maybe the skill-based items like strong verbal communication, etc). However to avoid thin sections, we could combine required and preferred into Requirements and Qualifications sections. Let's see if we have enough content for each. Requirements (required qualifications): list of 8 bullet points. Qualifications (preferred qualifications): list of 5 bullet points. Skills: maybe we could extract skills like "Strong verbal communication and presentation skills", "Ability to work in ambiguity", etc. But those are already in required. Could make Skills section with those soft skills. But risk of thin. Better to have Requirements (required), Qualifications (preferred), and maybe Skills omitted or merged. The instruction: Prefer a few substantive sections over many thin ones. So we could have Requirements (combining required and preferred?) but they'd be separate headings. Could we have Requirements (required) and Qualifications (preferred) both substantive. That's two sections. Skills maybe not needed. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any other: maybe "About the team" but not needed. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes eligibility statement about work authorization, which is not boilerplate? It's a requirement but not a heading. We can include that as a short

  maybe under Requirements or separate? It's about eligibility to work in US, no sponsorship. That's a requirement. Could include under Requirements as a bullet. Also "About Us" includes mission statement etc. That's not boilerplate; it's substantive about company. Could be part of About the role? But we already have About the role describing role. Could add a separate section "About the company"? Not in allowed headings. Allowed headings list includes About the role only. So we should incorporate that info into About the role or maybe Benefits? The About Us paragraph includes mission and benefits. Benefits we already have separate. The mission statement maybe could be part of About the role? Might be okay to include in About the role as extra context. But we must not invent headings. So we can put the About Us description into About the role section after role description, or we could create a separate

  under About the role. Thus About the role section will contain: role description paragraph + maybe the About Us mission paragraph (Chase is a leading financial services firm...). That seems okay. Now Benefits section: we have benefits list: 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. Also "competitive total rewards package including base salary...". That's pay. So Benefits section will list those benefits. Pay section: base salary determined based on role, experience, skill set and location; commission-based pay and/or discretionary incentive compensation, paid in cash and/or forfeitable equity. Now we need to ensure we don't include filler like "commensurate with experience", "not specified", etc. We have specifics. Now produce HTML fragment:

  About the role

  ...

  etc. Make sure to not include any extra text outside HTML. Let's craft content. About the role paragraph: combine role description and About Us mission. Role description: "As a Vice President – Product Owner on the JPM Wealth Management Self Directed Invest Account Opening team, you will play a critical role in defining the vision, strategy, and execution of the next generation of digital account opening experiences across the Wealth Management business lines. You will be an AI-forward leader who actively leverages tools such as GitHub Copilot, Claude, and other AI-powered platforms to accelerate product delivery, build scalable knowledge repositories, rapidly prototype solutions, and drive modern ways of working across the team. You are a product thought leader, deeply curious, actively engaged in industry-wide product management best practices, and continuously learning from leading product influencers and communities to bring fresh perspectives to the team. The role will partner with other product teams, designers, and technology teams across JPM WM and the broader JPMorgan Chase organization to deliver an intuitive, controlled, and seamless self-directed account opening experience for all JPM WM clients and advisors. You are comfortable working on large-scale initiatives, connecting dots across product lines, and conducting deep analysis to recommend solutions supported by data." About Us mission: "Chase is a leading financial services firm, helping nearly half of America's households and small businesses achieve their financial goals through a broad range of financial products. Our mission is to create engaged, lifelong relationships and put our customers at the heart of everything we do. We also help small businesses, nonprofits and cities grow, delivering solutions to solve all their financial needs." We can combine. Now Responsibilities: list each bullet from responsibilities section. Let's extract responsibilities bullets: - Champion the use of AI tools (e.g., GitHub, Copilot, Claude, ChatGPT) to accelerate product workflows — from drafting PRDs, user stories, and acceptance criteria to rapidly prototyping product concepts, interactive wireframes, and proof-of-concept demos — and foster a culture of AI adoption that team members can replicate - Serve as the Product Owner for the Self Directed Invest Account Opening experience; own the product backlog and drive delivery across business and technology partners to build and enhance account opening capabilities - Build and maintain AI-powered knowledge repositories that capture tribal knowledge, product decisions, requirements history, and platform documentation — ensuring the team operates with a single source of truth - Conduct requirement sessions with appropriate teams to understand the context of critical stakeholder needs, pain points, and business impact related to self-directed account opening flows - Manage a technology team and related scrum ceremonies – meet JPM standards for backlog health and epic delivery, including release coordination and planning - Engage with Tech Architects to determine architectural impact to the Account Opening platform and the right strategic approach to execute changes - Drive prioritization through Agile planning methods, using data and AI-driven insights to inform backlog sequencing and sprint planning decisions - Develop expert-level knowledge of the current state account opening platform and help with solutioning the target state - Provide key input in build-out of multi-year product roadmap and translate product strategy into actionable deliverables - Proactively analyze data and leverage data-driven experimentation and measurement frameworks to ensure that key results are on-track Now Requirements (required qualifications) bullets: - Demonstrated hands-on experience using AI productivity tools (e.g., GitHub Copilot, Claude, ChatGPT, or similar) to build documentation, knowledge bases, prototype product concepts, or accelerate product delivery workflows - 7+ years of product management, product ownership, or business analyst experience with a strong analytical background. - Intellectually curious with a demonstrated passion for product craft, actively follows product industry thought leaders, engages with product communities, and stays current on evolving best practices and frameworks - Experience working closely with user experience designers and software engineers in an Agile/Scrum environment - Ability to work in an environment with a high level of ambiguity and adapt accordingly - Execution focused and able to organize, prioritize, and manage multiple streams of work simultaneously - Strong partnership record and ability to build effective business relationships - Strong verbal communication and presentation skills - Must be authorized to work in the United States; no employment-based immigration sponsorship offered for this position. We could add the eligibility as a bullet. Now Qualifications (preferred qualifications) bullets: - Experience with self-directed brokerage, investment account opening, or wealth management digital platforms - Track record of building or implementing AI-augmented workflows, knowledge management systems, rapid prototyping practices, or intelligent documentation practices - Familiarity with prompt engineering, AI-assisted code review, or AI-driven product analytics - Active participation in product management communities, conferences, or publications (e.g., Mind the Product, Lenny's Newsletter, SVPG, Product-Led Alliance); contributions such as blog posts, talks, or mentorship a plus - Project management experience would be a strong plus Now Benefits: list: