Teller 20 Hours Pembroke Pines FL

We need to output HTML fragment only, with sections for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. We must not repeat job title. Must include only sections with real content. Must not include boilerplate like EEO, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include placeholder sections like Pay/Schedule/Benefits unless posting actually states them. Let's see what the posting includes. From the text: - "Why Wells Fargo: ..." includes description of company, benefits, etc. That could be considered "About the role"? Actually "About this role:" section follows. We need to parse sections: - "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!" This is company overview and benefits. Could be placed under "About the role"? But there is also "About this role:" later. We need to decide sections: The instructions say use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content for it. So we need to see what content maps. - About the role: The "About this role:" section describes 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." That's substantive. So we can have

About the role

with that content in

. - Responsibilities: The bullet list after "In this role you will:" enumerates duties. That's responsibilities. So we can have

Responsibilities

with

• each duty. - Required Qualifications: The section "Required Qualifications:" with "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 qualifications. Could be under Requirements or Qualifications. The instructions list both Requirements and Qualifications as possible headings. We need to decide which to use. Probably we can put Required Qualifications under

  Requirements

  or

  Qualifications

  . Since they have both headings as examples, we could use Requirements for required qualifications, and Qualifications for desired qualifications? Or we could combine. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose whichever fits. We have both required and desired qualifications. Could make two sections: Requirements (for required) and Qualifications (for desired). Or we could have Requirements covering both required and desired. But better to separate: Requirements for required qualifications, Qualifications for desired qualifications (or Skills). However desired qualifications list includes many skill-like items: experience in customer-facing roles, strong attention to detail, ability to accurately process transactions, strong verbal communication, etc. Those could be Skills. The instructions include Skills heading. So we could map: - Requirements: Required Qualifications (6+ months interacting with customers experience, or equivalent) - Qualifications: Desired Qualifications (list of items) - Skills: maybe not needed if we already have Qualifications covering skills. But we could also put the skill-like items under Skills. However we must not create thin sections; prefer few substantive sections over many thin ones. So maybe combine required and desired into Requirements? But then we lose distinction. However we could have Requirements (required) and Skills (desired). That seems reasonable. Let's examine desired qualifications list: "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." These are skills/qualities. So we could put them under

  Skills

  . Then Required Qualifications under

  Requirements

  . That seems appropriate. Now Benefits: The "Why Wells Fargo" section mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's benefits info. So we can have

  Benefits

  with that content. Pay: Not explicitly stated. No salary range. So we should NOT create Pay section. Schedule: The posting includes "Job Expectations: Ability to work a schedule that will include Saturdays". That's schedule info. So we can have

  Schedule

  with that sentence. Also there is "Posting Location: Silver Lakes Branch: 17199 Pines Blvd, PEMBROKE PINES, FL 33027" and "Posting End Date: 29 Sep 2026". This is minor metadata; we can fold into a short

  or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a

  with location and end date maybe. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "Job Expectations: Ability to work a schedule that will include Saturdays" we already used for Schedule. Also remove "This position is not eligible for Visa sponsorship" maybe minor metadata; could be included in a short p? It's not heading. Could be included in a short p with other metadata. But we can drop if not needed. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Visa sponsorship line is not exactly boilerplate but could be considered minor metadata; we can fold into a short p. Also "Reference Number R-572171" is minor metadata. We need to preserve all substantive information. So we need to keep location, posting end date, visa sponsorship? Might be considered substantive? It's about eligibility. Might be relevant. But we can include in a short p. Let's structure:

  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.

  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

  Skills

  • 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.