Personal Banker-Universal Branch Format Madison & 55th St.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have those headings only if content exists. We need to map content: About the role: description of role (the paragraph after "About this role:"). Responsibilities: the list under "In this role you will:" (the bullet points). Also maybe some duties from Job Expectations? But those are more expectations; could be part of Responsibilities or Requirements. We'll keep responsibilities as that list. Requirements: maybe the "Required Qualifications:" (6+ months experience). Also maybe "Job Expectations" includes schedule etc. But schedule is separate section. Qualifications: maybe "Desired Qualifications:" (the list). Could also be considered Requirements vs Qualifications. We'll treat Required Qualifications as Requirements, Desired Qualifications as Qualifications. Skills: maybe we can extract skills from desired qualifications list (comfort with digital tools, ability to identify needs, collaborate, follow policies). Could be a Skills section. Benefits: the list under Benefits. Pay: the pay range. Schedule: the ability to work schedule that will include Saturdays (from Job Expectations). Also maybe mention flexing between cash handling etc. But schedule is about Saturday work. We must not create sections with filler like "commensurate with experience". Avoid. We must not include boilerplate like EEO, drug policy, etc. We must not include Job ID/reference number. We must not include navigation etc. We must preserve all substantive information: need to include location, SAFE registration required, loan originator requirements, credit report, not eligible for visa sponsorship, etc. Where to put those? They are part of Job Expectations maybe. Could be part of Requirements or Qualifications? They are expectations/requirements. Could be placed under Requirements (maybe as additional requirements). But we already have Required Qualifications. Could add more under Requirements. We need to decide structure: maybe we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to fill each with appropriate content. Let's extract content: About the role paragraph: "Wells Fargo is seeking an Associate Personal Banker (SAFE) to join our National Branch. In this frontline role, you will build relationships with customers by supporting everyday banking needs through in‑branch interactions, scheduled conversations, and proactive outreach. You will learn about customers’ goals and connect them to the right banking products, services, and digital tools to help them manage their finances with confidence. You will support account openings, service requests, and credit applications while working closely with branch teammates to deliver a consistent, high-quality customer experience. Success is driven by strong relationship building, sound judgment, and the ability to balance service with growth. As a member of a leading financial institution, this role provides a strong foundation for long-term career growth and mobility, supported by Wells Fargo’s training and coaching." That's the About the role. Responsibilities list (from "In this role you will:"): - Build lasting customer relationships through proactive, meaningful conversations that support financial well-being and deepen engagement - Lead discovery-driven conversations to understand customer needs and connect them with relevant banking products, services, and solutions - Drive branch growth by identifying opportunities, promoting solutions, and making appropriate referrals to meet customer and business goals - Support everyday banking needs, including new account openings, service requests, and credit applications - Perform cash handling and teller line activities, accurately processing transactions while maintaining compliance and operational standards - Demonstrate comfort using and adopting digital tools and technologies to enhance the customer experience and support evolving banking needs - Deliver accurate, compliant service while exercising sound judgement within defined risk controls - Collaborate with branch teammates to coordinate seamless handoffs to licensed bankers or other specialists, ensuring customers are connected to the right expertise That's responsibilities. Required Qualifications: "6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education" Desired Qualifications list (each sentence): - Prior experience in financial services or a highly regulated, customer-facing role, demonstrating comfort with structured processes, accuracy, and service expectations - Experience building trust-based customer relationships through active listening, follow-up, and consistent engagement - Comfort initiating outreach (calls, emails, or other channels) to strengthen relationships and identify opportunities to support customer needs - Demonstrated comfort with digital tools and technology, with the ability to quickly learn new systems and confidently guide customers in adopting capabilities that enhance their banking experience - Ability to identify customer needs and connect them to appropriate solutions, including referrals when additional expertise is needed - Proven ability to collaborate with teammates and partners to resolve needs and deliver a seamless customer experience - Demonstrated ability to follow policies and regulations while identifying and escalating risk concerns Job Expectations content: - Ability to work a schedule that will include Saturdays - Support branch operations by flexing between cash handling and customer banking activities, with an emphasis on delivering strong service through account openings and ongoing account support. - 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 Location(s): "545 Madison Avenue NY, NY 10022" Pay Range: "$23.00 - $31.00" (base pay range). Also note incentive opportunities. Benefits 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 also have "Posting End Date: 4 Oct 2026" maybe minor metadata; 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 p for posting end date maybe. But it's not required; we can drop. We must not include boilerplate like EEO, etc. Now we need to map to sections. We have: About the role: paragraph. Responsibilities: ul li list. Requirements: maybe the Required Qualifications paragraph. Qualifications: maybe the Desired Qualifications list. Skills: maybe we can extract skills from desired qualifications: but we already have desired qualifications list; could be considered Skills. However we already have Qualifications section for desired qualifications. The instruction list includes both Qualifications and Skills as possible headings. We need to decide what to put where. We could treat Required Qualifications as Requirements, Desired Qualifications as Qualifications, and then Skills could be a subset like "Ability to identify customer needs..." etc. But that would duplicate. Better: Use Requirements for the mandatory experience (6+ months). Use Qualifications for the desired qualifications list. Use Skills for specific skill statements like comfort with digital tools, ability to identify needs, collaborate, follow policies. But those are already in desired qualifications. Could split. But we must not create thin sections; prefer few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one section? But we have both headings allowed; we could omit Skills if not enough distinct content. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if it would be thin. However we have many skill-like items; could make a Skills section with those items. But we already have Qualifications for desired qualifications; that may be enough. We could omit Skills. Alternatively, we could treat Required Qualifications as Requirements, Desired Qualifications as Qualifications, and then Skills could be something like "Demonstrated comfort with digital tools and technology, ability to quickly learn new systems, ability to guide customers, ability to identify needs, collaborate, follow policies". That's basically same as desired qualifications. Might be redundant. Given instruction to avoid thin sections, I'd include only sections that have substantial distinct content: About the role, Responsibilities, Requirements (required experience), Qualifications (desired qualifications), Benefits, Pay, Schedule. Possibly also Location? Not a heading; we could fold location into a short p under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is not minor metadata? It's substantive; maybe we can include a short p under About the role or separate? There's no heading for location; we could just include a
with location after About the role before Responsibilities. That's acceptable. Similarly, posting end date could be minor metadata; we can drop. Now schedule: we have ability to work schedule that will include Saturdays. Also maybe "Support branch operations by flexing between cash handling and customer banking activities" is more responsibility. But schedule section should contain schedule specifics. We'll put that. Now Pay: we have pay range. Now Benefits: list. Now we need to ensure we don't include any boilerplate. Now produce HTML fragment: use
for each section heading. Use - for lists. Use
for prose.
We must not include or .
We'll output something like:
About the role
Wells Fargo is seeking an Associate Personal Banker (SAFE) to join our National Branch. In this frontline role, you will build relationships with customers by supporting everyday banking needs through in‑branch interactions, scheduled conversations, and proactive outreach. You will learn about customers’ goals and connect them to the right banking products, services, and digital tools to help them manage their finances with confidence. You will support
for prose. We must not include or . We'll output something like:
About the role
Wells Fargo is seeking an Associate Personal Banker (SAFE) to join our National Branch. In this frontline role, you will build relationships with customers by supporting everyday banking needs through in‑branch interactions, scheduled conversations, and proactive outreach. You will learn about customers’ goals and connect them to the right banking products, services, and digital tools to help them manage their finances with confidence. You will support