Teller Bilingual Spanish Part Time San Lorenzo CA

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 must not repeat job title as heading. No Job ID/requisition numbers as headings; fold minor metadata into short p or drop. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to parse the posting. Content: - Intro: "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!" That's generic company description; maybe we can include as "About the role"? Actually "About this role:" is a heading in posting. So we can put that content under

About the role

. The "About this role:" paragraph: "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." We should include that as About the role. Then "In this role you will:" list of duties. Those are responsibilities. So we can put under

Responsibilities

with

• each bullet. List items: - 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. That's responsibilities. Then "Required Qualifications:" bullet list? 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 Bilingual speaking and listening proficiency in Spanish/English". That's required qualifications. Then "Desired Qualifications:" list of many bullet-like sentences. Those could be considered Skills or Qualifications. The instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide where to put required and desired qualifications. Possibly Required Qualifications under

  Requirements

  and Desired Qualifications under

  Qualifications

  or Skills. But we must not create thin sections; we can combine if appropriate. However we have both required and desired; we could put Required Qualifications under Requirements, Desired Qualifications under Qualifications (or Skills). The desired qualifications list includes many skill-like items: strong attention to detail, ability to accurately process transactions across multiple systems, strong verbal communication and active listening skills, ability to follow policies, proven cash-handling experience, ability to quickly build accuracy, professional integrity-driven approach, ability to recognize potential risk, ability to understand customer needs, identify referral opportunities, educate customers on digital banking tools, strong collaboration and relationship-building skills, organized and adaptable, ability to prioritize, ability to resolve routine customer concerns. These are skills/qualifications. We could put them under

  Skills

  . But we also have a Qualifications section maybe for desired qualifications. However we need to avoid thin sections; but we have enough content for each. We also have "Job Expectations:" bullet: Ability to work a schedule that will include Saturdays; This position is not eligible for Visa sponsorship; Must take and pass required language assessment. That's schedule and other expectations. So we can have Schedule section for ability to work schedule including Saturdays. Visa sponsorship and language assessment maybe not schedule; but we could include under Job Expectations but we only have allowed sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put schedule info under Schedule. Visa sponsorship and language assessment maybe could be placed under Requirements? But they are not exactly requirements; they are job expectations. Could include under Schedule as additional notes? Might be okay to include them in Schedule

  . Or we could drop them if they are minor metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Visa sponsorship and language assessment maybe considered minor metadata; we could fold into a short

  under Schedule or maybe under Requirements? But better to include them in Schedule section as they relate to schedule/eligibility. However schedule section should only be emitted if posting has real specific content for it. It does: "Ability to work a schedule that will include Saturdays". That's specific. So we can have Schedule section with that sentence. The other two items (visa sponsorship, language assessment) could be added as additional sentences in same

  or maybe separate

  . We'll keep them. Then Benefits: The posting lists benefits under "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then 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 should output as

  • each. Pay: The posting includes "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. $22.00 - $27.50". So we have pay range. So we can have Pay section with that info. Now we need to avoid boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is "Posting End Date: 29 Sep 2026 * Job posting may come down early due to volume of applicants. We Value Equal Opportunity Wells Fargo is an equal opportunity employer...." That's EEO boilerplate; we must remove. Also "Applicants with Disabilities ..." etc. Also "Drug and Alcohol Policy". Also "Wells Fargo Recruitment and Hiring Requirements:" etc. All that must be removed. Also "Posting Location(s): San Lorenzo, CA 94580 @RWF22" maybe minor metadata; we could fold into a short

    maybe under About the role? But location is substantive? It's location of job. Could be considered minor metadata but maybe we should keep? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." Location is not a heading; we could include as a short

    maybe under About the role or separate? But we have no section for location; we could just include a

    after About the role before Responsibilities. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a location paragraph might be okay as a short

    . But we need to decide if location is substantive enough to keep. The posting includes location; it's relevant. I'd keep it as a

    maybe under About the role or separate

    before sections. Since we cannot add arbitrary headings, we can just put a

    with location. Similarly "Posting End Date: 29 Sep 2026 * Job posting may come down early due to volume of applicants." That's metadata; could be dropped as per instruction to drop minor metadata. Probably drop. Also "Pay Range Reflected is the base pay range offered for this position..." we keep. Now we need to output only HTML fragment, no /, no markdown fences. Thus final HTML:

    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.

    Posting Location(s): San Lorenzo, CA 94580 @RWF22

    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,