Branch Manager, Triangle Southwest 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. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Intro: "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 about company, could be "About the role"? Actually "About this role:" heading appears later. The intro is more about company, but we can put under "About the role" maybe? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include if posting has real specific content. We need to extract content for each. Let's parse: - About the role: The section "About this role:" includes description: "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 substantive. - Responsibilities: The bullet list starting "In this role you will:" includes many responsibilities. We'll list them as

• . - Required Qualifications: "Required Qualifications:" includes bullet points: "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" and "2+ years of leadership experience". That's required. - Desired Qualifications: list after "Desired Qualifications:" includes many items. Those could go under Qualifications or Skills? The instruction: we have sections Requirements, Qualifications, Skills. We need to decide where to put what. Typically "Required Qualifications" and "Desired Qualifications" could go under Qualifications. "Skills" could be separate if there are skill-specific items. But we can combine desired qualifications under Qualifications as well. However we need to avoid filler. We'll include Qualifications section with both required and desired? Might be better to split: Requirements (maybe required qualifications) and Qualifications (desired). But the instruction says use headings like Requirements, Qualifications, Skills. So we can put required qualifications under Requirements, desired qualifications under Qualifications, and maybe skills under Skills if there are skill-specific items. However many desired qualifications are skill-like. We could put them under Skills. Let's extract: 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 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. Job Expectations (maybe under Requirements or Skills?): - 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. - Posting End Date: 11 Oct 2026 *Job posting may come down early due to volume of applicants. We should not include posting end date? It's metadata but maybe minor; we could drop or put in a short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short paragraph with posting end date and note about early removal. But maybe better to drop as it's not substantive for role. However it's still info. I'd include a short p: "

  Posting end date: 11 Oct 2026 (may be removed early due to high applicant volume).

  " That's minor metadata. Now Benefits: The posting mentions robust benefits, competitive compensation, programs for work-life balance, etc. In the intro: "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." That's benefits info. Also later maybe not explicit benefits list. So we can include Benefits section with that description. Pay: Not explicitly stated; only "competitive compensation" but no numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have robust benefits statement, so we can include Benefits. Pay: we have "competitive compensation" but not specific; that's vague. Should we include Pay? The instruction says never create Pay section unless posting actually states them. "competitive compensation" is a statement but not specific numbers. Might be considered stating compensation exists but not details. I'd avoid Pay section because it's not specific. Similarly Schedule: we have ability to work schedule that includes Saturdays, travel up to 50% etc. That's schedule info. So we can include Schedule section with those details. Skills: Could include some of the desired qualifications that are skill-based. But we already have Qualifications (desired). Might be redundant. Perhaps better: Requirements = required qualifications; Qualifications = desired qualifications; Skills = maybe we can extract skill-specific items like "Ability to analyze performance, identify strengths and opportunities, and execute action plans", "Exercise independent judgement and critical thinking skills", "Ability to lead teams in influencing, educating, and connecting customers to technology", "Knowledge of banking laws and regulations". Those are skills. But we already have them in desired qualifications. To avoid duplication, we could put desired qualifications under Qualifications and maybe not have Skills. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section that includes both required and desired? But we have separate headings for Requirements and Qualifications. Let's decide: - Requirements: required qualifications (5+ years, 2+ years leadership) - Qualifications: desired qualifications list (the bullet list) - Skills: maybe we can extract specific skill items like "Ability to work a schedule that includes Saturdays", "Ability to travel...", "SAFE registration required", etc. But those are more job expectations. Could go under Requirements or a separate section like Job Expectations but not in allowed headings. So maybe we put those under Requirements as well? But we already used Requirements for required qualifications. Could expand Requirements to include both required qualifications and job expectations (schedule, travel, SAFE, etc). That would be okay. Thus: Sections: - About the role (intro + role description) - Responsibilities (the "In this role you will:" list) - Requirements (required qualifications + job expectations: schedule, travel, SAFE, LO/CFPB, credit report, visa sponsorship, posting end date note) - Qualifications (desired qualifications list) - Benefits (robust benefits, competitive compensation, work-life balance programs) - (Pay omitted) - (Schedule omitted because included in Requirements) - Skills omitted (maybe not needed) We must not create empty sections. So we output only those with content. Now format: Use

  for each section heading. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. Let's craft. About the role: combine the introductory paragraph about Wells Fargo and the "About this role:" description. Might be two paragraphs. We'll put as

    for each. Responsibilities: list each bullet after "In this role you will:" as

  • . Requirements: list required qualifications as
  • items, plus job expectations as
  • items maybe separate? Could combine all as list. But we need to keep meaning. We'll make a list. Qualifications: list desired qualifications as
  • . Benefits: prose about robust benefits, competitive compensation, programs for work-life balance and well-being. Could be a

    . Now ensure we don't repeat job title. Not include "Branch Manager" as heading; it's fine in text. Now produce HTML. Let's draft. 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