Jobs · Information Technology · North Carolina

Executive Business Management Lead

Wells Fargo · Charlotte, NC · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections for headings where content exists. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Keep substantive info. We need to parse the posting. Content: Role Summary paragraph: leads development of executive reporting and strategic business materials... etc. That's about the role. Then "In This Role, You Will" bullet list (actually sentences). Those are responsibilities. Then "Required Qualifications:" list of items. Then "Desired Qualifications:" list. Then "Job Expectations:" includes visa sponsorship not eligible, relocation not available, posting location, posting end date, note about posting may come down early. Then EEO etc boilerplate to remove. We need sections: About the role (summary), Responsibilities (the "In This Role, You Will" bullet points), Requirements (maybe combine Required and Desired? But we have separate headings: Requirements, Qualifications, Skills. The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where. We have Required Qualifications and Desired Qualifications. Could map to Requirements (maybe required) and Qualifications (desired) or Skills. But we also have skills like PowerPoint, Excel etc. Those could go under Skills. We need to avoid filler sections. If we don't have content for Benefits, Pay, Schedule, we must not include those headings. We have no explicit benefits, pay, schedule info. So omit those sections. We have location and posting end date; could be placed under a short

maybe under About the role or a separate meta? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and end date in a short paragraph maybe under About the role or a separate meta paragraph. We must preserve all substantive information; do not invent or summarize away detail. Thus we need to capture: - Role Summary paragraph (the first paragraph). - Responsibilities: the bullet list after "In This Role, You Will". Each sentence could be a list item. - Required Qualifications: list items (5+ years IT in support of Business Services..., 5+ years experience in strategy..., 5+ years experience in Microsoft Office suite...). Those are three items. - Desired Qualifications: list items (many bullet points). We'll capture each as list item. - Job Expectations: includes visa sponsorship not eligible, relocation not available, posting location, posting end date, note about posting may come down early. Also maybe "We Value Equal Opportunity" etc is boilerplate to remove. So we keep the substantive expectations: visa sponsorship not eligible, relocation not available, posting location, posting end date, note about posting may come down early. Possibly also "Job posting may come down early due to volume of applicants." Keep that. We should not include EEO etc. Thus we can have sections:

About the role

... (role summary paragraph)

Responsibilities

  • ... each responsibility
  • ...

Requirements

  • 5+ years of Information Technology in support of Business Services experience, or equivalent demonstrated through one or a combination of the following work experience, training, military experience, education.
  • 5+ years of experience in strategy, business management, consulting, executive reporting, or a related role.
  • 5+ years of experience in Microsoft Office suite such as Word, PowerPoint, Visio, Excel for data visualization

Qualifications

  • Desired Qualifications items...
But we also have Skills maybe separate. However we could treat Desired Qualifications as Qualifications. The Skills could be derived from Required Qualifications (Microsoft Office) but we already have that under Requirements. Might be okay to not have Skills section. We must not create sections with filler. So we will not include Skills if we don't have distinct content beyond what's already covered. Thus final HTML fragment:

About the role

Role Summary This role leads the development of executive reporting and strategic business materials that support decisions, align priorities, and drive action. The ideal candidate can quickly understand a business objective, work through ambiguity, identify what is missing, gather inputs across multiple organizations, and turn fragmented information into a clear point of view and high-impact PowerPoint presentation. This is a business strategy role that requires strong judgment, executive presence, high attention to detail, and managing multiple priorities at one time under tight deadlines. This role requires someone who is self-motivated to learn the business, takes initiative without waiting for detailed direction, and proactively builds the knowledge and relationships needed to deliver results.

