Branch Manager Hill Country District

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Use

for each section heading. Use

• for lists,

  for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting: It includes "Why Wells Fargo ..." intro, then "About This Role", then "In This Role You Will" (responsibilities), then "Required Qualifications:", "Desired Qualifications:", "Job Expectations:", then location list, posting end date, etc. Also includes "We Value Equal Opportunity" etc which is boilerplate to remove. Also includes "Drug and Alcohol Policy", "Wells Fargo Recruitment And Hiring Requirements", etc. Remove those. We need to include sections only if there is real specific content. We have content for: - About the role: from "About This Role" paragraph(s). That includes description of role, purpose, onboarding program, etc. - Responsibilities: from "In This Role You Will" bullet list (though it's a paragraph with sentences separated by periods). We can treat each sentence as a list item? The instruction: use

  • for any list of duties/requirements/benefits. The responsibilities are a series of statements; we can make them list items. - Requirements: maybe combine Required Qualifications and Desired Qualifications? The instruction has separate sections: Requirements, Qualifications, Skills. We need to decide mapping. Usually "Required Qualifications" and "Desired Qualifications" could go under Requirements or Qualifications. Since we have both, we could put Required Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe Skills under Skills (but we may not have explicit skills list). However we have many skill-like statements in Desired Qualifications; we could treat them as Skills. But we must not create sections with filler. We have content for each. Also we have Job Expectations: includes schedule (Saturdays), travel up to 50%, SAFE registration, loan originator requirements, credit report, no visa sponsorship. That includes schedule and maybe other expectations. We could put schedule info under Schedule section if present. The posting says "Ability to work a schedule that includes Saturdays." and "Ability to travel in assigned geography up to 50% of the time during the first 6 months". Travel is not schedule but maybe we could put under Schedule? But schedule section should only be created if posting actually states schedule info. It does mention schedule (Saturdays). So we can create a Schedule section with that bullet. Pay: Not mentioned. Benefits: Not mentioned explicitly (though earlier intro mentions robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being). That's in the introductory "Why Wells Fargo" paragraph. That is substantive content about benefits and compensation. So we could create Benefits section with that info (robust benefits, competitive compensation, programs for work-life balance, well-being, community investment, authentic self, growth). Also Pay: maybe not specific numbers, but we have "competitive compensation". The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation" and "robust benefits". So we can include Benefits and Pay sections? Pay: "competitive compensation" is a statement about pay. So we could include Pay section with that statement. However we need to avoid filler like "commensurate with experience". "competitive compensation" is not filler; it's a statement. So we can include Pay. But we also have "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." That's benefits and compensation. We could split: Benefits: robust benefits, programs for work-life balance and well-being, community investment, authentic self, growth. Pay: competitive compensation. We need to ensure we don't invent details. We can paraphrase but must preserve substance. It's okay to rephrase slightly. Now, we need to output only HTML fragment, no /, no markdown fences. Let's structure:

    About the role

    ... (combined paragraphs from About This Role)

    Responsibilities

    • 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.

    Requirements

    • 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

    Qualifications

    • 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.

    Skills

    Maybe we could treat the Desired Qualifications as Skills, but we already used them as Qualifications. The instruction includes Skills section separate. We could move some of those to Skills. However we have already used Desired Qualifications for Qualifications. We could instead put Required Qualifications under Requirements, Desired Qualifications under Skills, and leave Qualifications empty? But we need to include a section only if there is real specific content. We have content for both required and desired. We could make Requirements = Required Qualifications, Skills = Desired Qualifications, and omit Qualifications section. Or we could make Qualifications = Combined required+desired, and omit Skills. The instruction says prefer a few substantive sections over many thin ones. So better to have fewer sections. We could combine Required and Desired into a single Qualifications section. But we already have Requirements separate. The instruction includes Requirements, Qualifications, Skills as possible headings. We could use Requirements for the mandatory years/experience, Qualifications for the desired qualifications (skills). That seems reasonable: Requirements = mandatory experience; Qualifications = desired qualifications (which are more like skills). Then we might not need a separate Skills section. Let's do that. Thus:

    Requirements

    (5+ years, 2+ years leadership)

    Qualifications

    (list of desired qualifications)
    Now Benefits and Pay and Schedule. Benefits: from intro: "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." Also earlier: "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." So we can combine. Pay: "competitive compensation" already mentioned; but we might avoid duplication. Since we already used competitive compensation in Benefits, we could still have Pay section with that statement, but it's duplicate. Better to not duplicate. We could put Pay section with "competitive compensation" and Benefits section with the rest (robust benefits, programs for work-life balance, community investment, authentic self, growth). However the intro says robust benefits AND competitive compensation together. To avoid duplication, we could assign competitive compensation to Pay, and robust benefits + programs to Benefits. That seems fine. Schedule: "Ability to work a schedule that includes Saturdays." Also travel up to 50% maybe not schedule but could be under Schedule? Travel is not schedule but could be under Job Expectations. But we have no Job Expectations section; we could incorporate travel into Schedule? Might be misleading. Better to create a Schedule section only for the Saturday schedule. Travel could be mentioned under Responsibilities or maybe under a separate section like "Job Expectations" but we don't have that heading. The instruction only allows those headings. We could put travel under Responsibilities as a bullet? It's not a responsibility but an expectation. However we could add a bullet under Responsibilities: "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." That is an expectation but could be placed under Responsibilities as it's a job expectation. Might be okay. But we also have SAFE registration, loan originator requirements, credit report, no visa sponsorship. Those are also job expectations. Could be placed under Responsibilities as additional bullets, but they are not responsibilities. However the instruction says use
    • for any list of duties/requirements/benefits. Expectations could be considered requirements? Might be okay to put them under Requirements? But they are not qualifications. Might be better to create a separate section like "Job Expectations" but not allowed. So we could incorporate them under Requirements as additional items? Might be confusing. Alternatively, we could create a section named "Requirements" for mandatory qualifications, and put the expectations under that as well? Might be okay. But we need to preserve all substantive information. We must not omit the SAFE registration, loan originator requirements, credit report, no visa sponsorship, travel, Saturday schedule. We could create a section "Schedule" for Saturday schedule, and put travel, SAFE registration, loan originator requirements, credit report, visa sponsorship under Responsibilities? Or maybe under a new section "Job Expectations" but not allowed. The instruction only lists specific headings; we cannot invent others. So we must fit into allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus we need to allocate the expectations to either Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, or Schedule. - Schedule: Saturday schedule. - Pay: competitive compensation. - Benefits: robust benefits, programs for work-life balance, community investment, authentic self, growth. - Responsibilities: core duties. - Requirements: mandatory