Branch Manager East Bay Ridge District
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones.
We need to 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; likely we can drop as boilerplate? It's not about the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories but it's generic marketing fluff. Might be considered boilerplate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The generic description may be considered not substantive for the role? It's about company culture, but maybe we can keep as "About the role"? Actually there is a section "About This Role" later. The generic Wells Fargo description could be considered company overview, not role-specific. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should create sections based on content. The generic Wells Fargo description could go under "About the role"? But "About the role" heading is for role description, not company. However we could treat it as "About the role" includes both company and role? The posting includes "About This Role" heading. So we should use that content for About the role section.
Thus we need to extract:
- About This Role: description of role, purpose, onboarding, etc.
- In This Role You Will: list of duties/responsibilities.
- Required Qualifications: bullet list.
- Desired Qualifications: bullet list.
- Job Expectations: schedule, travel, SAFE registration, etc.
- Locations: list of addresses.
- Pay Range: $37.50 - $67.31.
- Benefits: list of benefits.
- Posting End Date: maybe minor metadata; could be dropped or placed in short
. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Posting End Date is minor metadata; we could include in a short
at end or drop. Probably drop as not substantive? It's date; maybe keep as short
.
- Also there is "We Value Equal Opportunity" etc. That's EEO boilerplate; remove.
- "Applicants With Disabilities", "Drug and Alcohol Policy", "Wells Fargo Recruitment And Hiring Requirements", "Reference Number" - these are boilerplate; remove.
Thus we need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which content maps to which heading.
- About the role: use "About This Role" paragraph(s). That includes description of role, onboarding program, etc.
- Responsibilities: use "In This Role You Will" list of duties.
- Requirements: maybe combine Required Qualifications and Job Expectations? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings as examples; we can decide to use them as needed. We have Required Qualifications (5+ years banking, 2+ years leadership). Desired Qualifications (list). Job Expectations (schedule, travel, SAFE registration, etc.) Could be considered Requirements or Skills? Perhaps we can put Required Qualifications under "Requirements", Desired Qualifications under "Qualifications", and Job Expectations under "Schedule" (since includes schedule, travel). But also Skills could be derived from desired qualifications (like ability to hire, coach, develop, etc.) However we should not invent sections; we should only create sections when posting has real, specific content for it. So we need to see if we have content for each heading.
We have content for:
- About the role: yes.
- Responsibilities: yes (In This Role You Will list).
- Requirements: we have Required Qualifications (specific). Could be placed under Requirements.
- Qualifications: we have Desired Qualifications (specific). Could be placed under Qualifications.
- Skills: we could maybe extract from Desired Qualifications some skill statements, but they are already qualifications. Could we treat Desired Qualifications as Skills? But we already have Qualifications heading; maybe we can put Desired Qualifications under Skills? However the instruction says prefer a few substantive sections over many thin ones. We could combine Required and Desired under one "Requirements" section? But we need to follow headings examples; not required to use all. We can choose to include only sections that have substantive content. So we could have: About the role, Responsibilities, Requirements (combining Required and Desired), Benefits, Pay, Schedule. That would be 6 sections. Or we could split Requirements and Qualifications.
We need to decide based on content: Required Qualifications are specific (5+ years banking, 2+ years leadership). Desired Qualifications are a list of abilities. Those could be considered "Qualifications". Skills could be derived from those but we don't have a separate explicit skills list. So maybe we skip Skills section.
Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Desired Qualifications), Benefits, Pay, Schedule (Job Expectations includes schedule, travel, SAFE registration). Also we might include Locations? Not a heading; could be placed under About the role or Responsibilities? Probably not needed; but we should preserve ALL substantive information. Locations are substantive; we need to include them somewhere. Could add a short
under About the role or maybe a separate section "Locations"? Not in the heading list; but we could incorporate into About the role as a paragraph. The instruction says use headings for those examples; but we can also have other headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed, but better to stick to those. However we need to preserve location info; we could put it in a
under About the role or Responsibilities. Probably under About the role as a note: "Locations include: ..." as a paragraph.
Similarly, Posting End Date could be a short
at end.
We must not include boilerplate like EEO, etc.
Now we need to format lists.
For Responsibilities: we have a paragraph "In This Role You Will Provide strong, inclusive leadership..." It's a run-on sentence with multiple duties separated by periods? Actually it's a long sentence with multiple clauses separated by periods? Let's copy:
"In This Role You Will 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."
We need to split into list items. Each sentence seems to be a duty. We'll create
- for each.
Similarly for 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, education2+ years of leadership experience". There's a missing space before "2+ years". We'll treat as two bullet points? Actually it's a single qualification with two parts: experience requirement and leadership experience. Could be one bullet: "5+ years of banking, financial services, or Branch Network experience, or equivalent demonstrated through work experience, training, military experience, or education; and 2+ years of leadership experience." We'll keep as one bullet.
Desired Qualifications: list of bullet points each starting with ability etc. We'll create
- for each.
Benefits: list after "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.
We'll create
- for each.
Pay: we have "$37.50 - $67.31". Also note "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." We'll include that as prose under Pay heading.
Schedule: Job Expectations includes schedule, travel, SAFE registration, etc. We'll extract schedule specifics: "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." Those are expectations; we can put under Schedule heading (maybe also include
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to 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; likely we can drop as boilerplate? It's not about the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories but it's generic marketing fluff. Might be considered boilerplate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The generic description may be considered not substantive for the role? It's about company culture, but maybe we can keep as "About the role"? Actually there is a section "About This Role" later. The generic Wells Fargo description could be considered company overview, not role-specific. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should create sections based on content. The generic Wells Fargo description could go under "About the role"? But "About the role" heading is for role description, not company. However we could treat it as "About the role" includes both company and role? The posting includes "About This Role" heading. So we should use that content for About the role section. Thus we need to extract: - About This Role: description of role, purpose, onboarding, etc. - In This Role You Will: list of duties/responsibilities. - Required Qualifications: bullet list. - Desired Qualifications: bullet list. - Job Expectations: schedule, travel, SAFE registration, etc. - Locations: list of addresses. - Pay Range: $37.50 - $67.31. - Benefits: list of benefits. - Posting End Date: maybe minor metadata; could be dropped or placed in short
. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Posting End Date is minor metadata; we could include in a short
at end or drop. Probably drop as not substantive? It's date; maybe keep as short
. - Also there is "We Value Equal Opportunity" etc. That's EEO boilerplate; remove. - "Applicants With Disabilities", "Drug and Alcohol Policy", "Wells Fargo Recruitment And Hiring Requirements", "Reference Number" - these are boilerplate; remove. Thus we need to produce sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content maps to which heading. - About the role: use "About This Role" paragraph(s). That includes description of role, onboarding program, etc. - Responsibilities: use "In This Role You Will" list of duties. - Requirements: maybe combine Required Qualifications and Job Expectations? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings as examples; we can decide to use them as needed. We have Required Qualifications (5+ years banking, 2+ years leadership). Desired Qualifications (list). Job Expectations (schedule, travel, SAFE registration, etc.) Could be considered Requirements or Skills? Perhaps we can put Required Qualifications under "Requirements", Desired Qualifications under "Qualifications", and Job Expectations under "Schedule" (since includes schedule, travel). But also Skills could be derived from desired qualifications (like ability to hire, coach, develop, etc.) However we should not invent sections; we should only create sections when posting has real, specific content for it. So we need to see if we have content for each heading. We have content for: - About the role: yes. - Responsibilities: yes (In This Role You Will list). - Requirements: we have Required Qualifications (specific). Could be placed under Requirements. - Qualifications: we have Desired Qualifications (specific). Could be placed under Qualifications. - Skills: we could maybe extract from Desired Qualifications some skill statements, but they are already qualifications. Could we treat Desired Qualifications as Skills? But we already have Qualifications heading; maybe we can put Desired Qualifications under Skills? However the instruction says prefer a few substantive sections over many thin ones. We could combine Required and Desired under one "Requirements" section? But we need to follow headings examples; not required to use all. We can choose to include only sections that have substantive content. So we could have: About the role, Responsibilities, Requirements (combining Required and Desired), Benefits, Pay, Schedule. That would be 6 sections. Or we could split Requirements and Qualifications. We need to decide based on content: Required Qualifications are specific (5+ years banking, 2+ years leadership). Desired Qualifications are a list of abilities. Those could be considered "Qualifications". Skills could be derived from those but we don't have a separate explicit skills list. So maybe we skip Skills section. Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Desired Qualifications), Benefits, Pay, Schedule (Job Expectations includes schedule, travel, SAFE registration). Also we might include Locations? Not a heading; could be placed under About the role or Responsibilities? Probably not needed; but we should preserve ALL substantive information. Locations are substantive; we need to include them somewhere. Could add a short
under About the role or maybe a separate section "Locations"? Not in the heading list; but we could incorporate into About the role as a paragraph. The instruction says use headings for those examples; but we can also have other headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could also use other headings if needed, but better to stick to those. However we need to preserve location info; we could put it in a
under About the role or Responsibilities. Probably under About the role as a note: "Locations include: ..." as a paragraph. Similarly, Posting End Date could be a short
at end. We must not include boilerplate like EEO, etc. Now we need to format lists. For Responsibilities: we have a paragraph "In This Role You Will Provide strong, inclusive leadership..." It's a run-on sentence with multiple duties separated by periods? Actually it's a long sentence with multiple clauses separated by periods? Let's copy: "In This Role You Will 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." We need to split into list items. Each sentence seems to be a duty. We'll create
- for each.
Similarly for 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, education2+ years of leadership experience". There's a missing space before "2+ years". We'll treat as two bullet points? Actually it's a single qualification with two parts: experience requirement and leadership experience. Could be one bullet: "5+ years of banking, financial services, or Branch Network experience, or equivalent demonstrated through work experience, training, military experience, or education; and 2+ years of leadership experience." We'll keep as one bullet.
Desired Qualifications: list of bullet points each starting with ability etc. We'll create
- for each.
Benefits: list after "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.
We'll create
- for each. Pay: we have "$37.50 - $67.31". Also note "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." We'll include that as prose under Pay heading. Schedule: Job Expectations includes schedule, travel, SAFE registration, etc. We'll extract schedule specifics: "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." Those are expectations; we can put under Schedule heading (maybe also include
- for each.
Benefits: list after "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.
We'll create