Senior Architect - Storage Solutions

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. The posting includes: a description about Bank of America (mission, culture) maybe "About the role"? Actually "About the role" could be the introductory paragraph about the company and role. We have a "Job Description" repeated. The content includes: "This job is responsible for defining an architectural vision..." etc. Also "Position Summary:" etc. Then "Responsibilities:" list. Then "Required Qualifications:" list. Then "Desired Qualifications:" maybe part of qualifications? Could combine Required and Desired under Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities, Qualifications (maybe Required + Desired), Skills. Also we have Shift and Hours Per Week info -> that could go under Schedule? The posting says "Other Shift: 1st shift (United States of America) Hours Per Week: 40". That's schedule info. So we can include a Schedule section with that info. We have no explicit Benefits or Pay info. So we should NOT create those sections. We also have "About the role": we could use the introductory paragraphs about Bank of America mission and culture as About the role. Or maybe the first paragraph before "Job Description:" is about the company. We'll treat that as About the role. We must not repeat the job title as heading. The job title is Senior Storage Architect but we shouldn't put that as heading. We must not include Job ID/requisition numbers (none present). Remove boilerplate like EEO etc (none). Remove duplicated lines: there is a duplicated "Job Description:" line at start and later. We'll keep only one. We must preserve all substantive information. So we need to include all details from the description, responsibilities, qualifications, skills, shift/hours. We need to format lists with

• . For prose use

  . We need to decide how to split content. About the role: Could be the first paragraph: "At Bank of America, we are guided by a common purpose to help make financial lives better through the power of every connection. We do this by driving Responsible Growth and delivering for our clients, teammates, communities and shareholders every day. Being a Great Place to Work is core to how we drive Responsible Growth. This includes our commitment to being an inclusive workplace, attracting and developing exceptional talent, supporting our teammates’ physical, emotional, and financial wellness, recognizing and rewarding performance, and how we make an impact in the communities we serve. Bank of America is committed to an in-office culture with specific requirements for office-based attendance and which allows for an appropriate level of flexibility for our teammates and businesses based on role-specific considerations. At Bank of America, you can build a successful career with opportunities to learn, grow, and make an impact. Join us!" That's substantive. Then Responsibilities: we have a block after "Responsibilities:" with many sentences separated by line breaks? Actually it's a long paragraph with no clear bullet points but each sentence seems a responsibility. We could split each sentence into

