Branch Manager - Raleigh Southeast District

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 specific content. Must preserve all substantive info, remove boilerplate, etc. We need to parse the posting. First part: "Why Wells Fargo Are you looking for more? Find it here. At Wells Fargo, we're more than a financial services leader - we're a global trailblazer committed to driving innovation, empowering communities, and helping our customers succeed. We believe that a meaningful career is much more than just a job - it's about finding all of the elements to help you thrive, in one place. Living the Well Life means you're supported in life, not just work. It means having robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being. You'll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow. And we're recognized for it - Wells Fargo once again ranked in the top five on the 2026 LinkedIn Top Companies list of best workplaces "to grow your career" in the U.S. Join us!" That's company overview, not a specific section heading. Could be "About the role"? Actually "About This Role" appears later. The first part is generic company description; we could include it under "About the role"? But the instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have "About This Role" heading in the posting: "About This Role Wells Fargo is seeking accomplished, people-focused leaders interested in a Branch Manager career within the National Branch Network. ..." So we can map that to "About the role". We'll put that content under

About the role

with

. Then we have "In This Role You Will" bullet list of duties. That maps to Responsibilities. We'll put

Responsibilities

with

• items. Then "Required Qualifications:" and "Desired Qualifications:" and "Job Expectations:" etc. We need to map to Requirements, Qualifications, Skills maybe. The instruction: Use sections for Requirements, Qualifications, Skills. We need to decide where each piece goes. We have Required Qualifications (5+ years banking, 2+ years leadership). Desired Qualifications (list of abilities). Job Expectations (schedule, travel, SAFE registration, loan originator requirements, credit report, no visa sponsorship, posting end date). Also there is mention of benefits earlier in company overview: robust benefits, competitive compensation, programs for work-life balance. That could go under Benefits and Pay maybe. But we should only include sections if posting actually states them. The posting does mention robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being. That's benefits and compensation. So we can include Benefits and Pay sections. Schedule: The posting mentions ability to work a schedule that includes Saturdays, ability to travel up to 50% of time. That's schedule and travel. So we can include Schedule section. We must not include placeholder like "commensurate with experience". Not present. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can group them. Let's extract content: Company overview (Why Wells Fargo) maybe not needed as a section; but we could incorporate into About the role? However About the role already has its own content. The company overview is separate; but we could still include it as a paragraph under About the role? The instruction: "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 including company overview as a paragraph; but we need to decide where to place it. Since we have About the role section, we could put the company overview as a paragraph before the About the role content? But the instruction says use headings for sections; we can have multiple

  elements under a heading. So we could put the company overview as a

  under About the role heading, then the specific About This Role content as another

  . That would preserve all info. Alternatively, we could create a separate section like "About Wells Fargo" but not in allowed headings list. Better to stick to allowed headings. Thus under

  About the role

  we will have two paragraphs: first the company overview (Why Wells Fargo...), second the About This Role description. Now Responsibilities: from "In This Role You Will" list. Need to capture each bullet as
• . The text after "In This Role You Will" is a run-on sentence with multiple clauses separated by periods? Let's parse: "In This Role You Will Provide strong, inclusive leadership to build and retain a high-performing team, establishing clear expectations, and managing performance through targeted coaching to deliver sales, service, and operational excellence.Lead a branch team to proactively identify customer financial needs and deliver tailored consumer and business solutions that drive both customer value and business outcomes.Use branch manager routines to build individual capability, confidence, and productivity, delivering consistent, high-impact coaching through observation, feedback, and follow-up while holding the team accountable to behaviors and outcomes aligned to Wells Fargo priorities.Partner closely with internal sales partners to provide customers a comprehensive, coordinated Wells Fargo experience across Wealth & Investment Management, Business Banking, and Home Lending to maximize relationship depth, customer value, and branch performance.Identify opportunities for making banking easier for customers through education and demonstration of available digital options.Leverage reporting and employee observations to gain insight into strengths and opportunities, taking decisive action to improve team performance and expand primary bank relationships and wallet share.Demonstrate ownership by balancing growth, operational soundness, and talent decisions while proactively managing risk, resolving issues, and modeling behaviors that protect customers, employees, and the company." We need to split into separate responsibilities. Each sentence seems a separate bullet. We'll create
• for each. Now Requirements: maybe we combine Required Qualifications and Job Expectations? But we have separate headings: Requirements, Qualifications, Skills. We need to decide mapping. We could put Required Qualifications under

  Requirements

  . Desired Qualifications under

  Qualifications

  . Skills maybe under

  Skills

  (some of desired qualifications are skills). However we might overlap. Better to follow typical structure: Requirements = mandatory (required qualifications). Qualifications = desired qualifications. Skills = maybe specific abilities listed (like ability to analyze performance, etc.) but those are already in desired qualifications. Could also put skills under Qualifications. But we need to avoid empty sections. We have content for Required Qualifications and Desired Qualifications. We could put Required Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe Skills could be omitted if no distinct skill list beyond those. However we have some skill-like statements in Desired Qualifications: "Proven ability to hire, coach, and develop sales professionals...", "Demonstrated ability to lead a customer-focused sales culture...", "Ability to analyze performance...", "Exercise independent judgement...", "Demonstrated success managing and coaching across affluent...", "Ability to lead teams in influencing, educating, and connecting customers to technology...", "Knowledge of banking laws and regulations...". Those are skills/abilities. So we could put them under Skills. But then Qualifications would be empty. Better to put Desired Qualifications under Qualifications, and maybe Skills under Skills with some overlapping? Could split: Qualifications = desired qualifications (experience, abilities). Skills = specific abilities like ability to analyze performance, exercise independent judgement, knowledge of banking laws, ability to lead teams influencing tech, etc. But that would duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Perhaps we combine Required and Desired Qualifications into one Qualifications section, and put Skills maybe not needed. But we need to follow the allowed headings; we can omit sections if no real content. So we could have: - About the role - Responsibilities - Qualifications (combining required and desired) - Benefits - Pay - Schedule We could also include Requirements if we want to separate required vs desired, but that would be thin? Not necessarily; we have decent content for both. But we have to avoid too many sections. Let's see: we have About the role, Responsibilities, Qualifications (maybe split into Required and Desired as sub-sections? Not allowed headings). We could keep Qualifications as a section containing both required and desired, using

  or

  . That would be substantive. Benefits: we have robust benefits, competitive compensation, programs for work-life balance, well-being. Also mention of being rewarded for investing in community, celebrated for authentic self, empowered to grow. That's benefits. Pay: we have competitive compensation mentioned; but we don't have specific salary numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation" and "robust benefits". So we can include Pay and Benefits sections with that content. However we need to avoid filler like "commensurate with experience". Not present. Schedule: we have ability to work schedule that includes Saturdays, ability to travel up to 50% of time. Also maybe mention of onboarding etc. So we can include Schedule. We also have Job Expectations: SAFE registration, loan originator requirements, credit report, no visa sponsorship, posting end date. Those could be placed under Requirements or Qualifications? They are expectations. Could be part of Requirements. But we already have Required Qualifications. We could add them under Requirements as additional bullet points. However we decided to combine required and desired into Qualifications. Maybe better to have Requirements section for mandatory items (required qualifications + job expectations). Qualifications section for desired qualifications. Skills maybe not needed. Let's think: The instruction says use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use all if we have content. We need to avoid empty headings. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: we have Required Qualifications (5+ years banking, 2+ years leadership) plus Job Expectations (schedule includes Saturdays, travel up to 50%, SAFE registration, loan originator requirements, credit report, no visa sponsorship, posting end date). That's substantive. - Qualifications: we have Desired Qualifications list (several bullet points). That's substantive. - Skills: maybe we could extract specific skill statements from Desired Qualifications that are more skill-oriented, but we already have Qualifications covering them. Could we create Skills section with some of those? Might be redundant but still substantive. However we risk thin sections if we split too much. Let's see if we can create a meaningful Skills section with items like "Ability to analyze performance, identify strengths and opportunities, and execute action plans", "Exercise independent judgement and critical thinking skills", "Knowledge of banking laws and regulations", "Ability to lead teams in influencing, educating, and connecting customers to technology". Those are skills. That would be a few items. Could be okay. But we must not invent or summarize away detail; we can just take those statements from Desired Qualifications and put them under Skills. Then Qualifications could contain the remaining desired qualifications that are more about experience/proven ability etc. However the Desired Qualifications list includes both experience and skills. We could split them. Let's list Desired Qualifications bullet points from posting: - Proven ability to hire, coach, and develop sales professionals and direct reports, fostering a culture of accountability, collaboration, adaptability, and high performance. - Demonstrated ability to lead a customer-focused sales