Teller Part Time Mission Bend

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. Remove boilerplate. The posting includes: - About This Role: description of role, front line, etc. - In This Role You Will: list of duties (multiple bullet-like sentences). Could be responsibilities. - Required Qualifications: 6+ months of interacting with customers experience, or equivalent... - Desired Qualifications: list of many items. - Job Expectations: Ability to work a schedule that will include Saturdays; This position is not eligible for Visa sponsorship. - Posting Location(s): address. - Posting End Date. - Also mention "We Value Equal Opportunity" etc but that's boilerplate to remove. - Also mention "Living the Well Life" etc but that's generic benefits? It mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's benefits and compensation info. So we can include Benefits and Pay sections if they have specific content. It says: "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 somewhat generic but mentions robust benefits, competitive compensation, programs for work-life balance. Could be considered benefits and pay. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state robust benefits, competitive compensation, programs for work-life balance. So we can include Benefits and Pay sections with that content. Schedule: they mention ability to work a schedule that will include Saturdays. So we can include Schedule section. We must not repeat job title as heading. No Job ID/requisition numbers as headings; we can fold minor metadata into short p or drop it. So we can include location and posting end date in a p maybe under a generic "Details" but we shouldn't create a heading unless we have content. Could just include a

with location and end date. We must not include boilerplate like EEO, drug policy, etc. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to extract: About the role: The paragraph under "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 prose; we can put in

  . Responsibilities: The list under "In This Role You Will". Each sentence starts with a verb. We can make each as

• . Need to preserve all detail. Let's list them: - 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 9 items. Requirements: The "Required Qualifications:" line: "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. Could be a

  or

  . Since it's a single statement with subitems, we could make a
  with one
  • containing the statement, or just a

    . Probably better as

    . Desired Qualifications: many bullet-like statements. We could treat as Skills or Qualifications. The instruction: Use sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications (maybe under Requirements). Desired Qualifications could go under Qualifications or Skills. Since they are desired qualifications, we could put under Qualifications. Or we could split: Requirements = required, Qualifications = desired, Skills = maybe some of the desired that are skill-based. But we should not create thin sections. Better to combine desired qualifications into Qualifications section as a list. Thus: - Requirements: required qualifications (6+ months etc.) - Qualifications: desired qualifications list (many items) - Skills: maybe we could extract skill-specific items from desired qualifications, but many are skills already. Could just put desired qualifications under Qualifications and not have Skills section if it's thin. But we have many items; we could still have Skills section if we want to separate skill-based items. However instruction: Prefer a few substantive sections over many thin ones. So maybe we just have Requirements and Qualifications (covering desired). Then Benefits, Pay, Schedule. But we also have "Job Expectations: Ability to work a schedule that will include Saturdays; This position is not eligible for Visa sponsorship". The schedule part goes to Schedule section. Visa sponsorship note maybe not needed; could be omitted as minor metadata? It's not a heading; we could fold into a

    under Schedule or just drop. Probably include schedule note. Benefits: from "Living the Well Life" paragraph: robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being, rewarded for investing in community, celebrated for being authentic self, empowered to grow. Also mention "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 more about recognition. Could be part of Benefits or separate but we can include in Benefits. Pay: competitive compensation mentioned. Could be under Pay. Thus we can have:

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

    Benefits

    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. Wells Fargo has been recognized as a top-five workplace on the 2026 LinkedIn Top Companies list for best workplaces "to grow your career" in the U.S.

    Pay

    Competitive compensation is offered as part of the Wells Fargo total rewards package.

    Schedule

    Ability to work a schedule that will include Saturdays.

    We might also include location and posting end date as a

    maybe under a generic "Details" but we shouldn't create a heading unless we have content. Could just add a

    at the end:

    Posting location: 8750 Highway 6 S, Houston, TX 77083. Posting end date: 28 Sep 2026.

    We must not include boilerplate like EEO, drug policy, etc. Check that we didn't repeat job title as heading. Good. Check that we didn't put Job ID/requisition numbers as headings. We didn't. Check that we didn't create sections with filler like "commensurate with experience". We didn't. Check that we preserved all substantive information: we captured about role, responsibilities, required qualifications, desired qualifications, benefits, pay, schedule, location, end date. Did we miss any? The "Job Expectations" also had "This position is not eligible for Visa sponsorship". We omitted that; maybe we should include it as minor metadata. Could fold into a

    under Schedule or a separate note. Since it's not a heading, we can add a

    after Schedule:

    This position is not eligible for Visa sponsorship.

    That preserves info. Also we missed the sentence: "As a Teller, you will build foundational banking skills while learning about customers' needs and introducing them to helpful products, services, and digital tools." That's already in About the role paragraph; we included that. Check that we didn't miss any responsibilities: we captured all nine. Check that we didn't miss any desired qualifications: we captured all listed. Check that we didn't miss any benefits: we captured robust benefits, competitive compensation, programs for work-life balance, community investment, authentic self, empowerment, recognition. Good. Check that we didn't miss any pay: we mentioned competitive compensation. Check schedule: we included ability to work schedule that will include Saturdays. Check location and end date: we added. Check that we didn't include any boilerplate: we omitted EEO, drug policy, third-party recordings, etc. Now output only HTML fragment, no /, no markdown fences. Let's craft final HTML. Be careful to escape any special characters? Not needed. We'll output:

    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