Business Transformation, Product Manager-Payments-Vice President
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. No Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove "About Us" maybe? The instruction: "Prefer a few substantive sections over many thin ones." We need to include sections only when posting has real specific content. The posting includes: Job Description (intro paragraph), Job Responsibilities (list), Required Qualifications, Capabilities, And Skills (list), Preferred Qualifications, Capabilities, And Skills (list), About Us (some prose), About The Team (some prose). Also maybe "Benefits" content: The About Us includes benefits description: "We offer a competitive total rewards package...". That's benefits info. Also "Pay" maybe: "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..." That's pay info. Schedule not mentioned. So we can include sections: About the role (maybe the intro paragraph), Responsibilities, Requirements (maybe combine Required Qualifications), Qualifications (maybe Preferred?), Skills (maybe combine?), Benefits, Pay. But we must not create sections with filler like "commensurate with experience". The posting does have specific benefits and pay info, so we can include those sections.
We need to decide headings: According to rules, use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content exists.
We need to avoid repeating job title as heading. So we will not have a heading for the job title.
We need to output only HTML fragment, no /, no markdown.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include the content from the posting, but we can format as lists or paragraphs.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "About Us" maybe? But we can keep as prose under About the role? Actually "About Us" is separate; but we could incorporate into About the role? The instruction says use headings like About the role, Responsibilities, etc. So we can have About the role section containing the introductory paragraph (the first paragraph about shaping future, etc.) plus maybe About Us and About The Team? But those are separate sections; we could treat them as part of About the role or maybe we could have separate sections like About the company and About the team, but not in the allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. So we need to map content accordingly.
Thus:
- About the role: include the introductory paragraph(s) that describe the role: "You enjoy shaping the future..." plus maybe the description of being integral part of team, etc. Also maybe include "As a Product Manager in Business Transformation team in Merchant Services, you are an integral part..." That's role description. Also maybe include "About The Team" content? That could be considered part of About the role? But it's about the team, not the role. However we don't have a heading for About the team. Could we include it under About the role as extra prose? Might be okay but risk of adding unrelated content. However we need to preserve ALL substantive information; we cannot drop the About The Team info. So we need to include it somewhere. Since there's no specific heading for About the team, we could incorporate it into About the role section as additional prose, or we could create a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections for those headings if we have content. If we have content that doesn't fit those headings, maybe we should not create a heading for it; we could embed it under an existing heading if appropriate. The About The Team info is about the team, not the role, but we could still put it under About the role as it's still descriptive of the context. Might be acceptable.
Alternatively, we could create a section "About the company" but not in the list; risk of violating instruction. Better to stick to given headings.
Thus we will have sections:
- About the role: combine the introductory paragraph(s) and About The Team description.
- Responsibilities: list of responsibilities (the bullet points after "Job Responsibilities").
- Requirements: maybe combine Required Qualifications, Capabilities, And Skills (the list after that heading). Could also include "Required Qualifications, Capabilities, And Skills" as Requirements.
- Qualifications: maybe Preferred Qualifications, Capabilities, And Skills.
- Skills: maybe we could split but we have both Required and Preferred; we could put Required under Requirements, Preferred under Qualifications, and Skills maybe not needed. But we need to avoid thin sections. Could combine Skills into either Requirements or Qualifications. Since we have both Required and Preferred, we could have Requirements (Required) and Qualifications (Preferred). Skills maybe not needed.
- Benefits: from About Us: benefits description.
- Pay: from About Us: base salary, commission, incentive compensation.
- Schedule: not present, so omit.
We must not repeat job title. No Job ID etc.
We need to format lists with - . For prose, use
.
We need to preserve all substantive information: we must not lose any detail from the lists.
Let's extract content.
Intro paragraph(s):
"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 Business Transformation team in Merchant Services, you are an integral part of the team that innovates new product offerings and leads the end-to-end product life cycle. As a change leader you are responsible for translating Merchant Services' business priorities across growth, client experience, operational efficiency, and risk reduction into the organizational and workforce changes that deliver them. You partner with product, technology, operations, risk, and senior leadership to identify the business outcomes that matter, determine where AI and other capabilities create the greatest leverage, and design the operating model and adoption strategy required to realize that value. With a strong commitment to scalability, resiliency, and stability, you collaborate closely with cross-functional teams to ensure changes exceed customer expectations."
That's the intro.
About The Team:
"About The Team A part of the Commercial & Investment Bank, J.P. Morgan Payments enables organizations of all sizes to execute transactions efficiently and securely, transforming the movement of information, money, and assets. The team of experts tackles complex challenges at every stage of the payment lifecycle. And their industry-leading solutions facilitate seamless transactions across borders, industries, and platforms. Operating in over 160 countries and handling more than 120 currencies, J.P. Morgan Payments business is the largest processor of USD payments, with a daily transaction volume of $10 trillion."
We'll include that as prose under About the role.
Now Responsibilities list (the bullet points after "Job Responsibilities"):
We need to capture each bullet. The text:
"Partner with senior leaders to define the business outcomes Merchant Services owns (growth, client experience, efficiency, risk reduction) and translate them into a transformation agenda.
Identify the highest-value opportunities and apply AI, automation, and operating-model change to deliver measurable results; challenge work without a clear business case.
Prioritize and sequence initiatives based on business value and organizational change capacity.
Own end-to-end adoption strategy for new capabilities—from leadership alignment through frontline behavior change and reinforcement.
Diagnose adoption barriers using data-driven methods (e.g., telemetry, surveys, process insights, ONA where applicable) and design targeted interventions.
Define and own outcome-linked success metrics that connect capability deployment, behavior change, and business impact.
Redesign workflows for effective human–AI teaming, including clear handoffs, escalation points, and control points.
Partner with risk, compliance, and controls to embed 3LOD, model risk, and regulatory requirements into new operating models from day one.
Lead org design changes required to sustain the model (roles, skills, spans of control, new/retired roles).
Coach and enable senior sponsors with crisp narratives, communications, and translation of technical performance into adoption and business implications.
Build transformation capability (training, labs, coaching, change champions) and run a managed backlog with retrospectives and portfolio-level change-load oversight."
Note: there is a typo "escalation points" originally "escalation paths". We'll keep as in text.
We need to output each as
- .
Now Required Qualifications, Capabilities, And Skills list:
"7+ years in enterprise product, technology, or transformation roles
5+ years leading large-scale organizational change across 25+ teams in matrixed environments
Demonstrated track record applying structured processes to real, measurable outcomes — not just deliverables
AI product literacy: able to interrogate model performance, evaluation methods, bias, drift, and failure modes; not required to build, but cannot be snowed
Workflow decomposition: able to credibly partition a process into human, AI, and joint steps with defensible reasoning
Org analytics fluency: able to read and challenge process mining outputs, ONA graphs, and adoption telemetry
Risk and controls translation: fluent in how AI changes interact with 3LOD, model risk management, and regulatory obligations in a financial-services context
Senior stakeholder management — including coaching executive sponsors through ambiguity and AI literacy gaps
Sharp written and verbal communication; able to facilitate working sessions of 5–50+ across executive and frontline audiences
Scaled agile delivery experience; comfortable operating inside SAFe, LeSS, or equivalent frameworks"
We'll output as
- .
Now Preferred Qualifications, Capabilities, And Skills list:
"Prosci ADKAR certification or equivalent
Agile coaching credentials (SPC, CSP, ICP-ACC) and/or org design credentials
Experience in payments, merchant acquiring, or other regulated financial services
Working knowledge of AI governance frameworks (NIST AI RMF, EU AI Act, internal model risk standards)
History of building change communities of practice or change champion networks"
Now About Us benefits and pay:
From 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."
We need to separate Benefits and Pay sections.
Pay: "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."
Benefits: "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 child
for prose. Do not repeat job title. No Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. Also remove "About Us" maybe? The instruction: "Prefer a few substantive sections over many thin ones." We need to include sections only when posting has real specific content. The posting includes: Job Description (intro paragraph), Job Responsibilities (list), Required Qualifications, Capabilities, And Skills (list), Preferred Qualifications, Capabilities, And Skills (list), About Us (some prose), About The Team (some prose). Also maybe "Benefits" content: The About Us includes benefits description: "We offer a competitive total rewards package...". That's benefits info. Also "Pay" maybe: "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..." That's pay info. Schedule not mentioned. So we can include sections: About the role (maybe the intro paragraph), Responsibilities, Requirements (maybe combine Required Qualifications), Qualifications (maybe Preferred?), Skills (maybe combine?), Benefits, Pay. But we must not create sections with filler like "commensurate with experience". The posting does have specific benefits and pay info, so we can include those sections. We need to decide headings: According to rules, use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content exists.
We need to avoid repeating job title as heading. So we will not have a heading for the job title.
We need to output only HTML fragment, no /, no markdown.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include the content from the posting, but we can format as lists or paragraphs.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "About Us" maybe? But we can keep as prose under About the role? Actually "About Us" is separate; but we could incorporate into About the role? The instruction says use headings like About the role, Responsibilities, etc. So we can have About the role section containing the introductory paragraph (the first paragraph about shaping future, etc.) plus maybe About Us and About The Team? But those are separate sections; we could treat them as part of About the role or maybe we could have separate sections like About the company and About the team, but not in the allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. So we need to map content accordingly.
Thus:
- About the role: include the introductory paragraph(s) that describe the role: "You enjoy shaping the future..." plus maybe the description of being integral part of team, etc. Also maybe include "As a Product Manager in Business Transformation team in Merchant Services, you are an integral part..." That's role description. Also maybe include "About The Team" content? That could be considered part of About the role? But it's about the team, not the role. However we don't have a heading for About the team. Could we include it under About the role as extra prose? Might be okay but risk of adding unrelated content. However we need to preserve ALL substantive information; we cannot drop the About The Team info. So we need to include it somewhere. Since there's no specific heading for About the team, we could incorporate it into About the role section as additional prose, or we could create a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections for those headings if we have content. If we have content that doesn't fit those headings, maybe we should not create a heading for it; we could embed it under an existing heading if appropriate. The About The Team info is about the team, not the role, but we could still put it under About the role as it's still descriptive of the context. Might be acceptable.
Alternatively, we could create a section "About the company" but not in the list; risk of violating instruction. Better to stick to given headings.
Thus we will have sections:
- About the role: combine the introductory paragraph(s) and About The Team description.
- Responsibilities: list of responsibilities (the bullet points after "Job Responsibilities").
- Requirements: maybe combine Required Qualifications, Capabilities, And Skills (the list after that heading). Could also include "Required Qualifications, Capabilities, And Skills" as Requirements.
- Qualifications: maybe Preferred Qualifications, Capabilities, And Skills.
- Skills: maybe we could split but we have both Required and Preferred; we could put Required under Requirements, Preferred under Qualifications, and Skills maybe not needed. But we need to avoid thin sections. Could combine Skills into either Requirements or Qualifications. Since we have both Required and Preferred, we could have Requirements (Required) and Qualifications (Preferred). Skills maybe not needed.
- Benefits: from About Us: benefits description.
- Pay: from About Us: base salary, commission, incentive compensation.
- Schedule: not present, so omit.
We must not repeat job title. No Job ID etc.
We need to format lists with - . For prose, use
.
We need to preserve all substantive information: we must not lose any detail from the lists.
Let's extract content.
Intro paragraph(s):
"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 Business Transformation team in Merchant Services, you are an integral part of the team that innovates new product offerings and leads the end-to-end product life cycle. As a change leader you are responsible for translating Merchant Services' business priorities across growth, client experience, operational efficiency, and risk reduction into the organizational and workforce changes that deliver them. You partner with product, technology, operations, risk, and senior leadership to identify the business outcomes that matter, determine where AI and other capabilities create the greatest leverage, and design the operating model and adoption strategy required to realize that value. With a strong commitment to scalability, resiliency, and stability, you collaborate closely with cross-functional teams to ensure changes exceed customer expectations."
That's the intro.
About The Team:
"About The Team A part of the Commercial & Investment Bank, J.P. Morgan Payments enables organizations of all sizes to execute transactions efficiently and securely, transforming the movement of information, money, and assets. The team of experts tackles complex challenges at every stage of the payment lifecycle. And their industry-leading solutions facilitate seamless transactions across borders, industries, and platforms. Operating in over 160 countries and handling more than 120 currencies, J.P. Morgan Payments business is the largest processor of USD payments, with a daily transaction volume of $10 trillion."
We'll include that as prose under About the role.
Now Responsibilities list (the bullet points after "Job Responsibilities"):
We need to capture each bullet. The text:
"Partner with senior leaders to define the business outcomes Merchant Services owns (growth, client experience, efficiency, risk reduction) and translate them into a transformation agenda.
Identify the highest-value opportunities and apply AI, automation, and operating-model change to deliver measurable results; challenge work without a clear business case.
Prioritize and sequence initiatives based on business value and organizational change capacity.
Own end-to-end adoption strategy for new capabilities—from leadership alignment through frontline behavior change and reinforcement.
Diagnose adoption barriers using data-driven methods (e.g., telemetry, surveys, process insights, ONA where applicable) and design targeted interventions.
Define and own outcome-linked success metrics that connect capability deployment, behavior change, and business impact.
Redesign workflows for effective human–AI teaming, including clear handoffs, escalation points, and control points.
Partner with risk, compliance, and controls to embed 3LOD, model risk, and regulatory requirements into new operating models from day one.
Lead org design changes required to sustain the model (roles, skills, spans of control, new/retired roles).
Coach and enable senior sponsors with crisp narratives, communications, and translation of technical performance into adoption and business implications.
Build transformation capability (training, labs, coaching, change champions) and run a managed backlog with retrospectives and portfolio-level change-load oversight."
Note: there is a typo "escalation points" originally "escalation paths". We'll keep as in text.
We need to output each as
- .
Now Required Qualifications, Capabilities, And Skills list:
"7+ years in enterprise product, technology, or transformation roles
5+ years leading large-scale organizational change across 25+ teams in matrixed environments
Demonstrated track record applying structured processes to real, measurable outcomes — not just deliverables
AI product literacy: able to interrogate model performance, evaluation methods, bias, drift, and failure modes; not required to build, but cannot be snowed
Workflow decomposition: able to credibly partition a process into human, AI, and joint steps with defensible reasoning
Org analytics fluency: able to read and challenge process mining outputs, ONA graphs, and adoption telemetry
Risk and controls translation: fluent in how AI changes interact with 3LOD, model risk management, and regulatory obligations in a financial-services context
Senior stakeholder management — including coaching executive sponsors through ambiguity and AI literacy gaps
Sharp written and verbal communication; able to facilitate working sessions of 5–50+ across executive and frontline audiences
Scaled agile delivery experience; comfortable operating inside SAFe, LeSS, or equivalent frameworks"
We'll output as
- .
Now Preferred Qualifications, Capabilities, And Skills list:
"Prosci ADKAR certification or equivalent
Agile coaching credentials (SPC, CSP, ICP-ACC) and/or org design credentials
Experience in payments, merchant acquiring, or other regulated financial services
Working knowledge of AI governance frameworks (NIST AI RMF, EU AI Act, internal model risk standards)
History of building change communities of practice or change champion networks"
Now About Us benefits and pay:
From 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."
We need to separate Benefits and Pay sections.
Pay: "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."
Benefits: "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 child
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections for those headings if we have content. If we have content that doesn't fit those headings, maybe we should not create a heading for it; we could embed it under an existing heading if appropriate. The About The Team info is about the team, not the role, but we could still put it under About the role as it's still descriptive of the context. Might be acceptable.
Alternatively, we could create a section "About the company" but not in the list; risk of violating instruction. Better to stick to given headings.
Thus we will have sections:
- About the role: combine the introductory paragraph(s) and About The Team description.
- Responsibilities: list of responsibilities (the bullet points after "Job Responsibilities").
- Requirements: maybe combine Required Qualifications, Capabilities, And Skills (the list after that heading). Could also include "Required Qualifications, Capabilities, And Skills" as Requirements.
- Qualifications: maybe Preferred Qualifications, Capabilities, And Skills.
- Skills: maybe we could split but we have both Required and Preferred; we could put Required under Requirements, Preferred under Qualifications, and Skills maybe not needed. But we need to avoid thin sections. Could combine Skills into either Requirements or Qualifications. Since we have both Required and Preferred, we could have Requirements (Required) and Qualifications (Preferred). Skills maybe not needed.
- Benefits: from About Us: benefits description.
- Pay: from About Us: base salary, commission, incentive compensation.
- Schedule: not present, so omit.
We must not repeat job title. No Job ID etc.
We need to format lists with - . For prose, use
.
We need to preserve all substantive information: we must not lose any detail from the lists.
Let's extract content.
Intro paragraph(s):
"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 Business Transformation team in Merchant Services, you are an integral part of the team that innovates new product offerings and leads the end-to-end product life cycle. As a change leader you are responsible for translating Merchant Services' business priorities across growth, client experience, operational efficiency, and risk reduction into the organizational and workforce changes that deliver them. You partner with product, technology, operations, risk, and senior leadership to identify the business outcomes that matter, determine where AI and other capabilities create the greatest leverage, and design the operating model and adoption strategy required to realize that value. With a strong commitment to scalability, resiliency, and stability, you collaborate closely with cross-functional teams to ensure changes exceed customer expectations."
That's the intro.
About The Team:
"About The Team A part of the Commercial & Investment Bank, J.P. Morgan Payments enables organizations of all sizes to execute transactions efficiently and securely, transforming the movement of information, money, and assets. The team of experts tackles complex challenges at every stage of the payment lifecycle. And their industry-leading solutions facilitate seamless transactions across borders, industries, and platforms. Operating in over 160 countries and handling more than 120 currencies, J.P. Morgan Payments business is the largest processor of USD payments, with a daily transaction volume of $10 trillion."
We'll include that as prose under About the role.
Now Responsibilities list (the bullet points after "Job Responsibilities"):
We need to capture each bullet. The text:
"Partner with senior leaders to define the business outcomes Merchant Services owns (growth, client experience, efficiency, risk reduction) and translate them into a transformation agenda.
Identify the highest-value opportunities and apply AI, automation, and operating-model change to deliver measurable results; challenge work without a clear business case.
Prioritize and sequence initiatives based on business value and organizational change capacity.
Own end-to-end adoption strategy for new capabilities—from leadership alignment through frontline behavior change and reinforcement.
Diagnose adoption barriers using data-driven methods (e.g., telemetry, surveys, process insights, ONA where applicable) and design targeted interventions.
Define and own outcome-linked success metrics that connect capability deployment, behavior change, and business impact.
Redesign workflows for effective human–AI teaming, including clear handoffs, escalation points, and control points.
Partner with risk, compliance, and controls to embed 3LOD, model risk, and regulatory requirements into new operating models from day one.
Lead org design changes required to sustain the model (roles, skills, spans of control, new/retired roles).
Coach and enable senior sponsors with crisp narratives, communications, and translation of technical performance into adoption and business implications.
Build transformation capability (training, labs, coaching, change champions) and run a managed backlog with retrospectives and portfolio-level change-load oversight."
Note: there is a typo "escalation points" originally "escalation paths". We'll keep as in text.
We need to output each as
- .
Now Required Qualifications, Capabilities, And Skills list:
"7+ years in enterprise product, technology, or transformation roles
5+ years leading large-scale organizational change across 25+ teams in matrixed environments
Demonstrated track record applying structured processes to real, measurable outcomes — not just deliverables
AI product literacy: able to interrogate model performance, evaluation methods, bias, drift, and failure modes; not required to build, but cannot be snowed
Workflow decomposition: able to credibly partition a process into human, AI, and joint steps with defensible reasoning
Org analytics fluency: able to read and challenge process mining outputs, ONA graphs, and adoption telemetry
Risk and controls translation: fluent in how AI changes interact with 3LOD, model risk management, and regulatory obligations in a financial-services context
Senior stakeholder management — including coaching executive sponsors through ambiguity and AI literacy gaps
Sharp written and verbal communication; able to facilitate working sessions of 5–50+ across executive and frontline audiences
Scaled agile delivery experience; comfortable operating inside SAFe, LeSS, or equivalent frameworks"
We'll output as
- .
Now Preferred Qualifications, Capabilities, And Skills list:
"Prosci ADKAR certification or equivalent
Agile coaching credentials (SPC, CSP, ICP-ACC) and/or org design credentials
Experience in payments, merchant acquiring, or other regulated financial services
Working knowledge of AI governance frameworks (NIST AI RMF, EU AI Act, internal model risk standards)
History of building change communities of practice or change champion networks"
Now About Us benefits and pay:
From 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."
We need to separate Benefits and Pay sections.
Pay: "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."
Benefits: "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 child
. We need to preserve all substantive information: we must not lose any detail from the lists. Let's extract content. Intro paragraph(s): "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 Business Transformation team in Merchant Services, you are an integral part of the team that innovates new product offerings and leads the end-to-end product life cycle. As a change leader you are responsible for translating Merchant Services' business priorities across growth, client experience, operational efficiency, and risk reduction into the organizational and workforce changes that deliver them. You partner with product, technology, operations, risk, and senior leadership to identify the business outcomes that matter, determine where AI and other capabilities create the greatest leverage, and design the operating model and adoption strategy required to realize that value. With a strong commitment to scalability, resiliency, and stability, you collaborate closely with cross-functional teams to ensure changes exceed customer expectations." That's the intro. About The Team: "About The Team A part of the Commercial & Investment Bank, J.P. Morgan Payments enables organizations of all sizes to execute transactions efficiently and securely, transforming the movement of information, money, and assets. The team of experts tackles complex challenges at every stage of the payment lifecycle. And their industry-leading solutions facilitate seamless transactions across borders, industries, and platforms. Operating in over 160 countries and handling more than 120 currencies, J.P. Morgan Payments business is the largest processor of USD payments, with a daily transaction volume of $10 trillion." We'll include that as prose under About the role. Now Responsibilities list (the bullet points after "Job Responsibilities"): We need to capture each bullet. The text: "Partner with senior leaders to define the business outcomes Merchant Services owns (growth, client experience, efficiency, risk reduction) and translate them into a transformation agenda. Identify the highest-value opportunities and apply AI, automation, and operating-model change to deliver measurable results; challenge work without a clear business case. Prioritize and sequence initiatives based on business value and organizational change capacity. Own end-to-end adoption strategy for new capabilities—from leadership alignment through frontline behavior change and reinforcement. Diagnose adoption barriers using data-driven methods (e.g., telemetry, surveys, process insights, ONA where applicable) and design targeted interventions. Define and own outcome-linked success metrics that connect capability deployment, behavior change, and business impact. Redesign workflows for effective human–AI teaming, including clear handoffs, escalation points, and control points. Partner with risk, compliance, and controls to embed 3LOD, model risk, and regulatory requirements into new operating models from day one. Lead org design changes required to sustain the model (roles, skills, spans of control, new/retired roles). Coach and enable senior sponsors with crisp narratives, communications, and translation of technical performance into adoption and business implications. Build transformation capability (training, labs, coaching, change champions) and run a managed backlog with retrospectives and portfolio-level change-load oversight." Note: there is a typo "escalation points" originally "escalation paths". We'll keep as in text. We need to output each as
- . Now Preferred Qualifications, Capabilities, And Skills list: "Prosci ADKAR certification or equivalent Agile coaching credentials (SPC, CSP, ICP-ACC) and/or org design credentials Experience in payments, merchant acquiring, or other regulated financial services Working knowledge of AI governance frameworks (NIST AI RMF, EU AI Act, internal model risk standards) History of building change communities of practice or change champion networks" Now About Us benefits and pay: From 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." We need to separate Benefits and Pay sections. Pay: "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." Benefits: "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 child