Branch Manager Southern Westchester District

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, remove boilerplate: "Why Wells Fargo Are you looking for more? Find it here." etc. Also remove EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. We need to keep substantive info: About This Role, In This Role (responsibilities), Required Qualifications, Desired Qualifications, Job Expectations (schedule, travel, SAFE registration, etc.), Benefits, Pay Range, Locations (maybe not needed as a section; but location info could be part of something else? Not required heading). Also maybe "About This Role" is a section heading. We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include. - About the role: we have "About This Role" paragraph. So include

  About the role

  with that prose. - Responsibilities: we have "In This Role You Will" bullet list of duties. So include

  Responsibilities

  with
  • items. - Requirements: maybe combine Required Qualifications and Desired Qualifications? The instruction says use headings Requirements, Qualifications, Skills. We need to decide. Could have Requirements for required qualifications, Qualifications for desired qualifications, Skills maybe for skill-based items? But we can also combine. However we must not create empty sections. We have both required and desired qualifications. So we can have:

    Requirements

    for Required Qualifications (5+ years experience, 2+ years leadership). Use
    • .

      Qualifications

      for Desired Qualifications list. Skills: maybe we can extract skill items from desired qualifications? But we already have Qualifications section; maybe we can skip Skills if no distinct skill list. However we could treat some items as skills: e.g., "Ability to analyze performance...", "Exercise independent judgement...", etc. Those are abilities/skills. But we already have them in Desired Qualifications. Could still create Skills section with those items. But we must not create thin sections; better to have a few substantive sections. Could combine Desired Qualifications into Qualifications and maybe Skills not needed. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require all; only include when posting has real specific content. So we can include Requirements, Qualifications, Benefits, Pay, Schedule. Possibly also Skills if we have distinct skill list. Let's extract content. About This Role paragraph: "Wells Fargo is seeking accomplished, people-focused leaders interested in a Branch Manager career within the National Branch Network. This opportunity is designed for experienced managers who bring a strong foundation in branch leadership and are looking to apply their expertise within the Wells Fargo environment. As a Branch Manager, you will serve as the sales leader of the branch, accountable for acquiring, deepening and retaining customer relationships to drive consistent growth in primary checking, deposits, lending, credit cards and investments through disciplined execution, strong coaching, and effective performance management. You will lead, coach, and develop a team to consistently execute behaviors and improve banker productivity. You will foster an engaged, accountable culture focused on uncovering customer financial needs and recommending Wells Fargo solutions that deepen relationships and drive long-term value. You will balance growth objectives with strong operational risk management to protect customers, employees, and the company. Your onboarding starts with participation in the Branch Manager Readiness Program which is intended to offer a structured and supportive transition into leadership at Wells Fargo. Participants gain hands-on experience through guidance, mentorship, job shadowing, and practical learning opportunities in day-to-day branch operations. The program provides foundational knowledge, real-world practice, and leadership readiness needed to effectively lead a team and make an impact from day one. Successful completion of the Branch Manager Readiness program is required to transition into a Branch Manager position. Branch assignment is based on business need and branch availability at the time of placement. While in training, this position is an interim, nonexempt role. Employees currently serving in a Branch Manager role at Wells Fargo are not required to complete the program." That's the about role. Responsibilities (In This Role You Will) list: - 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'll put each as
    • . Requirements (Required Qualifications): - 5+ years of banking, financial services, or Branch Network experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education - 2+ years of leadership experience We'll list as
      • . Qualifications (Desired Qualifications) list: - 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 culture, driving measurable growth through coaching, accountability, disciplined execution, and taking ownership of performance outcomes, talent decisions, and risk management. - Ability to analyze performance, identify strengths and opportunities, and execute action plans that enable the team to achieve business objectives. - Exercise independent judgement and critical thinking skills to manage time, prioritize, and delegate tasks in a complex, fast-paced environment. - Demonstrated success managing and coaching across affluent, high net worth, and business customer segments by identifying complex financial needs and building strong relationships with customers, internal partners, and community stakeholders. - Ability to lead teams in influencing, educating, and connecting customers to technology, articulating the value of digital banking solutions to enhance customer experience. - Knowledge of banking laws and regulations, including compliance controls, operational risk management, and loss prevention, with the ability to model and reinforce behaviors that protect customers, employees, and the company. We'll list as
        • . Skills: Could we extract skill-specific items? The desired qualifications already cover skills. Might be redundant to create Skills section. But we could still create Skills section with items like "Ability to analyze performance...", "Exercise independent judgement...", etc. However that would split the desired qualifications. Better to keep Qualifications section and omit Skills. Benefits: list: - Health benefits - 401(k) Plan - Paid time off - Disability benefits - Life insurance, critical illness insurance, and accident insurance - Parental leave - Critical caregiving leave - Discounts and savings - Commuter benefits - Tuition reimbursement - Scholarships for dependent children - Adoption reimbursement We'll list as
          • . Pay: we have Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities. $37.50 - $67.31 We need to include Pay section with that info. Use

            for prose. Could also include the range as part of

            . Not a list. Schedule: we have Job Expectations: Ability to work a schedule that includes Saturdays. Ability to travel in assigned geography up to 50% of the time during the first 6 months (and prior to or up until placement in a specific branch), depending on location. SAFE registration is required at the time of employment and Wells Fargo will initiate the process after your start date. Loan Originators must meet LO/CFPB requirements and comply with Wells Fargo policies, including standards related to financial responsibility, character, fitness, and criminal background. A credit report may be reviewed (credit score not included) and additional ongoing screening may apply. This position is not eligible for Visa sponsorship. We need Schedule section: includes schedule (Saturdays) and maybe travel? Travel could be separate but we only have Schedule heading. Could include schedule and travel under Schedule? The instruction says use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So Schedule likely for schedule info. Travel maybe not a separate heading; could be included in Schedule as part of expectations. We'll include schedule and travel info in Schedule section. We also have Locations list; but no heading for Locations. Could drop or include as part of something else? Not required. We'll drop location list as not under any heading; but we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop location list entirely; we need to include it somewhere. Since there is no heading for Locations, we could include it under a generic section? But we must not create a heading unless there is real specific content for it. We could add a

            Locations

            even though not in the example list? 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; we could still use Locations heading if we want. However the instruction says "Use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; but not strictly forbidden to add others? It says use

            for section headings (e.g. ...). It doesn't say you cannot use other headings, but to follow the pattern. Safer to stick to those headings only. However we must preserve location info. Could we incorporate location info into another section like About the role or Responsibilities? Not appropriate. Could we add a

            after Benefits or Pay with location list? That would preserve info without a heading. That seems acceptable: we can include a

            containing the locations list (maybe as a comma-separated list). The instruction says use

            • for any list of duties/requirements/benefits, and

              for prose. Locations is a list; we could treat as a list and use

              • . But we need a heading? Not required; we could just put a
                • list without a heading? The instruction says use

                  for section headings (e.g...). It doesn't say every list must have a heading, but typical structure would have heading. However to preserve info, we could add a

                  Locations

                  even if not in examples; but risk violating instruction. The instruction says "Use

                  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples,