Personal Banker Sioux Falls

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, EEO, legal, etc. Also remove application instructions. Must not include placeholder text like "commensurate with experience". Must not create sections unless posting actually states them. We need to parse the posting. Content: - Intro about Wells Fargo (company description) maybe not needed? It's part of "About This Role"? Actually "About This Role" heading appears. The text after "About This Role" is description of role. So we can put that under

About the role

with paragraphs. - Then "In This Role You Will" list of duties. That's responsibilities. So we can put under

Responsibilities

with

• each bullet. - Then "Required Qualifications:" bullet? Actually it's a paragraph: "6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education". That's required qualifications. - Then "Desired Qualifications:" list of items. Those are desired qualifications (maybe skills). Could be under

  Qualifications

  or separate Required and Desired? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have "Requirements" and "Qualifications". Possibly "Requirements" for required qualifications, "Qualifications" for desired? Or "Skills" for desired? We need to decide. We have required qualifications: 6+ months interacting with customers experience, or equivalent via work experience, training, military, education. Desired qualifications: list of items: prior experience in financial services or highly regulated customer-facing role, demonstrating comfort with structured processes, accuracy, service expectations; experience building trust-based customer relationships through active listening, follow-up, consistent engagement; comfort initiating outreach; demonstrated comfort with digital tools and technology, ability to learn new systems and guide customers; ability to identify customer needs and connect them to appropriate solutions, including referrals; proven ability to collaborate with teammates and partners to resolve needs and deliver seamless experience; demonstrated ability to follow policies and regulations while identifying and escalating risk concerns. Also "Job Expectations: 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" Also posting locations list and posting end date. We need to include schedule info: "Ability to work a schedule that will include Saturdays". That's schedule. So we can have a Schedule section with that sentence. Pay: Not mentioned. So we should NOT create Pay section. Benefits: Not mentioned explicitly in the role description; earlier intro mentions robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being. That's generic company benefits. The instruction: "Prefer a few substantive sections over many thin ones." Should we include Benefits? The posting mentions "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." That's somewhat generic but still specific? It mentions benefits, compensation, work-life balance programs. Might be considered substantive. However the instruction says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits (robust benefits) and compensation (competitive compensation). So we could include Benefits section with that sentence. Pay: they mention competitive compensation but not specific numbers. That's still mention of compensation. However they said never create Pay section unless posting actually states them. It does state "competitive compensation". That is a statement about pay, albeit not specific. Should we include Pay? The instruction also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive compensation" is not filler? It's vague but still a statement. Might be okay. However they said prefer few substantive sections over many thin ones. Could combine Benefits and Pay? But headings are separate. Might be better to include Benefits section with that sentence, and maybe not include Pay because it's not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits and compensation. So we could create Benefits section with that sentence. For Pay, we could omit because it's not a specific number or range; but they said "competitive compensation" is a statement about pay. I'd lean to include Pay section with that sentence? However they said avoid filler like "commensurate with experience". "competitive compensation" is similar vagueness. Might be considered filler. Safer to omit Pay. Schedule: we have explicit statement about schedule including Saturdays. So include Schedule. Now we need to include location info? Not a heading; maybe we can fold into a short

  under About the role or maybe separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Location and posting end date are minor metadata; we can include a short

  maybe after About the role. We must not include boilerplate like EEO, legal, etc. Remove all that. We must preserve all substantive information: company intro about Wells Fargo? That's maybe not substantive for the role? It's generic but could be considered part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." The company intro is not specific to the role; maybe we can drop it? But it's part of the posting. However we could include it under About the role as a paragraph describing the company. It's substantive? It's about Wells Fargo being a global trailblazer etc. Might be considered boilerplate but it's unique to Wells Fargo. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description is not those. So we can keep it. Thus structure:

  About the role

  Wells Fargo description...

  About This 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.

  But note we already used "About This Role" as heading; we should not repeat job title. The "About This Role" heading is part of posting; we convert to

  About the role

  . Then we can include the paragraph(s) that follow. Then responsibilities:

  Responsibilities

  • 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
  Then Requirements (required qualifications):

  Requirements

  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 Qualifications (desired qualifications):

  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
  Then Benefits? The 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." That's benefits and compensation. We could make a Benefits section with that paragraph (excluding compensation maybe). But we decided maybe not include Pay. Let's include Benefits section with that sentence about robust benefits, programs for work-life balance, community investment, authentic self, empowerment. We'll omit competitive compensation from Benefits to avoid Pay duplication. Or we could include both benefits and compensation in Benefits. But then we would have no Pay section. That's fine. Thus:

  Benefits

  Living the Well Life means you're supported in life, not just work. It means having robust benefits, 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.

  We removed "competitive compensation". Could also keep it but then it's compensation. Might be okay. But to avoid Pay section, we can keep compensation in Benefits as it's not a separate Pay heading. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits and compensation. So we can have Benefits section that includes both. That's fine. Thus Benefits paragraph: "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." Now Schedule:

  Schedule

  Ability to work a schedule that will include Saturdays

  We could also include the rest of Job Expectations about flexing between cash handling and customer banking activities, emphasis on account openings, SAFE registration required, etc. Those are not schedule but maybe job expectations. Could be included under Responsibilities or