Personal Banker Midtown Place

We need to output HTML fragment with sections for headings where content exists. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must not include Job ID etc. Remove boilerplate. Preserve all substantive info. 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 overview; could be "About the role"? Actually "About This Role" heading appears later. The intro is more about Wells Fargo. Could be placed under a generic "About Wells Fargo" but we only have allowed headings list. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if there is real content. The intro about Wells Fargo could go under "About the role"? Actually "About the role" is for role description. The company overview could be placed maybe under "About the role"? But better to include a short paragraph under "About the role" that includes both company and role? However they said do NOT repeat the job title as a heading. The job title is Associate Personal Banker (SAFE). Not to repeat as heading. We have sections: - About This Role: description of 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 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 substantive. - In This Role You Will: list of duties (bulleted). That's responsibilities. - Required Qualifications: bullet. - Desired Qualifications: bullet. - Job Expectations: bullet (schedule, SAFE registration, etc.) - Posting Location: maybe not needed as heading; could be a short p. - Posting End Date: maybe minor metadata; could be in short p. - Also mention "We Value Equal Opportunity" etc. That's boilerplate EEO; we should remove. - Drug and Alcohol Policy etc. Remove. - Third-party recordings etc. Remove. - Reference Number etc. Remove. We need to include sections only when posting has real specific content. So we need to decide which headings to include. We have content for: - About the role (maybe combine company overview and role description). Could put company overview under "About the role"? Might be okay. - Responsibilities: the "In This Role You Will" list. - Requirements: maybe combine Required Qualifications and Job Expectations? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings if content exists. We have Required Qualifications and Desired Qualifications. Could put Required under "Requirements", Desired under "Qualifications"? Or we could put both under "Qualifications". But we need to follow instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content: - About the role: company overview + role description? Might be okay. - Responsibilities: the bullet list under "In This Role You Will". - Requirements: maybe the Required Qualifications (6+ months interacting with customers experience, etc.) - Qualifications: Desired Qualifications list. - Skills: maybe we could extract skills from desired qualifications? But we could also leave Skills empty if no specific skill section. But we should not create empty sections. So we omit Skills if no specific content. - Benefits: The posting mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's in the company overview intro. So we have benefits content: "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." Also "You'll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow." That's more about culture. But we can include benefits section with that. - Pay: Not explicitly stated; only "competitive compensation" but no numbers. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation" but not specific pay. Is that enough? It says "competitive compensation" is a statement about pay. However they said never create Pay section unless posting actually states them. It does state "competitive compensation". That is a statement about pay, albeit vague. Should we include Pay? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive compensation, which is about pay. So we could include Pay section with that statement. However they also said prefer a few substantive sections over many thin ones. Might be better to incorporate that into Benefits or About the role. But we have Benefits already; we could mention compensation there. The instruction says never create Pay section unless posting actually states them. It does state competitive compensation, but we could still choose not to create a separate Pay section to avoid thin section. However we need to preserve all substantive information; we can include that statement in Benefits or About the role. Since we already have Benefits section, we can include compensation there. That would satisfy preserving info without creating a thin Pay section. - Schedule: The posting mentions "Ability to work a schedule that will include Saturdays" and "Support branch operations by flexing between cash handling and customer banking activities". Also maybe shift? So we have schedule info: includes Saturdays. So we can create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We should not include Skills (no specific). Benefits we have content. Now we need to format:

About the role

... company overview + role description ...

Then

Responsibilities

• ... each bullet ...

Then

Requirements

• ... required qualifications ...

Then

Qualifications

• ... desired qualifications ...

Then

Benefits

... robust benefits, competitive compensation, programs for work-life balance, community investment recognition, authentic self celebration, empowerment to grow ...

Then

Schedule

... ability to work schedule that includes Saturdays; flex between cash handling and customer banking activities ...

We also need to include location and posting end date maybe as a short p after sections? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can add a

with location and end date after sections, maybe before closing. We must preserve all substantive information: location, posting end date, note about posting may come down early, SAFE registration required, loan originator requirements, credit report review, not eligible for visa sponsorship. Those are substantive. We need to include them somewhere. Could be in a

under maybe "Job Details" but we don't have that heading. We could add a

after sections for "Additional Details". But we must not create a heading unless we have specific content for it. We could just add a

without heading. That's allowed: we can have

for prose. So we can add a paragraph containing location, posting end date, note about early removal, SAFE registration, loan originator requirements, credit report, visa sponsorship. We must not include boilerplate EEO etc. Let's extract substantive details: - Posting Location: 650 Ponce De Leon Ave Ne, Atlanta, GA 30308 - Posting End Date: 23 Sep 2026 - Job posting may come down early due to volume of applicants. - 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. Also maybe mention "Job Expectations: Ability to work a schedule that will include Saturdays" we already used in Schedule. Also "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." That's schedule/responsibilities. Now we need to ensure we didn't miss any responsibilities from "In This Role You Will". Let's list them: - 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 Now 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: - 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 Now Benefits: from intro: robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being. Also rewarded for investing in community, celebrated for being authentic self