Teller Part Time Central San Diego

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. We need to parse the posting. First, "About this role:" is a heading. So we can have

About the role

then paragraph(s) describing role. Then responsibilities: "In this role you will:" list items. So we can have

Responsibilities

then

• each bullet. Then Required Qualifications: list of qualifications. Could be under Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include. We have Required Qualifications and Desired Qualifications. Could combine into Qualifications section. Also we have "Job Expectations: Ability to work a schedule that will include Saturdays". That's schedule info. Also "This position is not eligible for Visa sponsorship" maybe metadata. We have Pay Range: $22.00 - $27.50. So we can have Pay section. Benefits: list of benefits. Schedule: mention ability to work schedule includes Saturdays. We also have location info: posting location(s) list. That could be minor metadata; we can put in a short

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

  or drop it. So location list can be a short paragraph. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, required qualifications, desired qualifications, benefits list, pay range, schedule note. We must not include boilerplate like EEO, equal opportunity, scam warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. Also remove "Wells Fargo Recruitment and Hiring Requirements:" etc. Also remove "Reference Number". Also remove "Living the Well Life" etc? That's part of why Wells Fargo intro; but that is generic fluff maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why Wells Fargo" section is more marketing fluff but not explicitly prohibited. However we need to preserve all substantive information; but that section is not about the role specifics; it's generic company description. Might be considered boilerplate? Not sure. Safer to keep it? 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. Might be considered not essential to role but still part of posting. However the sections we output are limited to headings list; we could include it under About the role? Actually About the role already covers role description. The "Why Wells Fargo" could be placed as a paragraph before About the role? But we are not supposed to add extra headings not in list. Could just include it as a

  before the first heading? The instruction says output ONLY the HTML fragment; no /. It didn't forbid extra paragraphs outside headings. But they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have other

  content not under headings? Probably okay but better to fit under About the role. Thus we can combine the "Why Wells Fargo" fluff into About the role paragraph? Might be okay but it's not about the role. However we could still include it as a paragraph under About the role as general context. It's not violating. Now let's extract specifics. About this role: paragraph after "About this 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 the About the role content. Now Responsibilities: list after "In this role you will:" each bullet: - 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. Now Required Qualifications: bullet list? It says: "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" That's a single sentence but we can treat as a

  or

  • . Probably a

    . Desired Qualifications: list of bullet points after "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. Now Job Expectations: "Ability to work a schedule that will include Saturdays". Also "This position is not eligible for Visa sponsorship". Also "Posting Location(s): ..." list. We need Schedule section: mention ability to work schedule includes Saturdays. Could also note not eligible for Visa sponsorship maybe as metadata. Pay: "$22.00 - $27.50". Also note "Pay may vary depending on factors..." but that's generic; we can include as part of Pay section maybe as a sentence. Benefits: list after "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then bullet 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 keep each as

  • . Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications and Desired Qualifications; could combine into Qualifications section. Skills maybe we could extract from desired qualifications? But we already have qualifications covering skills. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (combining required and desired), Benefits, Pay, Schedule. That's 6 sections. We could also include Skills if we want to separate but not needed. We need to ensure we don't create sections with filler like "commensurate with experience". We have no such. Now we need to output HTML fragment. Structure:

    About the role

    ... (including maybe the Why Wells Fargo fluff? We'll incorporate maybe as a sentence before role description? But we can just put the role description as given.)

    Responsibilities

    • ...
    ...

    Qualifications

    Required: 6+ months of interacting with customers experience, or equivalent demonstrated through work experience, training, military experience, education.

    Desired: ... list items as

    maybe? Could also make a
    under Qualifications for desired qualifications. But we need to avoid too many sections; we can have a

    summarizing desired qualifications? But we need to preserve all detail; we can't summarize away detail. So we need to list each desired qualification item. Could put them under Qualifications as a

    after a

    heading "Desired Qualifications:" but that would be a heading inside Qualifications which is not allowed (only h3 for section headings). However we could embed a Desired Qualifications: inside a

    then a

    . That's okay. Thus Qualifications section could contain:

    Required Qualifications: 6+ months of interacting with customers experience, or equivalent demonstrated through work experience, training, military experience, education.

    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.
    ...
    That preserves detail. Now Benefits section:

    Benefits

    • 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
    • Scholiships for dependent children
    • Adoption reimbursement
    Pay section:

    Pay

    $22.00 - $27.50 per hour. Pay may vary depending on factors including demonstrated prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities.

    Schedule section:

    Schedule

    Ability to work a schedule that will include Saturdays.

    We might also include location info as a short p under About the role or separate? Could add a

    under About the role after the description: "Posting locations: 5