Teller Part Time Houston

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. The posting includes: - About this role: description (About this role) -> can map to "About the role" heading. - In this role you will: list of duties -> Responsibilities. - Required Qualifications: list -> Requirements (maybe also Qualifications). Desired Qualifications: list -> could be Qualifications or Skills. We need to decide. - Job Expectations: includes schedule (Ability to work a schedule that will include Saturdays) -> Schedule section. - Benefits: The "Why Wells Fargo" paragraph mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's benefits content. Also mentions compensation but not specific numbers. We should include Benefits section with that prose. Pay: they mention competitive compensation but not specific numbers; we should not create Pay section unless posting actually states them. It says "competitive compensation" but not specific; that's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, they mention robust benefits, programs designed to help you find work-life balance and well-being. That's specific enough? It's a statement about benefits existing. Likely we can include Benefits section with that prose. For Pay, they only say competitive compensation, no specifics; that might be considered not specific enough, so we should not create Pay section. Schedule: they explicitly state ability to work a schedule that will include Saturdays. That's specific, so include Schedule section. - Skills: maybe from Desired Qualifications we can extract skills: strong verbal communication, active listening, ability to follow policies, cash-handling, etc. Could put under Skills. - Qualifications: maybe Required Qualifications and Desired Qualifications combined? But we already have Requirements (maybe Required Qualifications) and Qualifications (maybe Desired). However instruction: prefer a few substantive sections over many thin ones. Could combine Required and Desired into Requirements and Skills? Let's think. We need to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have: - About the role: yes (About this role paragraph). - Responsibilities: yes (In this role you will: list). - Requirements: yes (Required Qualifications list). - Qualifications: maybe Desired Qualifications list could go here. - Skills: maybe we could extract skills from Desired Qualifications but that overlaps with Qualifications. Could we put Desired Qualifications under Qualifications and not have Skills? But we need to decide if we want Skills section. The posting includes many skill-like items: strong verbal communication, active listening, ability to follow policies, cash-handling, ability to build accuracy, professional integrity-driven approach, ability to recognize risk, ability to understand customer needs, identify referral opportunities, educate on digital tools, strong collaboration, organized adaptable, ability to resolve routine concerns. Those are skills. Could make Skills section from Desired Qualifications. Then Qualifications could be maybe empty? Better to have Qualifications for Required Qualifications and Skills for Desired Qualifications? But we already have Requirements for Required Qualifications. So we could map: - Requirements: Required Qualifications. - Skills: Desired Qualifications (skill-focused). - Qualifications: maybe we could omit if no distinct content. But we need to decide if we should include Qualifications heading only if there is real specific content. If we put Desired Qualifications under Skills, then Qualifications would be empty; we should not include it. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Check if Benefits section content: "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." That's benefits description. Also earlier: "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." That's more generic. We'll include the benefits sentence. Schedule: "Ability to work a schedule that will include Saturdays". We'll put that as a

maybe. Now we need to output HTML fragment only, no /. Use

for headings. Use

• for lists. Use

  for prose. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate. We need to preserve all substantive information. Let's extract: 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." That's the About the role content. Responsibilities: list from "In this role you will:" bullet points. Let's capture 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. That's 9 bullets. 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; we can put as

  or maybe as

  • but it's not a list. We'll use

    . Desired Qualifications (Skills): 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. That's 11 bullets. Benefits: from "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." We could include that as Benefits section prose. Might be a bit long but okay. Schedule: "Ability to work a schedule that will include Saturdays" We'll put as

    . Now ensure we don't include any boilerplate like "Why Wells Fargo: Are you looking for more? Find it here." That's part of the intro but maybe we can keep as part of Benefits? Actually that line is more like a tagline; but we already have Benefits section. Could include that line as part of Benefits? It's not exactly benefits but it's marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why Wells Fargo: Are you looking for more? Find it here." is not boilerplate but it's promotional; we could keep it as part of Benefits or maybe as a preamble before About the role? But we already have About the role heading; we could include that line as a

    before About the role? However the instruction says use

    for section headings; we can have multiple

    sections under each heading. The intro could be considered part of About the role? It's more about company. Could be placed under About the role as a preamble. But the About the role heading expects content about the role; we could put that introductory marketing text as a

    under About the role before the role-specific paragraph. That would preserve it. Thus About the role section:

    About the role

    then

    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!

    then

    Wells Fargo is seeking a Teller to join our National Branch Network....

    But we might be duplicating benefits content; we already have Benefits section. However the intro includes benefits description; we could keep it there and not have a separate Benefits section. But we need to decide: The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have benefits content (robust benefits, programs...). So we can have Benefits section with that content. The introductory marketing also includes similar content; we could avoid duplication by not repeating benefits in About the role. But we need to preserve ALL substantive information; we can't omit the introductory marketing text entirely. However we could include it as part of About the role (company overview) and not have a separate Benefits section, but then we would lose the explicit benefits section heading. However the benefits content is still present in the About the role paragraph. That might be acceptable; but we might still want a Benefits section to highlight it. The instruction: Prefer a few substantive sections over many thin ones. Having both About the role and Benefits might be okay if they