Associate Personal Banker - Morganton Plaza
or drop it. So we could include a short p with location and posting end date. But we might drop it as minor metadata. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Location and posting end date are substantive? Might be considered metadata but still info. However they said fold minor metadata into a short
or drop it. So we can include a short p with location and end date. Now Benefits section: from intro: "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." We can put that as Benefits. Schedule section: from Job Expectations: "Ability to work a schedule that will include Saturdays" plus maybe "Support branch operations by flexing between cash handling and customer banking activities". That's schedule-related. We should not create Pay section because no specific pay. Now we need to output HTML fragment with headings
for each section. Use - for lists. Use
for prose.
We must not include any extra markup like or . Just the fragment.
Order: About the role, Responsibilities, Requirements, Qualifications (maybe split Required vs Desired?), Skills, Benefits, Schedule. But we need to decide which sections to include based on content.
We have:
- About the role: yes.
- Responsibilities: yes (list).
- Requirements: we have Required Qualifications + Job Expectations (schedule, SAFE registration, etc). Could combine.
- Qualifications: maybe Desired Qualifications? Could be Skills? The rules: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. We need to map content appropriately.
We have Required Qualifications (mandatory) and Desired Qualifications (preferred). Could put Required under Requirements, Desired under Qualifications or Skills. The desired qualifications include experience, relationship building, outreach, digital tools, identifying needs, collaboration, following policies. Those are skills/qualifications. Could put under Skills.
Thus:
- Requirements: Required Qualifications + Job Expectations (schedule, SAFE registration, credit report, visa not eligible, etc). Might also include "Loan Originators must meet LO/CFPB requirements" but that seems irrelevant to this role; but it's in Job Expectations. We'll keep.
- Qualifications: maybe we could put Desired Qualifications here.
- Skills: maybe we could put some of the desired qualifications that are skill-based. But we have limited sections; we could combine Desired Qualifications into Qualifications and not use Skills. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not needed. However we have content for Skills maybe. But we can decide to include Skills if we have distinct skill-based content not covered elsewhere. Desired Qualifications includes skill-like items. Could put them under Skills. Then Qualifications could be empty? Better to put Desired Qualifications under Qualifications and omit Skills. Or we could put Required under Requirements, Desired under Skills, and leave Qualifications empty (but we must not emit heading with filler). So we should not emit a Qualifications heading if we have no specific content for it. So we will not include Qualifications heading.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Check if we have content for Skills: we can take Desired Qualifications list as skills. That seems appropriate.
Now Benefits: we have the paragraph about robust benefits etc.
Schedule: we have ability to work schedule including Saturdays, plus maybe "Support branch operations by flexing between cash handling and customer banking activities". That's schedule-related.
Now we need to ensure we don't include boilerplate like EEO, etc. We removed.
Now produce HTML.
Structure:
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 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
for prose. We must not include any extra markup like or . Just the fragment. Order: About the role, Responsibilities, Requirements, Qualifications (maybe split Required vs Desired?), Skills, Benefits, Schedule. But we need to decide which sections to include based on content. We have: - About the role: yes. - Responsibilities: yes (list). - Requirements: we have Required Qualifications + Job Expectations (schedule, SAFE registration, etc). Could combine. - Qualifications: maybe Desired Qualifications? Could be Skills? The rules: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. We need to map content appropriately. We have Required Qualifications (mandatory) and Desired Qualifications (preferred). Could put Required under Requirements, Desired under Qualifications or Skills. The desired qualifications include experience, relationship building, outreach, digital tools, identifying needs, collaboration, following policies. Those are skills/qualifications. Could put under Skills. Thus: - Requirements: Required Qualifications + Job Expectations (schedule, SAFE registration, credit report, visa not eligible, etc). Might also include "Loan Originators must meet LO/CFPB requirements" but that seems irrelevant to this role; but it's in Job Expectations. We'll keep. - Qualifications: maybe we could put Desired Qualifications here. - Skills: maybe we could put some of the desired qualifications that are skill-based. But we have limited sections; we could combine Desired Qualifications into Qualifications and not use Skills. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could omit Skills if not needed. However we have content for Skills maybe. But we can decide to include Skills if we have distinct skill-based content not covered elsewhere. Desired Qualifications includes skill-like items. Could put them under Skills. Then Qualifications could be empty? Better to put Desired Qualifications under Qualifications and omit Skills. Or we could put Required under Requirements, Desired under Skills, and leave Qualifications empty (but we must not emit heading with filler). So we should not emit a Qualifications heading if we have no specific content for it. So we will not include Qualifications heading. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Check if we have content for Skills: we can take Desired Qualifications list as skills. That seems appropriate. Now Benefits: we have the paragraph about robust benefits etc. Schedule: we have ability to work schedule including Saturdays, plus maybe "Support branch operations by flexing between cash handling and customer banking activities". That's schedule-related. Now we need to ensure we don't include boilerplate like EEO, etc. We removed. Now produce HTML. Structure:
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 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