Risk Decisions - UAT & Quality Transformation VP

We need to output HTML fragment with sections: About the role? Actually we have job description content. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, no boilerplate. We need to parse the job description. Key parts: - Intro paragraph: "Join JPMorganChase Risk Management and Compliance at the center of strengthening a firm that serves millions of customers and communities. Lead quality outcomes for decisioning platforms that power critical moments across the Risk lifecycle—from Offer Generation and Acquisitions through Account Management. You'll modernize testing with automation and GenAI-enabled practices while operating in a well-controlled, audit-ready environment. This is a high-impact leadership role with visibility across Product, Technology, Risk, Data, Controls, and Operations. As a/an UAT & Quality Transformation Manager (Vice President) in CCB Risk Decisions Product, you lead the end-to-end testing and quality function across a complex portfolio of batch and real-time decisioning platforms supporting the Risk lifecycle. You are accountable for delivery excellence, release confidence, testing governance, and the evolution from manual UAT to scalable, automated, pipeline-integrated quality engineering. You will lead and develop a high-performing, geographically distributed team and partner closely across interconnected Area Products—Offer Enablement & Commerce, New Account Originations, and Account Management—to establish modern testing frameworks, improve operational efficiency, and enable faster, safer delivery with strong risk and control discipline." That's about the role. So we can have

About the role

with

containing that paragraph(s). Possibly split into multiple paragraphs but okay. - Job Responsibilities: list bullet points after "Job Responsibilities". We need to capture each bullet. List: Own the testing and quality strategy across batch and real-time decisioning platforms, improving coverage, stability, release confidence, and delivery speed Lead the testing operating model, including standards, governance, quality gates, escalation paths, RACI/accountability, and audit-ready documentation Modernize UAT and QA practices by implementing automation-first and continuous testing approaches integrated into CI/CD pipelines Build scalable automation across service/API and end-to-end business process layers, ensuring maintainability, reliability, and measurable business value Drive responsible adoption of GenAI-enabled testing practices (e.g., scenario design, test generation, failure/defect analysis, evidence creation) with required human review and data governance controls Establish comprehensive test strategies, plans, entry/exit criteria, defect management workflows, and release readiness standards across products and programs Execute end-to-end test planning, coordination, reporting, and risk-based quality assessments across initiatives with complex dependencies and aggressive timelines Partner with Product, Technology, Risk, Data, Controls, Audit, and Operations to align on priorities, manage delivery risk, and resolve ambiguity and conflicts Measure quality outcomes through actionable metrics and dashboards (e.g., defect trends, escape rates, automation coverage, cycle time, stability, control evidence completeness) and continuously improve outcomes Lead large-scale, technology-intensive problem solving across architecture, integrations, tooling, environments, and test data constraints Coach and develop talent through performance management, workforce planning, succession planning, and an inclusive culture of accountability and continuous improvement We'll put these in