But note the text includes "Role Summary" at start; we can keep it as part of paragraph. Better to keep exactly as given but maybe remove the heading "Role Summary". However we must preserve all substantive information; we can keep the phrase "Role Summary" as part of paragraph. Now Responsibilities: list each sentence after "In This Role, You Will". Let's extract: - Own the development of executive-level presentations, business reviews, strategic updates, and other high-visibility business deliverables for an organization delivering technology to Commercial Banking, Corporate and Investment Banking, and Global Payments & Liquidity. - Transform complex, technical, and incomplete inputs into clear, concise, visually compelling PowerPoint narratives tailored to senior executive audiences. - Build the story, not just the slides: define the key message, establish a logical narrative, identify the evidence required, and connect insights to business priorities, decisions, risks, and actions. - Operate effectively with limited initial direction by determining what information is missing, identifying the right sources, engaging stakeholders, and independently developing the remaining content. - Navigate across multiple organizations and levels to collect, validate, reconcile, and synthesize information into one cohesive and accurate executive story. - Partner directly with senior leaders and subject-matter experts to understand the objective, challenge assumptions, clarify the point of view, and shape the final deliverable for maximum impact. - Use strategic judgment to prioritize information, distinguish key messages from supporting detail, and surface the insights most relevant to executive decision-making. - Translate technical or operational content into succinct, business-focused language that can be understood quickly by senior leaders and nontechnical audiences. - Manage multiple high-priority deliverables at the same time, adapt quickly as priorities change, and consistently meet time-sensitive deadlines without sacrificing quality or accuracy. - Maintain the end-to-end lifecycle of executive reporting deliverables by understanding and incorporating changes, proactively communicating updates to stakeholders, and managing the process through a consistent, recurring cadence. - Preserve historical executive presentations and supporting materials through consistent naming conventions and metadata, managing contributor permissions, and ensuring content is accurately organized and easily retrievable. - Apply exceptional attention to detail across content, data, formatting, branding, grammar, version control, and final quality assurance. - Use Excel for foundational analysis, including organizing data, applying formulas, creating pivot tables and charts, and validating information used in executive materials. - Attend and drive executive prep meetings for strategy sessions, business reviews, and upstream forums with accurate, well-structured, and presentation-ready materials. We need to ensure each is a
  • . Now Requirements: the three items as above. Now Qualifications (Desired): list each bullet: - Demonstrated experience independently designing custom executive-level PowerPoint presentations that translate complex information into a clear narrative, persuasive point of view, and actionable conclusion. - Advanced/Expert Level PowerPoint capability, including strong command of story flow, slide structure, visual hierarchy, message clarity, and executive-ready design. - Proven ability to think strategically, connect information across topics, and frame content around business outcomes, decisions, risks, and priorities. - Experience working directly with senior leaders and communicating confidently and professionally in executive settings. - Exceptional written, verbal, and interpersonal skills, with the ability to influence, ask effective questions, present key messaging, and tailor information to the audience. - Demonstrated ability to work independently through ambiguity, identify gaps, and proactively gather the information needed to complete a high-quality deliverable. - Exceptional attention to detail and a consistent record of producing accurate, polished work in a fast-paced, high-demand environment. - Strong organizational and prioritization skills, with the ability to manage multiple concurrent deliverables and changing deadlines. - Working knowledge of Microsoft Excel, including formulas, pivot tables, charts, data organization, and quality checks. - Familiarity with Power BI, Power Automate, and SharePoint is beneficial but not required. - Familiarity with Commercial Banking, Corporate and Investment Banking, or Global Payments & Liquidity is beneficial. Now Job Expectations: we can include a short paragraph under maybe a heading? There's no heading for Job Expectations in allowed list, but we could put under About the role or Responsibilities? Better to create a section maybe "Job Expectations" but not in allowed list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It seems they expect us to use those headings only. So we should map Job Expectations content into one of those sections, maybe under About the role or Responsibilities? But it's not exactly responsibilities. Could be under About the role as additional details. However we already have About the role summary; we could add a

    after summary containing the job expectations (visa, location, etc). That would preserve info. Thus after the About the role paragraph, we can add another

    containing: "This position is not eligible for Visa sponsorship. Relocation assistance is not available for this position. Posting Location: 300 S Brevard St. Charlotte, North Carolina 28202. Posting End Date: 27 Oct 2026. Job posting may come down early due to volume of applicants." We must not include EEO etc. Thus final HTML:

    About the role

    Role Summary This role leads the development of executive reporting and strategic business materials that support decisions, align priorities, and drive action. The ideal candidate can quickly understand a business objective, work through ambiguity, identify what is missing, gather inputs across multiple organizations, and turn fragmented information into a clear point of view and high-impact PowerPoint presentation. This is a business strategy role that requires strong judgment, executive presence, high attention to detail, and managing multiple priorities at one time under tight deadlines. This role requires someone who is self-motivated to learn the business, takes initiative without waiting for detailed direction, and proactively builds the knowledge and relationships needed to deliver results.

    This position is not eligible for Visa sponsorship. Relocation assistance is not available for this position. Posting Location: 300 S Brevard St. Charlotte, North Carolina 28202. Posting End Date: 27 Oct 2026. Job posting may come down early due to volume of applicants.

    Responsibilities

    • Own the development of executive-level presentations, business reviews, strategic updates, and other high-visibility business deliverables for an organization delivering technology to Commercial Banking, Corporate and Investment Banking, and Global Payments & Liquidity.
    • Transform complex, technical, and incomplete inputs into clear, concise, visually compelling PowerPoint narratives tailored to senior executive audiences.
    • Build the story, not just the slides: define the key message, establish a logical narrative, identify the evidence required, and connect insights to business priorities, decisions, risks, and actions.
    • Operate
  • Similar jobs

    Business Management Lead

    LPL FinancialSan Diego, CA· 4 mo ago
    Business Development$73k–$122k/yrapply on lplfinancial.wd1.myworkdayjobs.com

    Business Lead

    Artemis ARCUnited States· 3 mo ago
    RemoteBusiness Developmentapply on artemisarc-aptiveresources.icims.com

    Business Lead

    RampNew York, NY· 2 wk ago
    Business Developmentapply on jobs.ashbyhq.com