Branch Manager Lakeside District
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not include Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes Pay Range: $37.50 - $67.31. Also includes schedule: Ability to work a schedule that includes Saturdays. Ability to travel up to 50% of time during first 6 months. So schedule info present. Benefits listed. So we need sections: About the role (maybe from "About this role" paragraph). Responsibilities (the "In this role you will:" bullet list). Requirements (maybe "Required Qualifications" and "Job Expectations"? Actually "Required Qualifications" is a list; "Desired Qualifications" also list; "Job Expectations" list. Could combine into Requirements and Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We need to decide what goes where.
- About the role: likely the paragraph after "About this role:" describing the opportunity, purpose, onboarding program, etc.
- Responsibilities: the bullet list starting "In this role you will:" (list of duties).
- Requirements: maybe the "Required Qualifications" and "Job Expectations"? Actually Job Expectations includes schedule, travel, SAFE registration, etc. Those are more like requirements. Could treat "Required Qualifications" as Requirements.
- Qualifications: maybe "Desired Qualifications" as Qualifications.
- Skills: maybe combine some skill-based items from Desired Qualifications? But we could also put skill items under Skills heading. However we need to avoid thin sections. Could merge Skills into Qualifications? But we need to follow headings list; we can omit sections if no real specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not enough distinct content. But we have skill-like items in Desired Qualifications: ability to hire, coach, develop, lead customer-focused sales culture, analyze performance, exercise independent judgement, manage across affluent segments, lead teams influencing customers to technology, knowledge of banking laws, etc. Those could be considered Skills. Could create Skills section with those bullet points.
- Benefits: list of benefits.
- Pay: the pay range.
- Schedule: schedule info (Saturdays, travel up to 50%).
We must not include filler like "commensurate with experience". Not present.
We must not repeat job title as heading. Not include Job ID etc.
We must remove boilerplate: EEO, drug policy, etc. Also remove "Posting End Date", "Reference Number". Also remove "Position May Not Be Available At All Locations:" list? That's location info; maybe we can keep as minor metadata? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location list could be considered minor metadata; we could drop it or put in a short p. Probably drop it to keep concise.
Also remove "Living the Well Life" etc? That's part of Why Wells Fargo intro; maybe we keep as part of About the role? The "Why Wells Fargo" section is generic marketing; could be considered boilerplate? It's not exactly boilerplate but it's promotional. Might be considered part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the Why Wells Fargo paragraph as part of About the role? It describes company culture, benefits, etc. Could be part of About the role. But we already have About the role section; we could incorporate that.
Better: About the role includes the introductory marketing paragraph plus the description of the role. We'll combine.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
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
Maybe also include Job Expectations items like SAFE registration, travel, schedule? Those could be under Requirements or Schedule. But schedule is separate. We'll put SAFE registration, travel up to 50%, credit report review, no visa sponsorship under Requirements? Might be better to put under Requirements as they are requirements. However we have separate Schedule heading for schedule specifics (Saturdays, travel). So we could put travel under Schedule. SAFE registration and credit check maybe under Requirements.
Let's decide:
Requirements: Required Qualifications (5+ years, 2+ years leadership). Also Job Expectations: SAFE registration required at time of employment, Loan Originators must meet LO/CFPB requirements, credit report may be reviewed, position not eligible for Visa sponsorship. Also maybe "Ability to work a schedule that includes Saturdays" and travel up to 50% - those go to Schedule.
Qualifications: Desired Qualifications list.
Skills: maybe we can omit Skills if we think content thin. But we have many skill items in Desired Qualifications; we could move them to Skills. However Desired Qualifications already includes skill-like items. Could treat Desired Qualifications as Qualifications, and Skills as maybe empty; better to omit Skills heading.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Now craft content.
About the role paragraph: combine Why Wells Fargo intro and About this role description.
Let's write:
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. A meaningful career is 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, with 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. 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 seems comprehensive.
Now Responsibilities: the bullet list after "In this role you will:".
List items:
- 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 + Job Expectations (excluding schedule). Let's list:
- 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
- SAFE registration is required at the time of employment (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 could also include "Ability to work a schedule that includes Saturdays" and travel up to 50% under Schedule.
Now Qualifications: Desired Qualifications list.
Items:
- 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: list from posting.
- 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 could combine some items but keep as list.
Now Pay: $37.50 - $67.31 base pay
for prose. Do not repeat job title as heading. Do not include Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes Pay Range: $37.50 - $67.31. Also includes schedule: Ability to work a schedule that includes Saturdays. Ability to travel up to 50% of time during first 6 months. So schedule info present. Benefits listed. So we need sections: About the role (maybe from "About this role" paragraph). Responsibilities (the "In this role you will:" bullet list). Requirements (maybe "Required Qualifications" and "Job Expectations"? Actually "Required Qualifications" is a list; "Desired Qualifications" also list; "Job Expectations" list. Could combine into Requirements and Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We need to decide what goes where. - About the role: likely the paragraph after "About this role:" describing the opportunity, purpose, onboarding program, etc. - Responsibilities: the bullet list starting "In this role you will:" (list of duties). - Requirements: maybe the "Required Qualifications" and "Job Expectations"? Actually Job Expectations includes schedule, travel, SAFE registration, etc. Those are more like requirements. Could treat "Required Qualifications" as Requirements. - Qualifications: maybe "Desired Qualifications" as Qualifications. - Skills: maybe combine some skill-based items from Desired Qualifications? But we could also put skill items under Skills heading. However we need to avoid thin sections. Could merge Skills into Qualifications? But we need to follow headings list; we can omit sections if no real specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not enough distinct content. But we have skill-like items in Desired Qualifications: ability to hire, coach, develop, lead customer-focused sales culture, analyze performance, exercise independent judgement, manage across affluent segments, lead teams influencing customers to technology, knowledge of banking laws, etc. Those could be considered Skills. Could create Skills section with those bullet points. - Benefits: list of benefits. - Pay: the pay range. - Schedule: schedule info (Saturdays, travel up to 50%). We must not include filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, drug policy, etc. Also remove "Posting End Date", "Reference Number". Also remove "Position May Not Be Available At All Locations:" list? That's location info; maybe we can keep as minor metadata? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location list could be considered minor metadata; we could drop it or put in a short p. Probably drop it to keep concise. Also remove "Living the Well Life" etc? That's part of Why Wells Fargo intro; maybe we keep as part of About the role? The "Why Wells Fargo" section is generic marketing; could be considered boilerplate? It's not exactly boilerplate but it's promotional. Might be considered part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the Why Wells Fargo paragraph as part of About the role? It describes company culture, benefits, etc. Could be part of About the role. But we already have About the role section; we could incorporate that. Better: About the role includes the introductory marketing paragraph plus the description of the role. We'll combine. Now produce HTML. Structure:
About the role
...
Responsibilities
- ... ...
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