Teller Bilingual Spanish Part Time Henderson NV

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, "Why Wells Fargo" is intro; we can include maybe as part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need headings for sections that have content. We need to extract: - About the role: The paragraph after "About this role:" includes description: "Wells Fargo is seeking a Teller to join our National Branch Network..." etc. So we can put that in

. - Responsibilities: The list after "In this role you will:" includes bullet points. Those are duties. So we can put under Responsibilities with

• . - Requirements: There's "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" etc. We need to separate maybe Requirements (required) and Qualifications (desired) and Skills? The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what content goes where. We have Required Qualifications: list items: 6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education; Bilingual speaking and listening proficiency in Spanish/English. Desired Qualifications: many bullet points. Job Expectations: Ability to work a schedule that will include Saturdays; This position is not eligible for Visa sponsorship; Must take and pass required language assessment. Also there is "Pay Range Reflected is the base pay range offered for this position..." and "$20.00 - $25.00". So Pay section. Benefits: list of benefits. Schedule: maybe from Job Expectations about schedule includes Saturdays. Also maybe we can put schedule there. We must not include placeholder text like "commensurate with experience", etc. Not present. We must remove boilerplate: EEO, legal, etc. So we cut out those paragraphs. We need to preserve all substantive info. Let's craft sections:

  About the role

  Wells Fargo is seeking a Teller to join our National Branch Network. In this front line, customer focused role, you will support customers’ everyday banking needs through in-branch interactions, completing transactions accurately while delivering a welcoming and reliable experience. As a primary point of contact for customers, you represent the branch through strong service, attention to detail, and genuine care. As a Teller, you will build foundational banking skills while learning about customers’ needs and introducing them to helpful products, services, and digital tools. You will identify opportunities to support customers and connect them to the right banker for more detailed product conversations. You will work closely with branch teammates to keep daily operations running smoothly and deliver a consistent, high-quality customer experience. This role offers meaningful exposure to retail banking and serves as an excellent starting point for long-term growth and career mobility, supported by Wells Fargo’s training, coaching, and team-based culture.

  Responsibilities

  • Deliver a positive and reliable branch experience by accurately processing transactions and engaging customers with care.
  • Process routine service transactions (such as deposits, withdrawals, payments, and check cashing) with accuracy and attention to detail.
  • Welcome customers, understand their needs, and guide them to efficient ways to bank, including digital tools, self-service options, or the appropriate team member.
  • Build relationships, actively listen to understand everyday financial needs, and connect customers to relevant information, services, digital tools, or bankers.
  • Identify potential product or service needs, introduce solutions at a high level, and refer customers to a banker for detailed guidance.
  • Complete transactional and operational activities accurately, exercising sound judgment and managing risk in line with policies and controls.
  • Use strong communication and active listening skills to clarify needs and provide clear, simple solutions or next steps.
  • Collaborate with branch teammates to deliver strong operations and service, follow leadership direction, and escalate complex situations as needed.
  • Resolve routine customer questions or concerns and escalate more complex issues to ensure timely resolution.

  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
  • Bilingual speaking and listening proficiency in Spanish/English

  Desired Qualifications

  • Experience in customer-facing roles, with strong attention to detail and the ability to accurately process transactions across multiple systems in fast-paced environments.
  • Strong verbal communication and active listening skills, with the ability to understand needs, ask effective questions, and clearly explain solutions.
  • Ability to follow policies, procedures, and controls while maintaining accuracy and accountability.
  • Proven cash-handling experience
  • Demonstrated ability to quickly build accuracy, confidence, and consistency in customer transactions.
  • Professional, integrity-driven approach focused on building trust through reliable service.
  • Ability to recognize potential risk, ask questions, and appropriately escalate concerns to protect customers and the organization.
  • Ability to understand customer needs, identify referral and service opportunities, and educate customers on digital banking tools to improve convenience.
  • Strong collaboration and relationship-building skills, with the ability to work effectively with branch teammates to deliver a consistent customer experience.
  • Organized and adaptable, with the ability to prioritize effectively in a dynamic, customer-focused environment.
  • Ability to resolve routine customer concerns with sound judgment and professionalism.

  Job Expectations

  • Ability to work a schedule that will include Saturdays
  • This position is not eligible for Visa sponsorship
  • Must take and pass required language assessment
  Now Pay and Benefits and Schedule. Pay: we have "$20.00 - $25.00" and description: "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities." We should include that as a

  under Pay. Benefits: list: Health benefits, 401(k) Plan, Paid time off, Disability benefits, Life insurance, critical illness insurance, and accident insurance, Parental leave, Critical caregiving leave, Discounts and savings, Commuter benefits, Tuition reimbursement, Scholarships for dependent children, Adoption reimbursement. We can put as

  . Schedule: we already have schedule in Job Expectations (Ability to work a schedule that will include Saturdays). Could also create a Schedule section with that content. But we already have Job Expectations covering schedule plus other expectations. The instruction says we can have Schedule section if posting actually states them. It does state schedule includes Saturdays. So we could either keep Job Expectations or split. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine schedule into Job Expectations is fine. But we also need to include a Schedule section only if posting has real specific content for it. It does, but we already have schedule content in Job Expectations. Could we rename Job Expectations to Schedule? But we also have other expectations (visa sponsorship, language assessment). Those are not schedule. Might be better to keep Job Expectations as a section (covers schedule, visa, language assessment). However the allowed headings list includes Schedule but not Job Expectations. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. It might be okay to use other headings? Probably they want only those headings. So we should map content to those headings. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put Required Qualifications, Desired Qualifications, Job Expectations. Could map Required Qualifications -> Requirements, Desired Qualifications -> Qualifications, Job Expectations -> Skills? Or maybe Skills for desired qualifications? But we also have Skills section possible. Let's think: The posting includes "Required Qualifications" and "Desired Qualifications". Those could go under Requirements and Qualifications respectively. Skills could be derived from desired qualifications (like communication, etc.) but we could also put desired qualifications under Qualifications and maybe not have Skills separate if content thin. But we need to avoid thin sections. Perhaps we can combine Desired Qualifications and Skills into one Qualifications section, and not have separate Skills. Or we could put desired qualifications under Qualifications and put some skill-like items under Skills. But we have many desired qualifications; they are more like skills/experience. Could treat them as Skills. Then Qualifications could be required qualifications only. Let's do: - Requirements: Required Qualifications (the 6+ months, bilingual) - Qualifications: maybe we could put nothing? But we need to avoid empty. Could combine desired qualifications into Qualifications? But then we would have both Requirements and Qualifications with content. Skills maybe we could omit if we think desired qualifications already covered. However we have a Skills heading allowed; we could put some of the desired qualifications that are skill-based under Skills, and keep Qualifications for things like experience, education, etc. But the desired qualifications list includes many skill-like items. Could split. Simplify: Use Requirements for required qualifications, Qualifications for desired qualifications, and omit Skills (since we already covered). The instruction says we can include a section only when posting has real specific content for it. So we can omit Skills if we don't have distinct content beyond what's already in Qualifications. That seems acceptable. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to put schedule content: Ability to work a schedule that will include Saturdays. Also maybe we could mention that schedule includes Saturdays only. We'll put that under Schedule. Now we need to exclude boilerplate: EEO, legal, etc. Also remove "Posting Location(s): Henderson, NV 89014 @RWF22" maybe minor metadata; we can fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a short p for location maybe. But location is not a heading; we could just drop it. Probably safe to drop. Also remove "Posting End Date: 1 Oct 2026 * Job posting may come down early due to volume of applicants." That's metadata; drop. Also remove "Pay Range Reflected is the base pay range offered for this position..." we keep under Pay. Now produce HTML fragment. Let's craft:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  ...

  Pay

  $20.00 - $25.00 (base pay range; may vary based on performance, skills, experience, or work location; incentive opportunities may be available)

  Schedule