AO070 - Bus Strat & Init Mgr

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the job description. First paragraph: "At Bank of America, we are guided by a common purpose..." This is about the company culture. Could be "About the role"? Actually "About the role" is typical heading for description of role. The initial paragraph is more about company purpose, culture, inclusive workplace, etc. Could be considered "About the role" or maybe "About the company". Since only allowed headings are those listed, we can put that under "About the role". It's substantive. Then we have "Bus Strat & Init Mgr | Business Enablement | Program/Project Management and Process Design | H4" - that's like title line, but we must not repeat job title as heading. We can ignore or maybe include as metadata in a short

. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include that line as a short

maybe. Then: "This job is responsible for supporting the development and execution of strategic initiatives and/or processes aligned to priorities within a functional area and/or business. Key responsibilities include defining, developing, executing, monitoring, and/or refining strategic initiatives and processes in close collaboration with key stakeholders and internal partners." That's responsibilities. Then "Core Role Expectations" with bullet-like sentences. Those are responsibilities as well. Then a list of responsibilities: "Develop compelling data-driven narratives..." etc. Those are responsibilities. Then "Identify and promote improvements and simplification in how work is performed." also responsibility. Then "Required Qualifications:" list. Then "Desired Qualifications:" list. Then "Shift: 1st shift (United States of America) Hours Per Week: 40" -> that's schedule info. So we can have a Schedule section. No explicit Pay or Benefits mentioned. So we should not create those sections. We need to use

