Senior Vice President, AI Strategy Lead
BNY · New York, NY · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job description.
First, the job title is Senior Vice President, AI Strategy Lead. Not to repeat as heading.
We need sections: About the role (maybe from first paragraph?), Responsibilities (list of duties), Requirements (experience etc.), Qualifications (education), Skills (maybe not explicit), Benefits (some content about benefits), Pay (salary info), Schedule (maybe not present). Also "About Us" and "About The Team" maybe not needed as sections? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings if present.
We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove "About Us", "About The Team", awards maybe not needed? They might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove "About Us" or awards. But they might be considered not part of the core job description; but they are substantive info about company. However the instruction says "Prefer a few substantive sections over many thin ones." Might include About Us as part of "About the role"? Not sure.
We need to decide which sections to include.
Let's extract content:
Job Description paragraph: "We’re seeking a future team member for the role of Senior Vice President, AI Strategy Lead. This role is located in New York City."
Then "In this role, you’ll make an impact in the following ways:" followed by bullet-like sentences (actually each sentence is a responsibility). We can treat these as responsibilities list.
Then "To be successful in this role, we’re seeking the following:" followed by bullet-like sentences (experience, etc.) This is requirements/qualifications.
Then "About Us" paragraph about BNY.
Then "About The Team" paragraph with news, awards.
Then "Our Benefits And Rewards" paragraph describing benefits.
Then EEO statement etc.
We need to include Benefits section if posting actually states them. Yes there is benefits description.
Pay section: The posting mentions: "BNY assesses market data to ensure a competitive compensation package for our employees. The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting. Base salary offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. Base salary is only part of the total rewards package, which may include eligibility for an annual discretionary incentive award. Subject to the terms and conditions of the applicable plans then in effect, eligible employees may enroll in a 401(k) plan as well as participate in Company-sponsored medical, dental, vision, and basic life insurance plans for the employee and the employee’s eligible dependents. Eligible employees also may receive other benefits (including various paid time off benefits, such as vacation and sick time), dependent on the position offered. Details of participation in these benefit plans will be provided if an employee receives an offer of employment. If hired, the employee will be in an “at will” position and the Company reserves the right to modify base salary (as well as any other discretionary payments or compensation programs) at any time, including for reasons related to individual performance, Company or individual department/team performance, and market factors."
This includes pay info but not explicit numbers. It says expected base salary can be found in Job Info section at bottom (not provided). So we have no specific salary figure. The instruction: 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 actually states them. Since the posting does not state a specific salary figure, but does talk about compensation generally, is that considered stating them? It mentions base salary may vary, eligibility for incentive award, 401k, medical etc. That's more benefits. Pay section might be considered not having specific numbers, but we could still include Pay if we have some info like "competitive compensation", "base salary may vary", "annual discretionary incentive award". However the instruction says avoid filler like "varies". It says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay (competitive compensation, base salary may vary). That's still stating something, albeit vague. But we risk violating the rule about filler/placeholder text like "varies". The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section and the content includes "varies", that might be considered filler. Better to omit Pay section if we don't have concrete numbers. However we could include Pay section with the content that is not just "varies". But the content includes "Base salary offered may vary depending on multiple individualized factors". That's a variation statement. Might be considered filler. Safer to omit Pay section.
Schedule: No mention of schedule (full-time, part-time, remote). So omit.
Benefits: We have benefits description. That's substantive. So include Benefits section.
Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits.
We need to decide what goes where.
About the role: Could include location and brief overview: "We’re seeking a future team member for the role of Senior Vice President, AI Strategy Lead. This role is located in New York City." That's about the role.
Responsibilities: The list after "In this role, you’ll make an impact in the following ways:" each sentence.
Requirements: Could be experience requirements: "Typically 10+ years of experience in corporate strategy, strategy consulting, product strategy, AI/data strategy, enterprise transformation, or digital transformation. Experience leading AI, GenAI, automation, data, analytics, or technology-enabled transformation initiatives. Strong commercial judgment and experience developing business cases, roadmaps, KPIs, and executive recommendations. Demonstrated ability to influence senior stakeholders in a global, matrixed organization. Financial-services and responsible-AI experience are preferred."
Qualifications: Education: "Bachelor’s degree required; MBA or relevant Master’s degree preferred."
Skills: Could be derived from responsibilities? Not explicit. Might omit Skills if no explicit list.
We could combine Requirements and Qualifications into one section? But instructions say use headings for those if present. We have both.
We need to ensure we don't repeat content.
Now Benefits: The paragraph under "Our Benefits And Rewards". Also the later paragraph about 401k etc. Actually the benefits description includes both the earlier paragraph and later details about 401k etc. We should combine all benefit-related content into Benefits section.
We need to remove boilerplate: EEO statement, "BNY is an Equal Employment Opportunity/Affirmative Action Employer..." etc. Also remove "About Us", "About The Team", awards maybe? The instruction didn't explicitly say to remove them, but they are not part of the standard headings. However they are substantive about company. Could we include them under About the role? Possibly not. The instruction says "Prefer a few substantive sections over many thin ones." Including About Us and About Team would create extra sections not in the list. Better to omit them, as they are not requested headings. 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 says prefer few substantive sections. So we should stick to those headings only if we have content. So we omit About Us and About Team.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job description.
First, the job title is Senior Vice President, AI Strategy Lead. Not to repeat as heading.
We need sections: About the role (maybe from first paragraph?), Responsibilities (list of duties), Requirements (experience etc.), Qualifications (education), Skills (maybe not explicit), Benefits (some content about benefits), Pay (salary info), Schedule (maybe not present). Also "About Us" and "About The Team" maybe not needed as sections? The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings if present.
We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions). Also remove "About Us", "About The Team", awards maybe not needed? They might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove "About Us" or awards. But they might be considered not part of the core job description; but they are substantive info about company. However the instruction says "Prefer a few substantive sections over many thin ones." Might include About Us as part of "About the role"? Not sure.
We need to decide which sections to include.
Let's extract content:
Job Description paragraph: "We’re seeking a future team member for the role of Senior Vice President, AI Strategy Lead. This role is located in New York City."
Then "In this role, you’ll make an impact in the following ways:" followed by bullet-like sentences (actually each sentence is a responsibility). We can treat these as responsibilities list.
Then "To be successful in this role, we’re seeking the following:" followed by bullet-like sentences (experience, etc.) This is requirements/qualifications.
Then "About Us" paragraph about BNY.
Then "About The Team" paragraph with news, awards.
Then "Our Benefits And Rewards" paragraph describing benefits.
Then EEO statement etc.
We need to include Benefits section if posting actually states them. Yes there is benefits description.
Pay section: The posting mentions: "BNY assesses market data to ensure a competitive compensation package for our employees. The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting. Base salary offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. Base salary is only part of the total rewards package, which may include eligibility for an annual discretionary incentive award. Subject to the terms and conditions of the applicable plans then in effect, eligible employees may enroll in a 401(k) plan as well as participate in Company-sponsored medical, dental, vision, and basic life insurance plans for the employee and the employee’s eligible dependents. Eligible employees also may receive other benefits (including various paid time off benefits, such as vacation and sick time), dependent on the position offered. Details of participation in these benefit plans will be provided if an employee receives an offer of employment. If hired, the employee will be in an “at will” position and the Company reserves the right to modify base salary (as well as any other discretionary payments or compensation programs) at any time, including for reasons related to individual performance, Company or individual department/team performance, and market factors."
This includes pay info but not explicit numbers. It says expected base salary can be found in Job Info section at bottom (not provided). So we have no specific salary figure. The instruction: 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 actually states them. Since the posting does not state a specific salary figure, but does talk about compensation generally, is that considered stating them? It mentions base salary may vary, eligibility for incentive award, 401k, medical etc. That's more benefits. Pay section might be considered not having specific numbers, but we could still include Pay if we have some info like "competitive compensation", "base salary may vary", "annual discretionary incentive award". However the instruction says avoid filler like "varies". It says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay (competitive compensation, base salary may vary). That's still stating something, albeit vague. But we risk violating the rule about filler/placeholder text like "varies". The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section and the content includes "varies", that might be considered filler. Better to omit Pay section if we don't have concrete numbers. However we could include Pay section with the content that is not just "varies". But the content includes "Base salary offered may vary depending on multiple individualized factors". That's a variation statement. Might be considered filler. Safer to omit Pay section.
Schedule: No mention of schedule (full-time, part-time, remote). So omit.
Benefits: We have benefits description. That's substantive. So include Benefits section.
Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits.
We need to decide what goes where.
About the role: Could include location and brief overview: "We’re seeking a future team member for the role of Senior Vice President, AI Strategy Lead. This role is located in New York City." That's about the role.
Responsibilities: The list after "In this role, you’ll make an impact in the following ways:" each sentence.
Requirements: Could be experience requirements: "Typically 10+ years of experience in corporate strategy, strategy consulting, product strategy, AI/data strategy, enterprise transformation, or digital transformation. Experience leading AI, GenAI, automation, data, analytics, or technology-enabled transformation initiatives. Strong commercial judgment and experience developing business cases, roadmaps, KPIs, and executive recommendations. Demonstrated ability to influence senior stakeholders in a global, matrixed organization. Financial-services and responsible-AI experience are preferred."
Qualifications: Education: "Bachelor’s degree required; MBA or relevant Master’s degree preferred."
Skills: Could be derived from responsibilities? Not explicit. Might omit Skills if no explicit list.
We could combine Requirements and Qualifications into one section? But instructions say use headings for those if present. We have both.
We need to ensure we don't repeat content.
Now Benefits: The paragraph under "Our Benefits And Rewards". Also the later paragraph about 401k etc. Actually the benefits description includes both the earlier paragraph and later details about 401k etc. We should combine all benefit-related content into Benefits section.
We need to remove boilerplate: EEO statement, "BNY is an Equal Employment Opportunity/Affirmative Action Employer..." etc. Also remove "About Us", "About The Team", awards maybe? The instruction didn't explicitly say to remove them, but they are not part of the standard headings. However they are substantive about company. Could we include them under About the role? Possibly not. The instruction says "Prefer a few substantive sections over many thin ones." Including About Us and About Team would create extra sections not in the list. Better to omit them, as they are not requested headings. 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 says prefer few substantive sections. So we should stick to those headings only if we have content. So we omit About Us and About Team.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
About the role
We’re seeking a future team member for the role of Senior Vice President, AI Strategy Lead. This role is located in New York City.
Responsibilities
- Lead complex AI strategy workstreams and translate enterprise priorities into strategic themes, investment choices, operating-model recommendations, roadmaps, and executable plans.
- Shape AI Hub’s strategic agenda across AI-native platforms, digital employees, workflow automation, knowledge management, process reimagination, governed AI capabilities, and continuous intelligence.
- Identify, assess, and prioritize AI opportunities based on business value, client impact, operational efficiency, strategic alignment, technical feasibility, control readiness, adoption potential, and implementation complexity.
- Develop business cases, value hypotheses, cost-benefit analyses, KPI frameworks, adoption measures, and benefit-realization plans for priority initiatives.
- Define how AI capabilities can help platforms become more intelligent, context-aware, governed, reusable, and scalable across enterprise workflows.
- Advance continuous-intelligence priorities by connecting trusted data, governed AI, human judgment, operational context, and enterprise controls to practical business outcomes.
- Develop recommendations for AI operating models, prioritization mechanisms, portfolio governance, investment sequencing, adoption strategies, and cross-functional accountability.
- Produce executive-ready strategy narratives, decision papers, presentations, portfolio updates, and recommendations that simplify complex AI topics without overstating maturity or expected benefits.
- Partner with Product, Engineering, Data, Operations, Finance, Risk, Governance, Legal, Compliance, Audit, and business teams to align strategy with execution feasibility and enterprise standards.
- Ensure strategic recommendations address data readiness, responsible AI, model and technology risk, cybersecurity, privacy, resiliency, human oversight, regulatory considerations, and change management.
- Track emerging developments across GenAI, agentic workflows, enterprise AI platforms, automation, data products, model providers, and market practices to inform strategic choices.
- Establish portfolio transparency by defining consistent measures for initiative status, strategic alignment, adoption, value, dependencies, control readiness, and delivery progress.
- Lead senior-stakeholder discussions, frame decision options, clarify tradeoffs, and drive alignment on priorities and recommended actions.
- Build durable internal AI strategy capability by creating reusable strategic frameworks, analysis methods, decision templates, and value-measurement approaches.
- Operate independently as a senior individual contributor, bringing structured judgment and executive-quality output to high-priority and often ambiguous enterprise initiatives.
Requirements
- Typically 10+ years of experience in corporate strategy, strategy consulting, product strategy, AI/data strategy, enterprise transformation, or digital transformation.
- Experience leading AI, GenAI, automation, data, analytics, or technology-enabled transformation initiatives.
- Strong commercial judgment and experience developing business cases, roadmaps, KPIs, and executive recommendations.
- Demonstrated ability to influence senior stakeholders in a global, matrixed organization.
- Financial-services and responsible-AI experience are preferred.
Qualifications
Bachelor’s degree required; MBA or relevant Master’s degree preferred.
Benefits
BNY offers highly competitive compensation, benefits, and wellbeing programs rooted in a strong culture of excellence and our pay-for-performance philosophy. We provide access to flexible global resources and tools for your life’s journey. Focus on your health, foster your personal resilience, and reach your financial goals as a valued member of our team, along with generous paid leaves, including paid volunteer time, that can support you and your family through moments that matter.
Subject to the terms and conditions of the