• . - Required Qualifications, Capabilities, And Skills: list bullet points. List: Bachelor's degree or equivalent experience Minimum 5+ years of progressive experience in QA/UAT, testing leadership, quality engineering, and/or program delivery in a technology or business environment 5+ years leading teams and/or testing functions, including coaching, performance management, and workforce planning across multiple locations Proven ability to define and run testing governance, including standards, quality gates, metrics, reporting, and executive-level escalations Demonstrated experience modernizing testing from manual UAT to automation and continuous testing with measurable improvements (cycle time, efficiency, reliability, defect leakage) Strong hands-on and leadership experience with test automation across API/service and end-to-end workflows; ability to set patterns for maintainability and stability Experience delivering testing for complex, integrated platforms with multiple dependencies, environments, and data sources (internal, third-party, customer information, predictive models) Working knowledge of Agile/product delivery practices and aligning quality controls to support frequent, predictable releases (including True Continuous Delivery where feasible) Strong risk-based testing mindset and ability to operate in a controlled environment with regulatory/control/audit requirements Advanced stakeholder management and executive communication skills; ability to translate technical quality topics into business impact and decisions Proficiency with Jira and common delivery/reporting/documentation tools (PowerPoint, Excel, Visio or similar) We'll put under

  Requirements

  or maybe

  Qualifications

  . The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map Required Qualifications to Requirements (or Qualifications). Probably Requirements is appropriate. Then Preferred Qualifications could go under Qualifications or Skills? There's also Skills heading. We could put Preferred Qualifications under Qualifications as well, but we need to avoid duplication. Perhaps we combine Required and Preferred under Qualifications? But we need to preserve all info. Could have two sections: Requirements (for required) and Qualifications (for preferred). Or we could treat Required as Requirements and Preferred as Qualifications. That seems logical. - Preferred Qualifications, Capabilities, And Skills: list bullet points. List: Experience in Consumer Banking, Credit Card, Lending, and/or Risk Management decisioning and lifecycle processes (acquisitions through account management) Experience implementing GenAI-enabled testing capabilities with strong governance, controls, and evidence standards in a regulated environment Background in real-time decisioning and batch decisioning platforms, including high-availability or near-real-time integrations Familiarity with model-informed decisioning and testing considerations involving predictive models and third-party data sources Demonstrated success building enterprise-scale testing frameworks (shared tooling, reusable components, standards across multiple products) Experience partnering with Controls, Audit, and Operational Risk teams to define quality gates and produce audit-ready test artifacts Strong track record leading cross-functional transformation programs across Product, Engineering, Data, and Operations teams We'll put under

  Qualifications

  . - Skills: maybe we could extract skills from both required and preferred? But we already used those headings. The instruction says we can use Skills heading if there is real specific content. We could list skills like "Test automation, GenAI-enabled testing, Agile, Jira, stakeholder management, risk-based testing". But we must not invent or summarize away detail. Better to not create a Skills section if we don't have explicit skills list separate. The posting includes skills within qualifications. So we might skip Skills section. - Benefits, Pay, Schedule: The posting mentions "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." Also "Additional details about total compensation and benefits will be provided during the hiring process." Thus we have some benefits info. We should include a Benefits section with that info. Pay: they mention base salary determined based on role, experience, skill set and location; possible commission-based pay and/or discretionary incentive compensation. That's pay info. So we can include Pay section. Schedule: not mentioned. So we skip Schedule. We must not include boilerplate like EEO, equal opportunity, etc. Also remove "About Us", "About The Team" maybe? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About US" and "About The Team" sections are not boilerplate? They are descriptive about the company and team. Might be considered substantive? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About US" and "About The Team" are substantive about the company. However the headings we can use are limited to the set. We could incorporate that info into About the role? Or maybe we could add a section "About the company" but not allowed headings. So we might need to include that info within About the role paragraph or maybe as a separate

  after About the role but before Responsibilities. Since we cannot add arbitrary headings, we can just include it as part of the About the role description (maybe as additional paragraph). The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It doesn't forbid other headings, but likely they want only those. Safer to stick to those headings and put any extra info under About the role. Thus we will create About the role paragraph that includes the intro plus the "About US" and "About The Team" content. Let's extract About US: "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." About The Team: "Our Consumer & Community Banking division serves our Chase customers through a range of financial services, including personal banking, credit cards, mortgages, auto financing, investment advice, small business loans and payment processing. We're proud to lead the U.S. in credit card sales and deposit growth and have the most-used digital solutions – all while ranking first in customer satisfaction. Risk Management helps the firm understand, manage and anticipate risks in a constantly changing environment. The work covers areas such as evaluating country-specific risk, understanding regulatory changes and determining credit worthiness. Risk Management provides independent oversight and maintains an effective control environment." We'll combine. Now Benefits: list benefits. Pay: base salary determined based on role, experience, skill set and location; eligible roles may receive commission-based pay and/or discretionary incentive compensation, paid in the form of cash and/or forfeitable equity. We'll put that in Pay section. Now ensure we don't include any boilerplate like "We are an equal opportunity employer..." etc. Remove. Now produce HTML fragment. Structure:

  About the role

  ... combined intro + About US + About The Team ...

  Responsibilities

  • ... each bullet ...

  Requirements

  • ... required qualifications bullets ...

  Qualifications

  • ... preferred qualifications bullets ...

  Benefits

  • ... benefits bullets ...

  Pay

  ... pay description ...

  We should not include Schedule. Check that we didn't miss any substantive info: The mention of "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." We'll put as list. Also "Additional details about total compensation and benefits will be provided during the hiring process." Could be included in Benefits or Pay as a sentence. We'll include that as part of Benefits paragraph maybe. Now ensure we don't repeat job title as heading. We didn't. Now produce final HTML. Be careful to escape any HTML special characters? Not needed. Let's craft.