Branch Manager Metro East Twin Cities MN
Wells Fargo · Saint Paul Church, MN · 1 mo ago
Business Development$40.87–$62.5/hrFull-time
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 as heading. No Job ID etc. Remove boilerplate.
We need to extract content.
Let's parse the posting.
First part: "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 generic company description; maybe we can put under "About the role"? Actually "About this role:" heading appears later. The "Why Wells Fargo" is more about company; but we can include as part of About the role? 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. We need to include only those sections that have real specific content.
We have "About this role:" content after that. So we can put that under About the role.
Then responsibilities: "In this role you will:" list bullet points. Those are responsibilities.
Then Required Qualifications and Desired Qualifications: we can combine into Requirements? The instruction: Use sections Requirements, Qualifications, Skills. Possibly Requirements = Required Qualifications, Qualifications = Desired Qualifications? Or we can treat Required Qualifications as Requirements, Desired Qualifications as Qualifications. Skills maybe from Desired Qualifications? But we can also put Skills separate if there is explicit skills list. The Desired Qualifications includes abilities like "Proven ability to hire, coach, and develop sales professionals..." which are skills. Could treat as Skills.
But we need to avoid thin sections. Let's decide:
- About the role: include the "About this role:" paragraph.
- Responsibilities: the bullet list after "In this role you will:".
- Requirements: Required Qualifications (5+ years experience, 2+ years leadership). Could also include Job Expectations? Those are schedule/travel etc. Might go under Schedule.
- Qualifications: Desired Qualifications (list of abilities). Could be considered Qualifications.
- Skills: maybe we can extract specific skill statements from Desired Qualifications that are skill-like: "Proven ability to hire, coach, and develop sales professionals...", "Demonstrated ability to lead a customer-focused sales culture...", "Ability to analyze performance...", "Exercise independent judgement...", "Demonstrated success managing and coaching across affluent...", "Ability to lead teams in influencing, educating, and connecting customers to technology...", "Knowledge of banking laws and regulations...". Those could be Skills.
But we might combine Qualifications and Skills if they overlap. However instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section? But they gave separate headings as examples; we can choose to include only those with substantive content.
We have specific content for Pay: "$40.87 - $62.50" plus note about base pay range, incentives.
We have Benefits: list of benefits.
We have 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." Also maybe mention training interim nonexempt role? But schedule section should include schedule specifics.
We also have "Job Expectations" includes SAFE registration, loan originator requirements, credit report, visa sponsorship not eligible. Those are not schedule but maybe could be under Requirements? But they are more like eligibility/requirements. Could be part of Requirements.
We need to preserve all substantive information; do not invent or summarize away detail. So we must include all details.
Thus we need to include sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications + Job Expectations?), Qualifications (Desired Qualifications), Skills (maybe we can omit if we think it's thin), Benefits, Pay, Schedule.
But we need to avoid thin sections like "Skills" if it's just a repeat of Qualifications. Perhaps we can merge Desired Qualifications into Skills and call it Skills, and omit Qualifications. Or we can have Qualifications = Desired Qualifications, and Skills = maybe we can extract specific skill statements but that would be similar.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (includes Required Qualifications + Job Expectations), Qualifications (Desired Qualifications), Benefits, Pay, Schedule. That's 6 sections, each substantive.
We'll not include Skills separately.
Now we need to format.
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. We need to include only those sections that have real specific content.
We have "About this role:" content after that. So we can put that under About the role.
Then responsibilities: "In this role you will:" list bullet points. Those are responsibilities.
Then Required Qualifications and Desired Qualifications: we can combine into Requirements? The instruction: Use sections Requirements, Qualifications, Skills. Possibly Requirements = Required Qualifications, Qualifications = Desired Qualifications? Or we can treat Required Qualifications as Requirements, Desired Qualifications as Qualifications. Skills maybe from Desired Qualifications? But we can also put Skills separate if there is explicit skills list. The Desired Qualifications includes abilities like "Proven ability to hire, coach, and develop sales professionals..." which are skills. Could treat as Skills.
But we need to avoid thin sections. Let's decide:
- About the role: include the "About this role:" paragraph.
- Responsibilities: the bullet list after "In this role you will:".
- Requirements: Required Qualifications (5+ years experience, 2+ years leadership). Could also include Job Expectations? Those are schedule/travel etc. Might go under Schedule.
- Qualifications: Desired Qualifications (list of abilities). Could be considered Qualifications.
- Skills: maybe we can extract specific skill statements from Desired Qualifications that are skill-like: "Proven ability to hire, coach, and develop sales professionals...", "Demonstrated ability to lead a customer-focused sales culture...", "Ability to analyze performance...", "Exercise independent judgement...", "Demonstrated success managing and coaching across affluent...", "Ability to lead teams in influencing, educating, and connecting customers to technology...", "Knowledge of banking laws and regulations...". Those could be Skills.
But we might combine Qualifications and Skills if they overlap. However instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section? But they gave separate headings as examples; we can choose to include only those with substantive content.
We have specific content for Pay: "$40.87 - $62.50" plus note about base pay range, incentives.
We have Benefits: list of benefits.
We have 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." Also maybe mention training interim nonexempt role? But schedule section should include schedule specifics.
We also have "Job Expectations" includes SAFE registration, loan originator requirements, credit report, visa sponsorship not eligible. Those are not schedule but maybe could be under Requirements? But they are more like eligibility/requirements. Could be part of Requirements.
We need to preserve all substantive information; do not invent or summarize away detail. So we must include all details.
Thus we need to include sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications + Job Expectations?), Qualifications (Desired Qualifications), Skills (maybe we can omit if we think it's thin), Benefits, Pay, Schedule.
But we need to avoid thin sections like "Skills" if it's just a repeat of Qualifications. Perhaps we can merge Desired Qualifications into Skills and call it Skills, and omit Qualifications. Or we can have Qualifications = Desired Qualifications, and Skills = maybe we can extract specific skill statements but that would be similar.
Given instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (includes Required Qualifications + Job Expectations), Qualifications (Desired Qualifications), Benefits, Pay, Schedule. That's 6 sections, each substantive.
We'll not include Skills separately.
Now we need to format.
Use for each section heading.
Under each heading, we put content: For prose, use
. For lists, use
- . We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information: That includes the list of posting locations? That's under "Posting Locations:" with many addresses. Should we include that? It's substantive info about where the job is located. Should we include under maybe About the role? Or maybe a separate section? Not in the list of headings; but we could include it under About the role as a paragraph. The instruction says use headings only for those examples; but we can still include other info as paragraphs under those headings. So we can add a paragraph about locations under About the role or maybe under Responsibilities? Better to put under About the role after the description. We must not include boilerplate like EEO, scam warning, etc. Remove those. Also remove "Posting End Date: 4 Oct 2026 * Job posting may come down early due to volume of applicants." That's maybe not boilerplate but it's a date; could be considered metadata. Might be okay to keep? It's not in the heading list; we could put it under About the role as a small note. But it's not essential? It's substantive info about when posting ends. Might keep. But we need to remove duplicated lines. Let's extract sections. **About the role**: - The "Why Wells Fargo" paragraph (company description) maybe part of About the role. - The "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? Actually: "Employees currently serving in a Branch Manager role at Wells Fargo are not required to complete the program." So include that. We can combine the Why Wells Fargo and About this role into About the role section. Also include Posting Locations list. Also maybe include Posting End Date. **Responsibilities**: The bullet list after "In this role you will:" includes many bullet points. 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" and "2+ years of leadership experience" - Job Expectations: "Ability to work a schedule that includes Saturdays." (but schedule we will put under Schedule). Also "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." (Schedule). Also "SAFE registration is required at the time of employment and Wells Fargo will initiate the process after your start date." Also "Loan Originators must meet LO/CFPB requirements and comply with Wells Fargo policies, including standards related to financial responsibility, character, fitness, and criminal background." Also "A credit report may be reviewed (credit score not included) and additional ongoing screening may apply." Also "This position is not eligible for Visa sponsorship." We could keep schedule items under Schedule, and other expectations under Requirements. Thus Requirements: Required Qualifications + SAFE registration + Loan Originator requirements + credit report + visa sponsorship not eligible. **Qualifications**: Desired Qualifications list: bullet points. We'll put each as
- .
**Benefits**:
List under "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then bullet 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.
**Pay**:
Paragraph: "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. $40.87 - $62.50"
**Schedule**:
Paragraph: "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 mention that while in training, position is interim, nonexempt role. That's more about role nature; could be under About the role or Responsibilities? But we already have that in About the role maybe. We'll keep it there.
Now we need to output only HTML fragment, no markdown.
Let's craft.
We'll start with
About the role
then...
possibly multiple paragraphs. We need to ensure we don't duplicate content. Let's write About the role paragraph(s): First paragraph: Why Wells Fargo description. Second paragraph: About this role description. Third paragraph: Posting Locations list (maybe as- ).