2027 BNY Analyst Program - Office of the COO (New York, NY)

We need to output HTML fragment with sections: headings

for section headings 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. Content: - Title: "Job Description 202 7 BNY Analyst Program – Office of the COO". Not needed as heading. - Intro paragraph about Chief Operating Office practice. - "What You Will Do" section: bullet list of duties. - "Skills You Will Build" section: bullet list. - "Impact you will have at BNY" bullet list. - "Why this could be a fit for you" paragraph. - "Analyst Program" description: details about program. - "Program Eligibility": bullet list? Actually list: Enrollment in a 4-year undergraduate degree program with a strong focus on business-related and/or technology-related majors preferred; Graduating in Dec 2026 or May 2027 (U.S.); Minimum cumulative GPA of 3.0 or better; Does not require sponsorship for employment visa status (now or in the future) in the country where applying. - "About Us": paragraph. - "About The Team": paragraph with links? Might be considered boilerplate? It includes "check out the latest BNY news at BNY Newsroom & BNY LinkedIn". Might be considered navigation? Probably we can keep as paragraph but maybe it's fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About The Team" might be okay but could be considered boilerplate? It's not EEO. It's describing team. Might keep. - "Here’s a Few Of Our Recent Awards": list of awards. Might be considered boilerplate? It's not required but could be kept as it's substantive? Might be considered fluff but it's specific awards. Might keep. - "Our Benefits And Rewards": paragraph about benefits, compensation, etc. This includes mention of compensation details but not specific numbers. It says "The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting." No actual salary given. So we should not create Pay section because no specific salary. Benefits: they talk about benefits but not specific list. It says "We provide access to flexible global resources and tools...". It's generic. Might be considered boilerplate? The instruction: never create Benefits section unless posting actually states them. It does state benefits in general but not specific list. Might be considered too vague. Safer to omit Benefits section. - EEO statement: remove. - Additional paragraphs about base salary variability etc: remove as boilerplate. Thus we need sections: About the role (maybe intro), Responsibilities (What You Will Do), Skills (Skills You Will Build), Impact (Impact you will have at BNY), Qualifications (Program Eligibility), maybe About the team? Could be "About the team". But we need to decide which headings to use. We have content for: - About the role: could be the introductory paragraphs describing the Chief Operating Office practice and what the role is about. That's substantive. - Responsibilities: "What You Will Do" bullet list. - Skills: "Skills You Will Build" bullet list. - Impact: "Impact you will have at BNY" bullet list. - Qualifications: "Program Eligibility" bullet list. - Maybe "About the team": the paragraph about team and awards? Could be considered "About the team". But we have "About Us" and "About The Team". Might combine? The instruction: prefer a few substantive sections over many thin ones. Could combine About Us and About The Team into one "About the company" section? But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Us" heading. So we cannot create arbitrary headings; only those listed. So we must map content to those headings. Thus we can use: -

About the role

: include intro paragraphs describing the Chief Operating Office practice and the role. -

Responsibilities

: bullet list from "What You Will Do". -

Skills

: bullet list from "Skills You Will Build". -

Qualifications

: bullet list from "Program Eligibility". - Possibly

Impact

is not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Impact is not allowed. So we cannot create Impact heading. We could incorporate impact into Responsibilities or Skills? But better to omit if not allowed. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning examples, not exhaustive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create Impact heading. We could incorporate impact into About the role or Responsibilities. But we must preserve ALL substantive information; we cannot omit impact details. So we need to include them somewhere. Could add a

under About the role or Responsibilities. Probably best to add a

after Responsibilities summarizing impact. But we need to keep the bullet list of impact as is? Could convert to

• under a heading like "Impact" but not allowed. Could we use

  Requirements

  for impact? No. Requirements is for requirements. Could we treat impact as part of "Skills"? Not ideal. Maybe we can treat impact as part of "About the role" description. That would preserve the info. So we can include impact bullets as a
  under About the role after the intro paragraphs. Similarly, "Why this could be a fit for you" paragraph could go under About the role as well. "Analyst Program" description could be part of About the role or maybe under Requirements? Not exactly. Could be part of About the role. Thus we need to decide sections: About the role (intro + What You Will Do? Actually responsibilities separate). But we already have Responsibilities heading for duties. So About the role could include the practice description, Why this could be a fit, Analyst Program details, etc. Responsibilities: duties bullet list. Skills: skills bullet list. Qualifications: eligibility bullet list. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, navigation, legal, etc. Also remove "About Us", "About The Team", awards, benefits fluff? But we need to preserve substantive information. Are those substantive? "About Us" describes BNY as leading global financial services company, influence 20% of assets, AI, etc. That's substantive about company. Could be included under About the role? Possibly. But we already have About the role focusing on the role; maybe we can include a brief company description under About the role as well. But we must avoid duplication and boilerplate. The "About Us" paragraph is not boilerplate; it's specific to BNY. Could keep. The "About The Team" paragraph includes links to newsroom and LinkedIn; that might be considered navigation? It's basically a suggestion to check out news. Might be considered boilerplate? It's not essential. Could drop. The awards list: could be considered substantive? It's specific awards. Might keep under About the role as a list. Benefits paragraph: generic but mentions specific benefits like 401(k), medical, dental, vision, life insurance, paid time off. That's substantive. However we cannot create Benefits heading because not allowed? Actually Benefits is allowed heading. So we could create

  Benefits

  if the posting actually states them. It does state benefits: "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." Then later: "BNY assesses market data to ensure a competitive compensation package... Base salary offered may vary... 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." Thus we have specific benefits: 401(k), medical, dental, vision, basic life insurance, paid time off (vacation, sick time), paid volunteer time, annual discretionary incentive award. So we can create Benefits section with a
  • list. Pay: The posting says "The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting." No actual salary given. So we should not create Pay section because no specific salary. Schedule: Not mentioned. Thus sections: About the role, Responsibilities, Skills, Qualifications, Benefits. We need to include all substantive info. Let's extract content: About the role content: - Intro: "The Chief Operating Office practice brings together professionals focused on operational excellence, business management, governance, execution discipline, and enterprise enablement. The practice helps ensure that teams across BNY are equipped to deliver consistent, efficient, and well-governed outcomes while supporting the broader goals of the Platform Operating Model. It serves as a professional home for colleagues whose work strengthens how the organization operates, executes priorities, manages risk, and drives continuous improvement. By connecting practitioners across teams, the Practice promotes consistency, capability building, and the sharing of best practices." - "Why this could be a fit for you" paragraph: "This could be a fit for you if you’re interested in how organizations operate behind the scenes and enjoy bringing structure, coordination, and problem- solving to complex work. It’s an opportunity to build broad business exposure, strengthen your professional skills, and contribute to work that helps teams execute more effectively across the organization." - "Analyst Program" description: paragraphs about 24-month rotational program, induction, enterprise-wide onboarding, meaningful project work, mentorship, exposure, training, premier early-career experience. - "About Us": "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": maybe we can drop. - Awards: "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". Could be a list. We could include awards under About the role as a list. Thus About the role will have multiple paragraphs and maybe a list. Responsibilities: bullet list from "What You Will Do": - Support day-to-day activities and strategic initiatives across the Chief Operating Office (COO), helping drive effective execution against business priorities. - Collaborate with leadership teams and key