Senior Vice President, Infrastructure Engineer

We need to output HTML fragment with sections: 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. First, we need to identify sections. The posting includes: - Job Description: "We’re seeking a future team member for the role of Senior Vice President, Infrastructure Engineer to join our Technology Infrastructure Engineering team. This role will design, implement, and support enterprise-scale block, file, and object storage platforms while driving automation, modernization, operational stability, and compliance across the storage ecosystem. This role is located in Lake Mary, Florida." Then "In this role, you’ll make an impact in the following ways:" followed by bullet-like sentences (but not bullet list). We can treat as responsibilities. Then "To be successful in this role, we’re seeking the following:" then list of requirements. Then "About Us" section: description of BNY. Then "About The Team": description. Then "Our Benefits And Rewards": description of benefits. Then "BNY is an Equal Employment Opportunity..." etc (EEO boilerplate) which we need to remove. Also there is mention: "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 stated. Similarly schedule not mentioned. Thus we will include sections: About the role (maybe combine intro?), Responsibilities, Requirements, Qualifications? The posting lumps requirements and qualifications together. We could treat "To be successful..." as Requirements/Qualifications. Could split into Requirements and Qualifications but we need to avoid thin sections. Better to have one section: Requirements (or Qualifications). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with content. We have content for About the role (intro). Responsibilities (impact ways). Requirements/Qualifications (the "To be successful..." list). Skills (maybe we can extract skills from requirements: Python, Ansible, AI capabilities, etc). But we could also put skills within Requirements. However we could create a Skills section if we have specific skill list. The posting includes many specific technologies and skills. Could create Skills section enumerating them. But we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section, maybe called Requirements. Or we could have Requirements and Qualifications both but they'd be thin. Better to have one. Benefits: we have "Our Benefits And Rewards" section with description. So we can include Benefits. Pay: no specific salary, so omit. Schedule: not mentioned, omit. Thus output HTML with sections: About the role, Responsibilities, Requirements, Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO etc. We need to include location? The intro includes location: "This role is located in Lake Mary, Florida." That's substantive; we should keep it. We need to preserve all details: list of platforms, tasks, etc. Let's extract. Intro paragraph: "We’re seeking a future team member for the role of Senior Vice President, Infrastructure Engineer to join our Technology Infrastructure Engineering team. This role will design, implement, and support enterprise-scale block, file, and object storage platforms while driving automation, modernization, operational stability, and compliance across the storage ecosystem. This role is located in Lake Mary, Florida." We can put that in

  under About the role. Responsibilities: after "In this role, you’ll make an impact in the following ways:" then list of sentences separated by semicolons? Actually each sentence ends with a period. Let's capture each as a bullet. List: - Design, implement, and support high-performance, scalable, and resilient storage solutions across block platforms such as Dell PowerMax/VMAX, Pure Storage, PowerFlex, and XtremIO; file platforms including NetApp ONTAP and Dell PowerScale; and object platforms including NetApp StorageGRID and Pure FlashBlade. - Provide Level 3 engineering support across the storage estate, including complex troubleshooting, performance and availability analysis, capacity planning, sizing, data protection, replication, and operational stability. - Define and certify storage technologies, establish platform standards, and create build, engineering, and operational documentation that supports consistent delivery in a global, multi-vendor environment. - Lead critical projects and strategic initiatives, including large-scale technology refreshes, NAS and SAN migrations, CAS-to-S3 transitions, platform upgrades, lifecycle management, and on-premises infrastructure deployments. - Collaborate with application, compute, network, cybersecurity, data protection, governance, and operations teams to design storage architectures that meet performance, scalability, resiliency, and regulatory requirements. - Drive automation and process optimization using Python, Ansible, AI capabilities, and coding assistants such as Windsurf to improve provisioning, monitoring, operational efficiency, and platform standardization. - Ensure adherence to enterprise data-protection, governance, and compliance requirements through capabilities such as SnapLock, Object Lock, snapshots, and replication. We need to keep each as separate

• . Now Requirements/Qualifications: after "To be successful in this role, we’re seeking the following:" then list. List items: - Strong experience in enterprise storage engineering, with a proven record of designing, deploying, operating, and supporting large-scale block, file, and object storage environments. - Deep expertise in SAN and NAS architecture, S3-based object storage design, and protocols including Fibre Channel SAN, NFS, SMB, and S3. - Hands-on knowledge of Dell PowerMax/VMAX, XtremIO, PowerFlex, Pure Storage, NetApp ONTAP, Dell PowerScale, NetApp StorageGRID, Dell ECS, and Pure FlashBlade. - Strong understanding of SAN fabrics, including Cisco MDS and Brocade, as well as compute integration and on-premises infrastructure deployment. - Experience with storage management and engineering tools such as Solutions Enabler, Unisphere, DCNM, AIQUM, OCI/CI, InsightIQ, ActiveIQ, SyncIQ, Cyberduck, AWS CLI, and S3 APIs. - Demonstrated capability in capacity planning, performance optimization, availability troubleshooting, storage-tier design, and legacy-to-modern migration strategies. - Proficiency in Python and Ansible, with the ability to build scalable automation for provisioning, monitoring, operational efficiency, and repeatable infrastructure delivery. - Experience applying AI capabilities and coding assistants, including Windsurf, to accelerate engineering outcomes and identify opportunities for continuous improvement. - Ability to lead complex programs and strategic initiatives while operating effectively across global, multi-vendor, and highly regulated environments. - Strong collaboration, technical leadership, documentation, and problem-solving skills, with a focus on standardization, modernization, and measurable operational improvement. We can keep as
• . Now Benefits: after "Our Benefits And Rewards" heading. Paragraph: "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." Then later: "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." We need to remove boilerplate like EEO etc. The benefits section includes some generic statements but we should keep substantive info: competitive compensation, benefits, wellbeing programs, flexible global resources, focus on health, personal resilience, financial goals, generous paid leaves including paid volunteer time, 401(k) plan, medical/dental/vision/basic life insurance, other benefits like paid time off (vacation, sick). Also mention that base salary info is in Job Info section (but we don't have actual salary). We can keep that sentence but it's not specific salary; still it's substantive? It says expected base salary can be found in Job Info section at bottom. That's a reference; we could keep it as it's part of benefits description. However we should not create Pay section. It's okay to mention within Benefits that salary details are elsewhere. We should remove the EEO line: "BNY is an Equal Employment Opportunity/Affirmative Action Employer - Underrepresented racial and ethnic groups/Females/Individuals with Disabilities/Protected Veterans." Also remove any duplicated lines. Also remove "About Us", "About The Team" sections? The instruction says we should include sections only when posting has real specific content. Those sections have content about BNY culture, awards, etc. That is substantive. Should we include them? The allowed headings list does not include "About Us" or "About The Team". We could fold that content into About the role? But About the role is supposed to be about the role, not company. However we could create an "About Us" section but not in allowed headings. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? 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 other headings. We could incorporate the About Us/Team content into About the role? But that would be mixing company info with role info. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid adding other headings, but the examples suggest those are the expected sections. Safer to stick to those headings and incorporate any relevant company info into About the role or Benefits? The About Us content is about company culture, awards, etc. Could be considered part of "About the role"? Not really. But we could create a section "About the role" and include both role description and company overview? Might be okay. Alternatively we could treat "About Us" as part of "About the role" but that seems a stretch. Given the instruction to prefer few substantive sections, we could omit the About Us/Team content entirely? But that would be losing substantive information. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep that info. So we need to include it somewhere. Since we cannot create a heading outside the allowed list, we could fold it into a

  under an existing heading, maybe