Vice President, Risk Analytics
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Job Description (intro), Job Summary, Job Responsibilities, Required Qualifications, Capabilities, And Skills, Preferred Qualifications, Capabilities, And Skills, About Us, About The Team. Also mentions total rewards package, benefits, etc. There's no explicit Pay or Schedule details. So we should not create Pay or Schedule sections. Benefits: there is mention of benefits in About Us: "We offer a competitive total rewards package ... 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." That's specific enough to create a Benefits section.
We also have "About Us" and "About The Team" maybe could be combined into "About the role"? Actually "About the role" is a generic heading for role description. The posting includes Job Description and Job Summary which describe role. We could put that under About the role
with paragraphs.
Responsibilities: we have Job Responsibilities bullet list.
Requirements: we have Required Qualifications, Capabilities, And Skills (these are required). Could be under Requirements
or Qualifications
. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. We have both Required and Preferred qualifications. Could combine into Qualifications section (maybe separate Required and Preferred). But we should not create thin sections. Could have a single Qualifications section with required and preferred subpoints? But we need to use - for any list of duties/requirements/benefits. So we can list required qualifications as list items, and preferred qualifications as list items maybe under same section or separate? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we have sections: About the role, Responsibilities, Qualifications, Benefits. Within Qualifications we can have two sublists? But we cannot have headings inside? We could just list all qualifications (required and preferred) as list items, maybe marking preferred with "(Preferred)"? But we must preserve all substantive information; we cannot lose distinction between required and preferred. Could create two subsections using
? Not allowed? Only headings specified are for section headings. We could still use but not specified; better to avoid extra headings. Could embed both required and preferred in same list but differentiate via text. That preserves info.
Alternatively we could have separate sections: Requirements (for required) and Skills (for preferred). But the instruction lists Skills as a possible heading. Could treat Required Qualifications as Requirements, and Preferred Qualifications as Skills. That seems reasonable.
Thus sections: About the role (intro + job summary), Responsibilities, Requirements (required qualifications), Skills (preferred qualifications), Benefits.
We must not repeat job title as heading. No Job ID etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
About the role: combine Job Description paragraph and Job Summary paragraph(s). The Job Description: "Join a team where advanced analytics, strong data foundations, and practical decisioning come together to improve outcomes for customers and the firm. You will lead high-impact data science initiatives that strengthen credit and fraud risk performance through better data, better models, and better insights. This role offers the opportunity to set a multi-year vision, build new capabilities, and scale analytics products that directly influence senior decision-making. You will partner closely with leaders and stakeholders to turn ambiguous questions into measurable business outcomes."
Job Summary: "As a Vice President, Risk Analytics in the Consumer Risk Insights team, you will lead a team of data scientists and analytics professionals to build and scale customer data assets and models that improve credit and fraud risk outcomes. You will work with partners across risk, product, technology, and operations to identify the most important problems, define success metrics, and translate opportunities into measurable analytical solutions. You will raise standards for quality and explainability so decision-makers can act with confidence. You will communicate clearly with both technical teams and senior leaders, using crisp storytelling to explain tradeoffs, recommendations, and expected impact. You will also identify where generative artificial intelligence can be used responsibly to accelerate the analytics lifecycle and improve productivity."
We can combine into one or two
elements.
Responsibilities: list bullet points from Job Responsibilities. Each bullet is a sentence starting with a verb. We'll put each as
- .
Required Qualifications: list from Required Qualifications, Capabilities, And Skills. Items:
- Master's degree in a quantitative field (for example, computer science, statistics, mathematics, physics, or related discipline)
- Proven experience leading and developing data science teams, including coaching, performance management, and team culture
- Demonstrated ability to deliver production-grade, data-driven solutions to complex business problems
- Strong expertise in consumer financial services and applying analytics to risk decisioning, including credit and fraud
- Deep knowledge of statistical modeling and data mining methods across structured and unstructured data
- Strong programming capability in Python and SQL (and/or comparable analytics languages) and experience working with large-scale data
- Ability to frame ambiguous problems, define clear success metrics, and prioritize high-impact work
- Strong stakeholder management skills and ability to influence senior leaders through sound judgment and crisp storytelling
- Excellent written and verbal communication skills for technical and non-technical audiences
Preferred Qualifications: list from Preferred Qualifications, Capabilities, And Skills:
- Doctoral degree in a quantitative field
- Experience building and scaling analytics “data products” used by multiple teams or functions
- Hands-on experience applying generative artificial intelligence techniques to analytics workflows (for example, enrichment, classification, or unstructured text processing)
- Experience improving transaction data quality, categorization, and explainability for downstream analytics or decisioning
- Experience partnering with model risk management, governance, and control functions to support responsible deployment
- Track record of delivering executive-level narratives and decision materials tied to measurable outcomes
Benefits: from About Us: "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."
We should not include Pay section because we don't have specific numbers. Benefits section can include the above.
We should exclude boilerplate like About Us mission statement? The About Us includes mission and other generic statements; we can keep the substantive benefits part. The mission statement maybe not needed but it's substantive? It's about the firm; could be considered part of About the role? But we already have About the role covering role description. The About Us includes mission and description of Chase; could be considered extra but not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the About Us description? It's substantive about the firm. However we already have About the role; maybe we can include an "About the company" section? Not in allowed headings list. But we could incorporate into About the role? Might be okay to add a brief paragraph about Chase under About the role? But the instruction says use headings like About the role, Responsibilities, etc. It didn't forbid other headings 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 stick to those headings. The About Us description could be placed under About the role as extra paragraph? Might be okay.
But we already used About the role for role description; we could add another paragraph about the firm. That would still be under same heading.
Thus About the role section will have multiple
paragraphs: first the job description/intro, second the job summary, third maybe the About Us description (mission etc). However the About Us includes also "We are an equal opportunity employer..." which is boilerplate EEO; we should remove that. Also remove "Visit our FAQs..." etc. Also remove "We also make reasonable accommodations..." etc. Also remove "Equal Opportunity Employer/Disability/Veterans". Also remove "About The Team" maybe could be included as part of About the role? It describes the team; could be relevant. We could include that as another paragraph.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, navigation, legal, cookie, etc. Also remove "About Us" heading itself (we are not outputting headings for that). We'll just embed the substantive content.
Let's extract substantive content from 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."
That's substantive.
Then the benefits paragraph we already captured.
We should also maybe include "We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success." That's also substantive but somewhat generic; still could keep.
But we must avoid EEO statements. So we can keep the diversity statement? It's not EEO boilerplate but a positive statement about diversity. Might be okay.
We'll keep: "We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success."
We'll omit the EEO legal stuff.
Now 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. The CCB Data & Analytics team responsibly leverages data across Chase to build competitive advantages for the businesses while providing value and protection for customers. The team encompasses a variety of disciplines from data governance and strategy to reporting, data science and machine learning. We have a strong partnership with Technology, which provides cutting edge data and analytics infrastructure. The team powers Chase with insights to create the best customer and business outcomes."
That's substantive about the team; we could include under About the role as extra paragraph.
Thus About the role will have several paragraphs.
Now we need to ensure we don't include any filler like "commensurate with experience" etc. Not present.
Now produce HTML:
About the role
Join a team where advanced analytics, strong data foundations, and practical decisioning come together to improve outcomes for customers and the firm. You will lead high-impact data science initiatives that strengthen credit and fraud risk performance through better data, better models, and better insights. This role offers the opportunity to set a multi-year vision, build new capabilities, and scale analytics products that directly influence senior decision-making. You will partner closely with leaders and stakeholders to turn ambiguous questions into measurable business outcomes.
As a Vice President, Risk Analytics in the Consumer Risk Insights team, you will lead a team of data scientists and analytics professionals to build and scale customer data assets and models that improve credit and fraud risk outcomes. You will work with partners across risk, product, technology, and operations to identify the most important problems, define success metrics, and translate opportunities
? Not allowed? Only headings specified are for section headings. We could still use but not specified; better to avoid extra headings. Could embed both required and preferred in same list but differentiate via text. That preserves info.
Alternatively we could have separate sections: Requirements (for required) and Skills (for preferred). But the instruction lists Skills as a possible heading. Could treat Required Qualifications as Requirements, and Preferred Qualifications as Skills. That seems reasonable.
Thus sections: About the role (intro + job summary), Responsibilities, Requirements (required qualifications), Skills (preferred qualifications), Benefits.
We must not repeat job title as heading. No Job ID etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
About the role: combine Job Description paragraph and Job Summary paragraph(s). The Job Description: "Join a team where advanced analytics, strong data foundations, and practical decisioning come together to improve outcomes for customers and the firm. You will lead high-impact data science initiatives that strengthen credit and fraud risk performance through better data, better models, and better insights. This role offers the opportunity to set a multi-year vision, build new capabilities, and scale analytics products that directly influence senior decision-making. You will partner closely with leaders and stakeholders to turn ambiguous questions into measurable business outcomes."
Job Summary: "As a Vice President, Risk Analytics in the Consumer Risk Insights team, you will lead a team of data scientists and analytics professionals to build and scale customer data assets and models that improve credit and fraud risk outcomes. You will work with partners across risk, product, technology, and operations to identify the most important problems, define success metrics, and translate opportunities into measurable analytical solutions. You will raise standards for quality and explainability so decision-makers can act with confidence. You will communicate clearly with both technical teams and senior leaders, using crisp storytelling to explain tradeoffs, recommendations, and expected impact. You will also identify where generative artificial intelligence can be used responsibly to accelerate the analytics lifecycle and improve productivity."
We can combine into one or two
but not specified; better to avoid extra headings. Could embed both required and preferred in same list but differentiate via text. That preserves info. Alternatively we could have separate sections: Requirements (for required) and Skills (for preferred). But the instruction lists Skills as a possible heading. Could treat Required Qualifications as Requirements, and Preferred Qualifications as Skills. That seems reasonable. Thus sections: About the role (intro + job summary), Responsibilities, Requirements (required qualifications), Skills (preferred qualifications), Benefits. We must not repeat job title as heading. No Job ID etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft. About the role: combine Job Description paragraph and Job Summary paragraph(s). The Job Description: "Join a team where advanced analytics, strong data foundations, and practical decisioning come together to improve outcomes for customers and the firm. You will lead high-impact data science initiatives that strengthen credit and fraud risk performance through better data, better models, and better insights. This role offers the opportunity to set a multi-year vision, build new capabilities, and scale analytics products that directly influence senior decision-making. You will partner closely with leaders and stakeholders to turn ambiguous questions into measurable business outcomes." Job Summary: "As a Vice President, Risk Analytics in the Consumer Risk Insights team, you will lead a team of data scientists and analytics professionals to build and scale customer data assets and models that improve credit and fraud risk outcomes. You will work with partners across risk, product, technology, and operations to identify the most important problems, define success metrics, and translate opportunities into measurable analytical solutions. You will raise standards for quality and explainability so decision-makers can act with confidence. You will communicate clearly with both technical teams and senior leaders, using crisp storytelling to explain tradeoffs, recommendations, and expected impact. You will also identify where generative artificial intelligence can be used responsibly to accelerate the analytics lifecycle and improve productivity." We can combine into one or two
elements. Responsibilities: list bullet points from Job Responsibilities. Each bullet is a sentence starting with a verb. We'll put each as
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 stick to those headings. The About Us description could be placed under About the role as extra paragraph? Might be okay. But we already used About the role for role description; we could add another paragraph about the firm. That would still be under same heading. Thus About the role section will have multiple
paragraphs: first the job description/intro, second the job summary, third maybe the About Us description (mission etc). However the About Us includes also "We are an equal opportunity employer..." which is boilerplate EEO; we should remove that. Also remove "Visit our FAQs..." etc. Also remove "We also make reasonable accommodations..." etc. Also remove "Equal Opportunity Employer/Disability/Veterans". Also remove "About The Team" maybe could be included as part of About the role? It describes the team; could be relevant. We could include that as another paragraph. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, navigation, legal, cookie, etc. Also remove "About Us" heading itself (we are not outputting headings for that). We'll just embed the substantive content. Let's extract substantive content from 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." That's substantive. Then the benefits paragraph we already captured. We should also maybe include "We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success." That's also substantive but somewhat generic; still could keep. But we must avoid EEO statements. So we can keep the diversity statement? It's not EEO boilerplate but a positive statement about diversity. Might be okay. We'll keep: "We recognize that our people are our strength and the diverse talents they bring to our global workforce are directly linked to our success." We'll omit the EEO legal stuff. Now 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. The CCB Data & Analytics team responsibly leverages data across Chase to build competitive advantages for the businesses while providing value and protection for customers. The team encompasses a variety of disciplines from data governance and strategy to reporting, data science and machine learning. We have a strong partnership with Technology, which provides cutting edge data and analytics infrastructure. The team powers Chase with insights to create the best customer and business outcomes." That's substantive about the team; we could include under About the role as extra paragraph. Thus About the role will have several paragraphs. Now we need to ensure we don't include any filler like "commensurate with experience" etc. Not present. Now produce HTML:
About the role
Join a team where advanced analytics, strong data foundations, and practical decisioning come together to improve outcomes for customers and the firm. You will lead high-impact data science initiatives that strengthen credit and fraud risk performance through better data, better models, and better insights. This role offers the opportunity to set a multi-year vision, build new capabilities, and scale analytics products that directly influence senior decision-making. You will partner closely with leaders and stakeholders to turn ambiguous questions into measurable business outcomes.
As a Vice President, Risk Analytics in the Consumer Risk Insights team, you will lead a team of data scientists and analytics professionals to build and scale customer data assets and models that improve credit and fraud risk outcomes. You will work with partners across risk, product, technology, and operations to identify the most important problems, define success metrics, and translate opportunities