• for any list of duties/requirements/benefits. For prose, use

  . We need to decide which content goes under which heading. Possible sections: - About the role: includes company purpose paragraph and maybe the short metadata line. - Responsibilities: includes the job responsible sentence, core role expectations, and the bullet list of duties (the develop compelling..., distill..., create..., interpret..., convert..., design..., tailor..., identify...). Could also include the "Key responsibilities include..." sentence. - Requirements: maybe combine Required Qualifications and Desired Qualifications? But we have separate headings: Requirements, Qualifications, Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have multiple possible headings. We need to decide which to use based on content. We have Required Qualifications and Desired Qualifications. Could put Required Qualifications under "Requirements" and Desired Qualifications under "Qualifications" or "Skills". But we also have skills listed (e.g., Strong executive communication..., Advanced PowerPoint skills..., Strong analytical skills..., Advanced proficiency in MS365...). Those could go under Skills. Better to follow typical structure: Requirements (mandatory), Qualifications (preferred), Skills (maybe technical). But we have overlapping. We could do: - About the role: company purpose paragraph + metadata line. - Responsibilities: all responsibility sentences. - Requirements: Required Qualifications list. - Qualifications: Desired Qualifications list. - Skills: maybe we could extract skill statements from Required Qualifications? But they are already there. Could also put skill statements under Skills. However we might duplicate. We could instead put Required Qualifications under Requirements, and Desired Qualifications under Qualifications, and then maybe not have a separate Skills section unless we have distinct skill content not covered. The Required Qualifications includes skills like communication, PowerPoint, analytical, MS365 proficiency. Those are skills but also qualifications. Could still be under Requirements. Given we want few substantive sections over many thin ones, we could combine Required and Desired Qualifications into one "Qualifications" section, and maybe not have Requirements separate. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role, Responsibilities, Qualifications (combining required and desired), Schedule. We could also have Skills if we want to separate technical skills, but that may be thin. Let's see content: Required Qualifications: - Strong executive communication and storyatelling skills, including the ability to prepare concise leadership updates, summarize risks and impacts, and influence data-driven decisions - Demonstrated curiosity, ownership, and initiative in identifying business problems, researching solutions, modernizing processes, and helping build team capability through documentation and knowledge sharing - Advanced PowerPoint skills with demonstrated ability to develop executive-ready presentations that effectively communicate analytical results, business impacts, recommendations, and strategic insights - Strong analytical skills, with an investigative mindset and ability to use data to enhance efficiency and develop reporting to drive business insights - Advanced proficiency in MS365 applications (Excel, PowerPoint, CoPilot) Desired Qualifications: - Experience building dashboards, visualizations, and self-service reporting solutions using Tableau, Power BI, or similar business intelligence tools. - Experience with Alteryx, Python, or comparable automation/data transformation tools to streamline manual processes, improve repeatability, and reduce operational risk - Experience using AI or Microsoft Copilot capabilities to improve productivity, summarize data insights, support documentation, or identify process improvement opportunities - Experience in Global Treasury Servicing, Fulfillment, and Merchant Operations businesses and/or experience supporting large geographically dispersed teams - Strong relationship-building and influencing skills - Ability to lead in a complex, fast-paced environment - Technology or Reporting team experience a plus - PMO, Executive Communications, or COO/Business Management experience a plus - Prior call center or workforce management experience We could combine these into a Qualifications section with two sub-lists? But we only allowed

  • for any list. We could have a single list combining all items, maybe with headings inside? Not allowed. Better to split into Required and Desired as separate headings: Requirements and Qualifications. That gives two sections, still few. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. We need to ensure we don't create empty sections. Now we need to format. About the role: include the company purpose paragraph(s). Also maybe include the short metadata line: "Bus Strat & Init Mgr | Business Enablement | Program/Project Management and Process Design | H4". We'll put that as a

    maybe. Responsibilities: include the sentences: "This job is responsible for supporting the development and execution of strategic initiatives and/or processes aligned to priorities within a functional area and/or business. Key responsibilities include defining, developing, executing, monitoring, and/or refining strategic initiatives and processes in close collaboration with key stakeholders and internal partners." Then the "Core Role Expectations" paragraph (maybe treat as prose). Then the bullet list of duties (starting with "Develop compelling data-driven narratives..."). We need to use

    • for any list of duties/requirements/benefits. So the bullet list should be
      • each. The "Core Role Expectations" is a paragraph; we can keep as

        . Now Requirements: list of Required Qualifications as

        • . Qualifications: list of Desired Qualifications as
          • . Schedule: include "Shift: 1st shift (United States of America) Hours Per Week: 40". Could be a

            . We must not include boilerplate like EEO etc. Not present. Now output only HTML fragment. Let's craft. We'll start with maybe not required; just output the HTML fragment directly. We'll do:

            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 and providing a culture of caring is core to how we drive Responsible Growth. We are intentional about fostering an inclusive workplace where every teammate has the opportunity to succeed, build a career and contribute to our shared success. This includes attracting and developing exceptional talent, recognizing and rewarding performance, and supporting our teammates’ physical, emotional, and financial wellness through affordable, competitive and flexible benefits. We value the unique perspectives individuals bring from all backgrounds and career paths - whether shaped by military service, community college education, or a wide range of work and life experiences. These journeys foster resilience, leadership and innovation, strengthening our workforce and positively impact the communities we serve. Bank of America is committed to an in-office culture that supports collaboration, engagement, and career development. Our approach includes clear in-office expectations, while providing an appropriate level of flexibility based on role-specific responsibilities and business needs. At Bank of America, you can build a successful career with opportunities to learn, grow, and make an impact. Join us!

            Bus Strat & Init Mgr | Business Enablement | Program/Project Management and Process Design | H4

            Responsibilities

            This job is responsible for supporting the development and execution of strategic initiatives and/or processes aligned to priorities within a functional area and/or business. Key responsibilities include defining, developing, executing, monitoring, and/or refining strategic initiatives and processes in close collaboration with key stakeholders and internal partners.

            Core Role Expectations: The Business Strategy & Initiatives Manager will transform complex data into actionable insights that support executive decision-making, risk management, and operational excellence across Global Treasury and Merchant Operations (GTMO). This role partners closely with senior leaders across Treasury Servicing, Fulfillment, Merchant Operations, Workforce Management, Analytics, Command Centers, Reporting, and Communications to enhance operating model effectiveness, identify emerging trends and risks, and deliver streamlined, data-driven solutions that drive strategic outcomes.

            • Develop compelling data-driven narratives that translate data and analytics into actionable insights for senior leaders and key stakeholders.
            • Distill large volumes of information into concise key messages, executive summaries, and decision-support materials.
            • Create visually engaging dashboards, charts, infographics, timelines, and analytical storyboards that simplify complex information and accelerate decision-making.
            • Interpret quantitative results, trends, anomalies, and key performance indicators to identify meaningful business implications and recommendations.
            • Convert technical findings into concise, audience-appropriate language that can be easily understood by both business and non-technical stakeholders.
            • Design presentations that connect data, business context, and strategic objectives into a cohesive and persuasive story.
            • Tailor presentation content and visualizations based on audience type, ranging from operational teams to executive leadership and governance forums.
            • Identify and promote improvements and simplification in how work is performed.

            Requirements

            • Strong executive communication and storyatelling skills, including the ability to prepare concise leadership updates, summarize risks and impacts, and influence data-driven decisions
            • Demonstrated curiosity, ownership, and initiative in identifying business problems, researching solutions, modernizing processes, and helping build team capability through documentation and knowledge sharing
            • Advanced PowerPoint skills with demonstrated ability to develop executive-ready presentations that effectively communicate analytical results, business impacts, recommendations, and strategic insights
            • Strong analytical skills, with an investigative mindset and ability to use data to enhance efficiency and develop reporting to drive business insights
            • Advanced proficiency in MS365 applications (Excel, PowerPoint, CoPilot)

            Qualifications

            • Experience building dashboards, visualizations, and self-service reporting solutions using Tableau, Power BI, or similar business intelligence tools.