Associate Roving Personal Banker, Winston Salem District
About the role
with paragraph describing role: "Wells Fargo is seeking a Roving Associate Personal Banker (SAFE) to join our National Branch Network. In this front-line role, you will provide support across multiple branch locations within an assigned geography, building 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 across different locations to deliver a consistent, high-quality customer experience. Success is driven by a strong service mindset, sound judgment, flexibility, and effective teamwork in changing branch environments. This role offers meaningful exposure to a large financial institution and serves as a foundation for long-term growth and career mobility, supported by Wells Fargo's training and coaching." - Then "In This Role You Will" list of duties. That's responsibilities. SoResponsibilities
with- each bullet.
List items:
- Provide personalized banking support across multiple branch locations within an assigned geographic area, covering for banker and teller absences and temporarily filling open positions as needed
- Adapt quickly to new branch environments, teams, and customer needs while maintaining consistent service quality and adherence to bank standards
- 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 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 judgment 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
- Then "Required Qualifications:" bullet: "6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education"
- Then "Desired Qualifications:" list of items.
- Then "Job Expectations:" list.
- Then "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"
- Then "Posting Location(s):" list of addresses.
- Then "Pay Range: This job profile is eligible for a 10% pay differential."
- Then "Posting End Date: 7 Oct 2026 Job posting may come down early due to volume of applicants."
- Then EEO etc (remove).
- Then "Reference Number R-576742-1" (metadata, drop).
We need sections: About the role (we have). Responsibilities (we have). Requirements (maybe combine Required Qualifications? The spec says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide mapping. We have Required Qualifications and Desired Qualifications. Could put under Requirements (maybe required) and Qualifications (desired). Or we could combine both into Qualifications. But spec says we can include sections only when posting has real specific content. We have both required and desired. Could create Requirements for required qualifications, and Qualifications for desired qualifications. Also Skills maybe from desired qualifications list (some are skills). But we can also put skills under Qualifications. However we need to avoid thin sections. Let's see content: Required Qualifications: one bullet (6+ months interacting with customers experience, or equivalent...). That's substantive. Desired Qualifications: multiple bullet points about prior experience, building trust, outreach, digital tools, identify needs, collaborate, follow policies. Job Expectations: travel 100%, schedule includes Saturdays, support branch operations flexing between cash handling and customer banking activities, SAFE registration required, loan originator requirements, credit report review, not eligible for visa sponsorship. Pay: "This job profile is eligible for a 10% pay differential." That's specific. Schedule: mention ability to work schedule that includes Saturdays, travel 100% etc. Could be under Schedule. Benefits: Not mentioned explicitly besides "robust benefits, competitive compensation" in intro but that's generic fluff. The spec says do not create Benefits unless posting actually states them. The intro mentions "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." That's somewhat generic but still mentions benefits. However it's part of company description, not specific to role. Might be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The benefits statement is part of the company pitch, not necessarily boilerplate but could be considered generic. However it's not a specific benefit like health insurance, 401k. The spec says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (robust benefits). So we could include a Benefits section with that sentence? But we must not include filler like "commensurate with experience". The phrase "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." is somewhat vague but still a statement. I'd consider it substantive enough to include a Benefits section. But we also have Pay differential statement. Schedule: travel 100% and ability to work schedule that includes Saturdays. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to avoid thin sections. Let's see if we can combine some. Maybe we can have: - About the role (intro) - Responsibilities (list) - Requirements (Required Qualifications) - Qualifications (Desired Qualifications) - Skills (maybe extract from desired qualifications: digital tools, outreach, collaboration, etc.) but that would be thin. Better: combine Desired Qualifications and Skills into Qualifications section (since they are qualifications). Then we could have Skills omitted. But spec list includes Skills as possible heading; we can omit if not needed. We need to include Pay and Schedule sections if we have content. Benefits: we have statement. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check each for substantive content. About the role: we have paragraph. Responsibilities: list of duties. Requirements: Required Qualifications bullet. Qualifications: Desired Qualifications bullet list. Benefits: sentence about robust benefits etc. Pay: "This job profile is eligible for a 10% pay differential." Schedule: includes travel 100% and ability to work schedule that includes Saturdays. Also maybe mention SAFE registration etc? That's more requirement. But schedule: "Ability to travel 100% of the time within assigned geography. Commute to assigned branch location(s) for the duration of the assignment, with travel expectations aligned to company policy Ability to work a schedule that will include Saturdays". We'll capture that. We must not include duplicated lines. Ensure we don't repeat. Now produce HTML fragment: use
for each section heading, then
for prose,
- for lists.
We must not include or . Just fragment.
Let's craft.
About the role paragraph: combine the intro paragraphs (maybe two paragraphs). We'll put as one
. Responsibilities:
- with each duty.
Requirements:
with the required qualifications sentence. Qualifications:
- with desired qualifications items.
Benefits:
with the benefits sentence. Pay:
with pay differential sentence. Schedule:
with travel and schedule expectations. Check for any leftover boilerplate: we removed EEO, reference number, etc. Make sure not to include "Posting Location(s)" etc. That's location info; is that substantive? It's location addresses. Should we include? The spec didn't list a Locations section; but we could include under About the role? Not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Location addresses are substantive. Should we include them? There's no specific heading for Locations in the allowed list, but we could maybe put them under About the role as a paragraph? However the spec says use headings only from the list; we could add a
with locations after About the role before Responsibilities. That's okay; we just shouldn't add a heading not in list. So we can include location list as a
or
- without a heading. But we need to decide if we want to include them. The spec says preserve ALL substantive information. So we should include location addresses.
Where to put? Could add a
after About the role: "Posting Location(s):" then list. But that heading "Posting Location(s):" is not allowed as a heading (since not in list). We can just include the sentence as part of a paragraph: "Posting Location(s): 5306 Hwy 158 (P.O. Box 40), Advance NC 27006; 2565 Lewisville-Clemmons Rd., Clemmons NC 27012; ..." etc. That's okay. Similarly, "Posting End Date: 7 Oct 2026 Job posting may come down early due to volume of applicants." That's also substantive. Could add as a paragraph after Pay or before? Not in headings list. We can include as a
without heading. Similarly, "SAFE registration is required at the time of employment..." etc. That's substantive; could be part of Requirements or Qualifications? It's about registration and visa. Could be part of Requirements (maybe under Required Qualifications). But we already have Required Qualifications separate. Could add another bullet under Requirements? Or we could add a separate
under Requirements. We need to preserve all substantive info, not just headings. So we need to embed those details somewhere. Let's list all substantive info blocks: - Company intro (About Wells Fargo) - we used in About the role. - About This Role paragraph (role description) - we used. - In This Role You Will list (Responsibilities) - used. - Required Qualifications: bullet. - Desired Qualifications: list. - Job Expectations: travel 100%, schedule includes Saturdays, support branch operations flexing between cash handling and customer banking activities, SAFE registration required, loan originator requirements, credit report review, not eligible for visa sponsorship. - Posting Location(s): list of addresses. - Pay Range: eligible for 10% pay differential. - Posting End Date: 7
- for lists.
We must not include or . Just fragment.
Let's craft.
About the role paragraph: combine the intro paragraphs (maybe two paragraphs). We'll put as one