Jobs · Finance · Wisconsin

Roving Personal Banker Shorewood Area

Wells Fargo · Menomonee Falls, WI · 1 mo ago
FinanceFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Must not include placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Pay Range: "This job profile is eligible for a 10% pay differential." That's some pay info. So we can include Pay section with that. Benefits? Not explicitly listed; there is mention of "robust benefits, competitive compensation" in the "Why Wells Fargo" intro but that's generic. Should we include Benefits? The instruction: never create Benefits sections unless posting actually states them. The posting says "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." That's a statement about benefits but not specific. Might be considered generic. Safer to omit Benefits section because not specific. Schedule: posting includes "Ability to work a schedule that will include Saturdays" and "Ability to travel 100% of the time within assigned geography." Also "Commute to assigned branch location(s) for the duration of the assignment". So we can include Schedule section with those details. Also "Job Expectations" includes schedule and travel. So we can put Schedule. We need sections: About the role (the paragraph after "About this role:"), Responsibilities (the bullet list after "In this role you will:"), Requirements (maybe "Required Qualifications:"), Qualifications (maybe "Desired Qualifications:"), Skills (maybe combine desired qualifications?), but we need to follow instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We have content for About the role (the paragraph after "About this role:" up to before "In this role you will:"). Responsibilities: the bullet list after "In this role you will:" (list of duties). Use
  • . Requirements: "Required Qualifications:" content. Qualifications: "Desired Qualifications:" content. Skills: maybe we could extract from desired qualifications? But they are qualifications. Could treat Skills as separate but we may not have explicit skills list. Could combine desired qualifications into Skills? But we already have Qualifications section for desired qualifications. Might be redundant. Perhaps we can put Skills as empty? Not allowed. Better to omit Skills if no specific skills section. Pay: we have "Pay Range: This job profile is eligible for a 10% pay differential." That's specific enough. Schedule: we have schedule details. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Make sure not to include boilerplate like "Why Wells Fargo" etc. That's introductory marketing; we should not include as it's not a section heading? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only output those headings we decide to include. The "Why Wells Fargo" is not a standard heading; we should omit it as it's boilerplate? It's marketing but maybe considered part of About the role? However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Why Wells Fargo" is substantive? It's about company culture. Could be considered part of About the role? But the section "About the role" is supposed to be about the role, not company. However we could include that as part of About the role? The instruction says "About the role" heading for section headings (e.g. About the role...). So we should put the role description under About the role. The "Why Wells Fargo" is not about the role; it's about company. Could be omitted as it's not role-specific? But it's substantive info about employer. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit it, we lose info. However the instruction also says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Could we include a heading like "About Wells Fargo"? Not in list. Probably they expect us to only use those headings; any other content should be placed under appropriate heading if possible. The "Why Wells Fargo" could be placed under About the role? Might be a stretch but could be considered part of role context. However the role description already starts after "About this role:" which is separate. The "Why Wells Fargo" is before that. Might be considered company overview, not role. But we could still include it as a paragraph under About the role heading? Might be okay. Better to include a short paragraph under About the role that includes both the "Why Wells Fargo" and the role description? But the role description is more specific. We could split: About the role heading includes the paragraph after "About this role:" (the role description). The "Why Wells Fargo" could be omitted as it's not role-specific but still substantive. However the instruction says preserve ALL substantive information; we would be losing that. But maybe they consider that boilerplate? It's not cookie/navigation/legal/EEO etc. It's marketing but still substantive. Hard to know. Given typical tasks, they'd expect to keep the "Why Wells Fargo" as part of About the role? I'd include it as a paragraph under About the role before the role-specific description. Thus About the role section will contain two paragraphs: first the "Why Wells Fargo" text, then the role description. Now Responsibilities: list items. Requirements: Required Qualifications paragraph. Qualifications: Desired Qualifications paragraph. Pay: the pay differential line. Schedule: the schedule expectations: 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 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. We should keep as prose maybe

    . Now ensure we don't include any boilerplate like "Posting End Date", "Posting Location(s)", "Job Expectations" heading? Actually "Job Expectations" is a heading in the posting; we could treat that as part of Schedule or Responsibilities? The content under Job Expectations includes schedule and travel etc. We already captured schedule. Could also include "Job Expectations" as a separate section but not in allowed headings. Better to incorporate into Schedule. We must not include "Posting Location(s)" etc. Remove. Also remove "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", EEO, etc. Also remove "Reference Number". Also remove "SAFE registration is required..." that's part of qualifications? Actually it's under Job Expectations? It's after schedule: "SAFE registration is required at the time of employment and Wells Fargo will initiate the process after your start date." That's a requirement; could be placed under Requirements or Qualifications. It's a requirement. We'll include under Requirements maybe as an extra sentence. Also "Loan Originators must meet LO/CFPB requirements..." is specific to loan originators; not relevant? Might be extraneous but it's substantive. Could be included under Requirements? Might be confusing. Since role is Roving Associate Personal Banker (SAFE), not loan originator. That line may be irrelevant but it's in posting. We could keep it under Requirements as a note? Might be considered boilerplate for certain roles. Safer to omit? It's specific to loan originators, not this role. Might be considered not applicable. I'd omit. Also "This position is not eligible for Visa sponsorship" is a requirement; include under Requirements. Now format. We'll output:

    About the role

    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!

    About this 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 Responsibilities:

    Responsibilities

    • 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
    Requirements:

    Requirements

    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

    SAFE registration is required at the time of employment and Wells Fargo will initiate the process after your start date.

    This position is not eligible for Visa sponsorship.

    Qualifications:

    Qualifications

    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

Similar jobs