• . However the instruction: Use
  • for any list of duties/requirements/benefits. The responsibilities block is not explicitly a list but it's a series of duties. We could treat as list items. Better to split by sentences. Let's extract responsibilities sentences: - Works across the business, operations and technology to create the solution intent and architectural vision for complex solutions and prioritize functional and non-functional requirements into a technology backlog to enable the technology roadmap and functionality to support evolving capabilities and services - Contributes to the creation of the architecture roadmap of defined domains (Business, Application, Data, and Technology) in support of the product roadmap and the development of best practices including standardized templates - Clarifies the architecture, assists with system design to support implementation, and provides solution options to resolve any architectural impediments - Facilitates solution driven discussions, leads the design of complex architectures, and finds creative solutions through knowledge of domain, practical experiments, and proof of concepts while ensuring architecture is flexible, modular, and adaptable - Educates team members on the technology practices, standardization strategies, and best practices to create innovative solutions - Supports the team as needed to select the technology stack required for solutions and helps select preferred technology products - Performs design and code reviews to ensure all non-functional requirements are sufficiently met (for example, security, performance, maintainability, scalability, usability, and reliability) - Serve as the lead architect for enterprise midrange storage services, including File/NAS Storage, Block Storage, Object Storage and Data Protection and Backup Services - Create and maintain storage blueprints, reference architectures, technology standards, strategic roadmaps and product lifecycle strategies - Define future-state architectures and transition plans for storage and data protection services. - Evaluate emerging technologies, market trends, and vendor roadmaps to identify innovation opportunities and strategic investments. - Work closely with Product Managers and Technical Product Managers to define service capabilities, service offerings, operational requirements, and customer adoption strategies. - Collaborate with Vendor Managers and strategic technology partners to influence product direction, review roadmaps, and drive feature adoption. - Provide architecture governance and design reviews for strategic projects and application onboarding efforts. - Support capacity planning, scalability planning, performance architecture, data protection strategy, cyber resiliency, and disaster recovery initiatives. - Author and present architecture recommendations to senior leadership, engineering teams, risk organizations, and project stakeholders. That's many items. Qualifications: We have Required Qualifications and Desired Qualifications. Could combine under Qualifications heading with sub-sections? But we only allowed headings list; we could still have

    Qualifications

    and then inside we could have

    for prose and

    • for list items. We could separate Required and Desired as separate
      maybe with a note? But we must not invent headings like "Required Qualifications". We can just list all qualifications under Qualifications, maybe separate with a note? But we must preserve all substantive information; we can include both required and desired as list items, maybe with a prefix? However that could lose distinction. Better to keep two lists: one for Required, one for Desired, but still under same heading? Could use

      but not allowed? Only specified headings list; we could still use

      but 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 to be safe we stick to

      for sections and use

      or

      inside. We could include a

      stating "Required Qualifications:" then list, then another

      "Desired Qualifications:" then list. That preserves info. Skills: There's a "Skills:" line followed by a list: Analytical Thinking, Architecture, Result Orientation, Solution Design, Technical Strategy Development, Application Development, Collaboration, Data Management, DevOps Practices, Risk Management. Also "Other Shift: 1st shift (United States of America) Hours Per Week: 40" is schedule. Thus Skills section: list those. Schedule: include shift and hours. Now we need to output only HTML fragment. Let's craft:

      About the role

      At Bank of America, we are guided by a common purpose to help make financial lives better through the power of every connection. We do this by driving Responsible Growth and delivering for our clients, teammates, communities and shareholders every day. Being a Great Place to Work is core to how we drive Responsible Growth. This includes our commitment to being an inclusive workplace, attracting and developing exceptional talent, supporting our teammates’ physical, emotional, and financial wellness, recognizing and rewarding performance, and how we make an impact in the communities we serve. Bank of America is committed to an in-office culture with specific requirements for office-based attendance and which allows for an appropriate level of flexibility for our teammates and businesses based on role-specific considerations. At Bank of America, you can build a successful career with opportunities to learn, grow, and make an impact. Join us!

      Responsibilities

      • Works across the business, operations and technology to create the solution intent and architectural vision for complex solutions and prioritize functional and non-functional requirements into a technology backlog to enable the technology roadmap and functionality to support evolving capabilities and services
      • Contributes to the creation of the architecture roadmap of defined domains (Business, Application, Data, and Technology) in support of the product roadmap and the development of best practices including standardized templates
      • Clarifies the architecture, assists with system design to support implementation, and provides solution options to resolve any architectural impediments
      • Facilitates solution driven discussions, leads the design of complex architectures, and finds creative solutions through knowledge of domain, practical experiments, and proof of concepts while ensuring architecture is flexible, modular, and adaptable
      • Educates team members on the technology practices, standardization strategies, and best practices to create innovative solutions
      • Supports the team as needed to select the technology stack required for solutions and helps select preferred technology products
      • Performs design and code reviews to ensure all non-functional requirements are sufficiently met (for example, security, performance, maintainability, scalability, usability, and reliability)
      • Serve as the lead architect for enterprise midrange storage services, including File/NAS Storage, Block Storage, Object Storage and Data Protection and Backup Services
      • Create and maintain storage blueprints, reference architectures, technology standards, strategic roadmaps and product lifecycle strategies
      • Define future-state architectures and transition plans for storage and data protection services.
      • Evaluate emerging technologies, market trends, and vendor roadmaps to identify innovation opportunities and strategic investments.
      • Work closely with Product Managers and Technical Product Managers to define service capabilities, service offerings, operational requirements, and customer adoption strategies.
      • Collaborate with Vendor Managers and strategic technology partners to influence product direction, review roadmaps, and drive feature adoption.
      • Provide architecture governance and design reviews for strategic projects and application onboarding efforts.
      • Support capacity planning, scalability planning, performance architecture, data protection strategy, cyber resiliency, and disaster recovery initiatives.
      • Author and present architecture recommendations to senior leadership, engineering teams, risk organizations, and project stakeholders.

      Qualifications

      Required Qualifications:

      • Bachelor's degree in Computer Science, Information Systems, Engineering, or related field, or equivalent work experience.
      • 10+ years of experience in enterprise infrastructure, storage engineering, or storage architecture.
      • 5+ years of experience designing and architecting enterprise storage solutions.
      • Deep expertise in enterprise storage and backup platforms such as NetApp ONTAP, Dell PowerMax, Hitachi HCP, NetApp StorageGRID, Cohesity, NetBackup
      • Strong understanding of NAS protocols (NFS, SMB), SAN technologies (Fibre Channel, iSCSI, NVMe/TCP), Object Storage (S3) and Backup and recovery architectures
      • Experience developing technology roadmaps and strategic infrastructure plans.
      • Experience producing architecture documentation, blueprints, and design standards.
      • Proven ability to lead complex infrastructure architecture initiatives across multiple teams.
      • Excellent written, verbal, and presentation skills.

      Desired Qualifications:

      • Experience with Cloud-native storage services, VMware Cloud Foundation, OpenShift and Kubernetes platforms, Infrastructure automation and DevOps practices, Cyber recovery vault solutions, Large-scale data center modernization programs
      • Experience influencing strategic product roadmaps through direct engagement with vendors and technology partners.
      • Experience presenting architectural recommendations and investment strategies to executive leadership.