Jobs · Finance · Utah

Teller Part Time Brighton Salt Lake City

Wells Fargo · Salt Lake City, UT · 1 mo ago
FinancePart-time
We need to produce HTML fragment with sections for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must include sections only when posting has real specific content. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Content: - Intro about Wells Fargo (company description). That's not a section heading but could be part of "About the role"? Actually "About This Role" heading present. The text after "About This Role" describes the role: "Wells Fargo is seeking a Teller to join our National Branch Network...". That's substantive. So we can put that under

About the role

with

. - Then "In This Role You Will" list of duties. That's responsibilities. So we can have

Responsibilities

with
  • each bullet. - Then "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" etc. We need to map to sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have 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 requirement. Desired Qualifications: a list of many items (experience in customer-facing roles, strong attention to detail, ability to accurately process transactions across multiple systems in fast-paced environments, strong verbal communication and active listening skills, ability to follow policies, proven cash-handling experience, demonstrated ability to quickly build accuracy, confidence, and consistency in customer transactions, professional integrity-driven approach, ability to recognize potential risk, ability to understand customer needs, identify referral and service 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 desired qualifications/skills. Job Expectations: "Ability to work a schedule that will include Saturdays" and "This position is not eligible for Visa sponsorship". Also location and posting end date etc. Those are metadata; we can fold minor metadata into a short

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

    or drop it." So we can include location and maybe schedule expectation in a

    under maybe "Schedule" section if schedule is stated. The schedule: "Ability to work a schedule that will include Saturdays". That's schedule info. So we can create a

    Schedule

    with

    Ability to work a schedule that will include Saturdays.

    . Also "This position is not eligible for Visa sponsorship" is minor metadata; could be placed in a

    maybe under Requirements or separate note. But we can fold into a short

    maybe under Requirements or at end. Benefits: The posting mentions earlier: "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 description. So we can create a

    Benefits

    with

    Robust benefits, competitive compensation, programs for work-life balance and well-being, rewards for community investment, recognition for authenticity, empowerment to grow.

    . Also mention "competitive compensation" but not specific pay. Since we cannot create Pay section unless posting actually states them. It mentions competitive compensation but not specific numbers, so we should not create Pay section (since no specific pay). The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits is stated (robust benefits etc). So we can include Benefits. Schedule is stated (Ability to work a schedule that will include Saturdays). So include Schedule. Pay: not specific, so omit Pay section. Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. Possibly combine Qualifications and Skills? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have separate sections for Requirements, Qualifications, Skills. But we need to avoid thin sections. We have Required Qualifications (a short bullet) and Desired Qualifications (a long list). Could split: Requirements = Required Qualifications; Qualifications = Desired Qualifications? Or Skills = some of the desired qualifications that are skills. But we can also combine Desired Qualifications into Skills section. However we must not invent sections with filler. Let's think: The posting includes both Required and Desired qualifications. We could have: - Requirements: Required Qualifications (6+ months...). - Qualifications: Desired Qualifications (list). - Skills: maybe we could extract skill-based items from Desired Qualifications (communication, attention to detail, cash handling, etc.) but that would be duplicative. Better to have Requirements and Qualifications only, and maybe Skills not needed. But the instruction says we can use those headings if we have content. It's okay to omit Skills if not needed. However we have a lot of skill-like items; we could put them under Skills. But then Qualifications would be empty? Not good. We could treat Required Qualifications as Requirements, Desired Qualifications as Qualifications, and maybe we don't need Skills. That seems reasonable. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Check if any other sections like "About the role" we already have. Now we need to preserve all substantive information. Let's extract: About the 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 keep that as a

    . Responsibilities: list from "In This Role You Will" bullet points. Let's extract 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. We need to ensure each as

  • . Requirements: 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 sentence. Could be

    or

    • . Since it's a single requirement, we can put

      . Qualifications: Desired Qualifications list. Let's extract each bullet: - 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. We'll put each as

    • under
        . Benefits: from earlier: "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." That's benefits plus recognition. We'll keep the benefits description: robust benefits, competitive compensation, programs for work-life balance and well-being, rewarded for investing in community, celebrated for being authentic self, empowered to grow. Also mention recognition as top five LinkedIn Top Companies. That's also a benefit/recognition. We'll include. Schedule: "Ability to work a schedule that will include Saturdays". Also maybe mention location? But location is minor metadata; we can include in a short

        maybe under a separate "Location" but not required. The instruction says fold minor metadata into a short

        or drop it. We could add a

        for location: "Posting Location(s): 1985 E 7000 S Salt Lake City, UT 84121". But that's minor metadata; we could drop it. Safer to drop it. Also posting end date etc. Drop. Visa sponsorship note: "This position is not eligible for Visa sponsorship". That's also minor metadata; we could drop or include in a short

        . Probably drop. Now we need to output only HTML fragment, no /, no markdown fences. Thus:

        About the role

        ...

        Responsibilities

        • ...
        • ...

        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

        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.

Similar jobs