Jobs · Marketing · New York

Payments-Digital & Design-Product Manager-Vice President

JPMorganChase · New York, NY · Today
On-siteMarketingFull-time
We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove duplicated lines. We need to preserve all substantive information. Let's parse the job description. First paragraph: "Job Description You enjoy shaping the future of product innovation as a core leader, driving value for customers, guiding successful launches, and exceeding expectations. Join our dynamic team and make a meaningful impact by delivering high-quality products that resonate with clients. As a Product Manager in Integrated Digital Solutions, 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." That's about the role. Could be "About the role". We'll put that as

About the role

with

containing that paragraph. Next: "Job Responsibilities" then a list of responsibilities separated by no bullet but sentences. We need to extract each duty as list items. Let's list them: - 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 - Collaborate with partners and/or third party vendors to drive the development and delivery of integrated banking solutions within enterprise applications, partnering closely with product managers, engineers, and external stakeholders to translate complex business needs into clear functional requirements and execution milestones - Integrate data analytics, user experience research, competitor/market analysis, client feedback, internal stakeholder feedback, and business goals to drive prioritization of potential partnerships - Establish the approach and manage the rollout of new solutions, including objective/scope, target population selection, end-to-end user acceptance testing, readiness, governance, communication, training/support, policies and procedures, and the feedback/metrics needed to move pilots into general availability - Collaborates with controls, sourcing, compliance, legal, risk, and third-party oversight to ensure third-party vendors/partners and solutions go through third-party oversight and product review processes - Develops and maintains deep relationships with delivery partners across the business including Sales, COS, Marketing and Controls, to collaborate on deliverables needed to-go-to market strategy - 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 - Assist in the product development lifecycle by documenting requirements, ensuring sprint inputs (e.g. design and requirements) and outputs (e.g. tested code) are as envisioned, and providing direction and feedback to the partner and/or third-party vendor doing the development work - Participate in user research to uncover client needs and use the personas to identify new integration/partnership ideas and use cases to inform partnership strategy We need to put these under

Responsibilities

with
  • each. Next: "Required Qualifications, Capabilities, And Skills" then list: - 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 - Exceptional interpersonal skills-ability to cultivate and build strong relationships with colleagues at all levels - Demonstrated ability to effectively collaborate with cross-functional teams internally and externally to achieve specific business results - Effective communication skills and ability to translate and synopsize data for decision-making - Strong analytics and problem-solving skills with the ability to adapt to evolving priorities within the product organization - Strong skills in project management, organization, problem-solving and time management These are required qualifications. Could be under

    Requirements

    or

    Qualifications

    . The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have responsibilities, required qualifications (maybe Requirements), preferred qualifications (maybe Skills). Also we have "Preferred Qualifications, Capabilities, And Skills" list: - Demonstrated prior experience working in a highly matrixed, complex organization - Knowledge of how the following platforms work is required, and experience with onboarding clients to them: J.P. Morgan Access, J.P. Morgan's file transmissions, J.P. Morgan's mixed payments file processing (H2H Payments/Paysource), J.P. Morgan's Treasury Services APIs, J.P. Morgan's integrated Solution Plugins - Proficiency with Microsoft Office skills including Excel and PowerPoint - Familiarity with Artificial intelligence tools and agentic solutions a plus - Experience with Jira, Confluence, and SharePoint a plus These could be under Skills or Qualifications. Since we have both Required Qualifications and Preferred Qualifications, we could split: Requirements for required, Skills for preferred (or Qualifications for required, Skills for preferred). The instruction says we can include sections only when posting has real specific content. We have both. We also have "About Us" and "About The Team" sections. Those could be under "About the role"? Actually "About Us" is company description; "About The Team" is team description. Could be part of About the role? But we already have About the role covering role description. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. However we could include "About Us" as part of About the role? Might be better to include a separate "About the company" but not in list. Probably we should incorporate substantive info about company and team into About the role paragraph or maybe a separate

    after About the role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." It doesn't forbid other headings besides the listed ones, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we can include only those headings that have content. We have About the role, Responsibilities, Requirements (required qualifications), Skills (preferred qualifications). Benefits, Pay, Schedule: we need to check if posting states them. In the "About Us" paragraph: "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, awarded in recognition of individual achievements and contributions. 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. Additional details about total compensation and benefits will be provided during the hiring process." Thus we have some info about Pay and Benefits. It mentions base salary determined based on role, experience, skill set and location; commission-based pay etc. That's specific enough to include Pay and Benefits sections. Schedule not mentioned. So we should include Pay and Benefits sections with the specific content. We should not include vague placeholder like "commensurate with experience". But here we have specifics: base salary determined based on role, experience, skill set and location; commission-based pay and/or discretionary incentive compensation; benefits list. That's substantive. Thus we will include:

    About the role

    ...

    Responsibilities

      ...

    Requirements

      ...
    (for required qualifications)

    Skills

      ...
    (for preferred qualifications)

    Benefits

      ...
    (list benefits)

    Pay

    ...

    (describe base salary and commission etc.) We should not include Schedule. We must remove boilerplate: EEO, equal opportunity, scam-warning, navigation, cookie, legal, application instructions, duplicated lines. Also remove "About Us" and "About The Team" sections? We have incorporated some of that info into Benefits and Pay maybe. But we also have company description and team description. Should we include them? They are substantive but not covered by headings. Could we add a

    after About the role that includes company and team description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the company description and team description somewhere. We could add a

    under About the role that includes that info, or we could create a separate heading like "About the company" but not in the list. However the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could embed that info in a

    after About the role without a heading. That would preserve it. Thus About the role

    will contain the initial role description plus maybe the company and team description. But that may be too long; still okay. Let's extract company description: "JPMorganChase, one of the oldest financial institutions, offers innovative financial solutions to millions of consumers, small businesses and many of the world's most prominent corporate, institutional and government clients under the J.P. Morgan and Chase brands. Our history spans over 200 years and today we are a leader in investment banking, consumer and small business banking, commercial banking, financial transaction processing and asset management." Team description: "J.P. Morgan's Commercial & Investment Bank is a global leader across banking, markets, securities services and payments. Corporations, governments and institutions throughout the world entrust us with their business in more than 100 countries. The Commercial & Investment Bank provides strategic advice, raises capital, manages risk and extends liquidity in markets around the world." We'll combine them after the role description. Now 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. We'll put each as

  • . Pay: "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, awarded in recognition of individual achievements and contributions." We'll put that as

    . Now ensure we didn't include any boilerplate like "Additional details about total compensation and benefits will be provided during the hiring process." That's somewhat generic but still substantive? It's a statement that details will be provided later. Might be considered filler but it's still info. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting

Similar jobs