Branch Manager Salt Lake South District

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. We need to parse the posting. Key sections: - Intro about Wells Fargo (company description) maybe "About the role"? Actually "About This Role" is a heading. We'll use

About the role

and put description. - Responsibilities: The "In This Role You Will" bullet list. - Required Qualifications: bullet list. - Desired Qualifications: bullet list. - Job Expectations: schedule, travel, SAFE registration, etc. Could be under Schedule or maybe separate. - Benefits: The posting mentions "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." Also "You'll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow." Also mention "recognized for it - Wells Fargo once again ranked in the top five on the 2026 LinkedIn Top Companies list". That's more about company but could be Benefits. However we need actual benefits specifics: robust benefits, competitive compensation, programs for work-life balance, community investment reward, authenticity, growth empowerment. We'll include those. - Pay: Not explicitly stated; only "competitive compensation" but no numbers. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation" but not specific numbers. Is that enough? It says "competitive compensation" is a statement about pay. Might be considered stating pay. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive compensation" is vague but still a statement. Might be okay to include Pay section with that phrase. But better to avoid if not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive compensation". So we can include Pay with that phrase. - Schedule: The posting mentions "Ability to work a schedule that includes Saturdays." Also travel up to 50% etc. That's schedule info. So we can include Schedule section. - Benefits: we have robust benefits etc. - Skills: maybe we can combine desired qualifications as Skills? But we have separate sections for Qualifications and Skills. The instruction: 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. Likely: - About the role: company description and role overview. - Responsibilities: the bullet list under "In This Role You Will". - Requirements: maybe "Required Qualifications". - Qualifications: maybe "Desired Qualifications"? Or we could treat Required as Requirements and Desired as Qualifications. But they listed both Required Qualifications and Desired Qualifications. Could map Required Qualifications to Requirements, Desired Qualifications to Qualifications. - Skills: maybe we could extract skill statements from desired qualifications? But we already used desired as Qualifications. Could leave Skills empty or omit. Better to omit Skills if no specific skill list beyond qualifications. - Benefits: robust benefits etc. - Pay: competitive compensation. - Schedule: ability to work schedule includes Saturdays, travel up to 50% etc. We must not include boilerplate like EEO, etc. We must preserve all substantive information: location list, posting end date? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location list maybe minor metadata? It's substantive? Might be considered location info. Should we keep? It's location of possible branches. Could be considered minor metadata but still substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep location list. Where to put? Could be a short

under About the role or maybe a separate section? There's no heading for location. Could just include as a paragraph after About the role. Posting End Date: also minor metadata; could be a short

. We must not include duplicated lines. Now craft HTML. Structure:

About the role

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.

Then maybe a paragraph for location list and posting date.

Locations: 1985 E 7000 S, Salt Lake City, UT 84121; 7169 S Bingham Junction Blvd Ste 10, Midvale, UT 84047; 1750 W 12600 S, Riverton, UT 84065; 9311 S 2000 S, Sandy, UT 84093; 10010 S State St, Sandy, UT 84070; 2640 W 9000 S, West Jordan, UT 84088; 3889 W Campus View Drive, West Jordan, UT 84084; 5474 W Daybreak Pkwy Ste G100, South Jordan, UT 84009; 6099 S State St, Murray, UT 84107. Posting end date: 29 Sep 2026 (may come down early due to volume of applicants).

Now Responsibilities:

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.

Now Requirements (Required Qualifications):

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

Now Qualifications (Desired Qualifications):

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.

Now Benefits:

Benefits

• Robust benefits
• Competitive compensation
• Programs designed to help you find work-life balance and well-being
• Rewards for investing in your community
• Recognition for being your authentic self
• Empowerment to grow
• Recognized as a top five workplace on the 2026 LinkedIn Top Companies list for career growth
. Now Pay: we already have competitive compensation in Benefits; but Pay section maybe redundant. However we could still include Pay with "Competitive compensation". But we already have that in Benefits. Might be duplication. Better to not duplicate. Since Benefits already includes competitive compensation, we could omit Pay section. But the instruction: include a section ONLY when posting has real, specific content for it. Pay content is "competitive compensation". That's specific enough. But we already used it in Benefits. Could we keep Pay separate with just that phrase? Might be okay but could be seen as duplication. I'd rather keep Pay separate with that phrase, and Benefits without compensation phrase. Let's adjust. Benefits: robust benefits, programs for work-life balance, community investment reward, authenticity celebration, growth empowerment, top five workplace recognition. Pay: competitive compensation. Schedule:

Schedule

• 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.
We might also include SAFE registration etc under Job Expectations but not a heading. Could be placed under Schedule or maybe a separate section like "Expectations". But we have no heading for Expectations. Could fold into Schedule or maybe a short paragraph under About the role? Better to add a section "Expectations"? Not in allowed headings list. The allowed headings list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Expectations. So we must incorporate that info elsewhere, maybe under Schedule or Responsibilities? The SAFE registration and loan originator requirements are not schedule. Could be under Requirements? Might be considered a qualification? It's a job expectation. Could be placed under Requirements as additional bullet. But the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can only use those headings. We can still have other content under those headings. So we can add SAFE registration etc under Requirements or Qualifications. Probably under Requirements