Vice President, Compliance & Control (AML Surveillance / Transaction Monitoring)

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 that have real specific content. We need to parse the job description. Content: - Job Description: "We’re seeking a future team member for the role of Vice President, Compliance & Control (VPR) to join our Financial Crimes Compliance (“FCC”) team. This role is located in Pittsburgh, PA or Lake Mary, FL." - Then bullet list of impact ways: "In this role, you’ll make an impact in the following ways:" then list items (each sentence). Those are responsibilities. - Then "To be successful in this role, we’re seeking the following:" then list of qualifications/experience. - Then "About Us" paragraph. - Then "About The Team" paragraph with awards. - Then "Our Benefits And Rewards" paragraph describing benefits. - Then EEO etc (boilerplate) to remove. - Also mention base salary info: "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." We need to include sections only if real specific content. We have: - About the role: maybe the initial paragraph describing role and location. That could be "About the role". Use

About the role

then

with that content. - Responsibilities: the list of impact ways. Use

Responsibilities

then

• each. - Requirements/Qualifications/Skills: The "To be successful..." list includes education, experience, preferred background, certifications. Could split into Requirements (education/experience) and Qualifications (preferred) and Skills (certifications). But we should prefer few substantive sections over many thin ones. Could combine into one section "Requirements" covering all. Or separate "Qualifications" and "Skills". The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We have content for Requirements (Bachelors degree, 5-7 years experience). Qualifications (Financial Services, Audit or Compliance background, experience with assigned products, etc). Skills (Experience in AML Transaction Monitoring desired, Subject matter expertise in financial crimes investigations involving digital assets, correspondent banking, institutional custody, and/or private wealth, ACAMS or CFE certification and intelligence work). Could combine but better to separate as they are distinct. We also have Benefits: "Our Benefits And Rewards" paragraph describing compensation, benefits, wellbeing programs, flexible resources, paid leaves, etc. Also mention base salary info (Pay). So we can have Benefits section and Pay section. Pay: The paragraph about base salary, discretionary incentive award, 401(k), medical etc. Actually that overlaps with Benefits. But we can separate: Benefits (health, wellbeing, paid leaves) and Pay (base salary, incentive award). However the text includes both benefits and pay together. Might be better to have a single Benefits section that includes pay details. But instruction says include Pay section only if posting actually states them. It does state base salary info. So we can include Pay. Schedule: No mention of schedule (remote/hybrid etc). Not present, so omit. About Us and About The Team could be combined into "About the company" but we have headings for About the role only. There's no specific heading for About Us in list but we could treat as "About the company" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings like About Us. So we need to decide where to put that info. Could incorporate into About the role? Or maybe we can omit About Us and About The Team as they are not required headings; but we must preserve ALL substantive information. So we need to include that info somewhere. Since we cannot create arbitrary headings, we could put them under a generic

  after the role description before Responsibilities? But that might break structure. 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, not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. But we could also use other headings if needed? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. Thus we need to fit About Us and About The Team into one of those sections. Perhaps we can put them under "About the role" as a description of the company/team. But About the role is supposed to be about the role, not company. However we could include a brief description of the team within About the role. Or we could create a section "About the team" but not in list; maybe we can treat as "About the role" extended. Alternatively, we could omit About Us and About The Team, but that would lose substantive info (awards, company description). The instruction says preserve ALL substantive information. So we must include them. Thus we need to incorporate them somewhere, maybe as a

  after the role description but before Responsibilities, without a heading? The instruction says use

  for section headings (e.g...). It doesn't say every section must have a heading; we could have a

  without heading. But they likely expect headings for each section. However we could add a heading like "About the company" even if not in the list; risk of being marked wrong. But maybe they'd accept any heading as long as it's

  . The examples are just examples. So we could add

  About the company

  and

  About the team

  . That seems reasonable. But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the expected headings; but they didn't say "only these". Safer to follow the examples but also we could add others if needed. However they said "Prefer a few substantive sections over many thin ones." Adding many headings may be thin. But we have substantive content for About Us and About The Team; we could combine them into one section "About the company and team". That would be one heading. Thus we can have

  About the company and team

  with paragraphs covering both. Now Benefits and Pay: we have benefits description and pay description. Could combine into one section "Benefits and Pay". But they said prefer few substantive sections over many thin ones. So we could combine Benefits and Pay into one section. However they also said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, so we could have separate but combining is okay. Let's decide: We'll have sections: - About the role (location and brief role description) - About the company and team (company description, team, awards) - Responsibilities - Requirements - Qualifications - Skills - Benefits and Pay (combined) That's 7 sections. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract each. **About the role**: Original: "We’re seeking a future team member for the role of Vice President, Compliance & Control (VPR) to join our Financial Crimes Compliance (“FCC”) team. This role is located in Pittsburgh, PA or Lake Mary, FL." We should keep that exactly. **About the company and team**: Combine: About Us paragraph: "At BNY, our culture allows us to run our company better and enables employees’ growth and success. As a leading global financial services company at the heart of the global financial system, we influence nearly 20% of the world’s investible assets. Every day, our teams harness cutting-edge AI and breakthrough technologies to collaborate with clients, driving transformative solutions that redefine industries and uplift communities worldwide. Recognized as a top destination for innovators, BNY is where bold ideas meet advanced technology and exceptional talent. Together, we power the future of finance – and this is what is all about. Join us and be part of something extraordinary." About The Team paragraph: "At BNY, our culture speaks for itself, check out the latest BNY news at BNY Newsroom & BNY LinkedIn Here’s a Few Of Our Recent Awards America’s Most Innovative Companies, Fortune, 2025World’s Most Admired Companies, Fortune 2025“Most Just Companies”, Just Capital and CNBC, 2025" Note there is missing punctuation and spacing; we should preserve as is but maybe fix obvious typos? We should not invent or summarize away detail, but we can keep the text exactly as given, including missing spaces. However we might want to keep readability but not alter meaning. The text: "Here’s a Few Of Our Recent Awards America’s Most Innovative Companies, Fortune, 2025World’s Most Admired Companies, Fortune 2025“Most Just Companies”, Just Capital and CNBC, 2025". There's no space between 2025World’s. We'll keep as is. We'll combine into one

  maybe two paragraphs. **Responsibilities**: List items after "In this role, you’ll make an impact in the following ways:" each sentence. Let's list them: 1. Lead complex, high-risk transaction-based investigations end-to-end (including multi-jurisdictional activity, nested relationships, and multi-product flows) and determine disposition with clear rationale and audit-ready documentation 2. Leverage bank systems/applications when searching for signs of suspicious activity and evaluating internal party or external party Anti-Money Laundering (“AML”) risk 3. Use transactional data to spot patterns and tell the story—efficiently analyze large datasets to identify suspicious behavior, link related parties/activity, and surface actionable insights 4. Provide expertise in transaction monitoring and actively build experience by preparing risk-based reviews of both current and emerging regulatory requirements, addressing concerns and identifying control gaps 5. Conduct Level 2 transaction-based investigations and/or perform quality control reviews 6. Support the firm’s Global Anti-Money Laundering program including providing thorough investigations for Suspicious Activity Report (“SAR”) consideration. 7. Identify and escalate material issues using defined governance, with crisp problem statements and recommended actions 8. Contribute to the preparation of time sensitive reporting and appropriately escalate issues 9. Participate in projects and program activities that aim to