Teller Part Time Village Oaks

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. We must not repeat job title as heading. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, cookie/navigation, etc. Must not create sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. Let's 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; could be considered "About the role"? Actually it's about company. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have "About This Role" heading in posting: "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 is suitable for "About the role". So we will create

About the role

and then a

with that content. Next: "In This Role You Will" list of duties. That is responsibilities. So

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. We need to ensure we keep all details. Next: "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" etc. We need to decide headings: 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" Desired Qualifications: a list of many items. Job Expectations: "Ability to work a schedule that will include Saturdays" and "This position is not eligible for Visa sponsorship". Also location and posting location. Pay: "$20.00 - $26.00" plus description. Benefits: list of benefits. Schedule: maybe from Job Expectations about schedule includes Saturdays. We need to decide which headings to use. We have content for Requirements (maybe Required Qualifications). We have content for Qualifications (maybe Desired Qualifications). We have content for Skills (maybe many of the desired qualifications are skills). Could combine. But instruction: Prefer a few substantive sections over many thin ones. So we might combine Required and Desired qualifications into a single "Requirements" section? Or separate "Requirements" and "Qualifications"? The headings list includes both Requirements and Qualifications. We could put Required Qualifications under Requirements, Desired Qualifications under Qualifications. That seems appropriate. Skills: maybe we could extract skill-based items from desired qualifications (communication, active listening, cash handling, etc.) but many are already there. Could create Skills section summarizing skill items. But we might avoid thin sections. Pay: we have pay range. Schedule: we have ability to work schedule that includes Saturdays. Benefits: we have list. We must not create sections with filler like "commensurate with experience". Not relevant. We must not include boilerplate like EEO, disability, drug policy, etc. We must not include navigation, cookie, etc. We must not include Job ID/requisition numbers as headings; we can fold minor metadata into short

  or drop it. So we can include location maybe in a paragraph under About the role or separate? The location is "Posting Location(s): 8000 White Lane Blvd Ste A Bakersfield, CA 93307 @RWF22". That's minor metadata; we could include as a short

  after About the role maybe. Also "Posting End Date: 30 Oct 2026" and "Job posting may come down early due to volume of applicants." That's also metadata; we could drop or include as short p. We need to preserve ALL substantive information; but we can drop minor metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can either drop or include as short p. Probably better to include location and maybe end date as a short p under About the role or separate. We must not repeat job title as heading. Now let's craft HTML. We'll start with

  About the role

  then

  containing the About This Role paragraph plus maybe location and end date as separate short p? Could combine. Better: After About the role paragraph, add a

  with location and posting end date. But we need to avoid duplication: The location line includes "@RWF22" which maybe is a code; we can keep. Now Responsibilities:

  Responsibilities

  with each duty as
  • . Now Requirements:

    Requirements

    containing Required Qualifications text. Now Qualifications:

    Qualifications

    with Desired Qualifications items. Now Skills: maybe we could extract skill items from Desired Qualifications that are skill-focused: Strong verbal communication and active listening skills, Ability to follow policies..., Proven cash-handling experience, Demonstrated ability to quickly build accuracy..., Professional, integrity-driven approach..., Ability to recognize potential risk..., Ability to understand customer needs..., Strong collaboration and relationship-building skills..., Organized and adaptable..., Ability to resolve routine customer concerns... These are more like skills/competencies. Could put them under Skills. But we already have Qualifications list; maybe we can combine Qualifications and Skills into one? But headings list includes both; we could put Qualifications for desired qualifications (experience, etc.) and Skills for skill-based items. However many desired qualifications are skill-based; splitting may cause thin sections. But we can still make them substantive. Let's decide: We'll put Desired Qualifications under Qualifications as a list (since they are qualifications). Then we can omit Skills section (or combine). But we need to include Skills heading only if we have real specific content. We could extract skill-specific items and put under Skills, leaving Qualifications for experience/education. Let's see. Desired Qualifications 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. We could treat first item as experience (customer-facing roles) maybe under Qualifications. The rest are skills/competencies. Could split: Qualifications: experience in customer-facing roles, 6+ months interacting with customers (required) plus maybe education etc. But we already have Required Qualifications separate. Given the instruction to prefer few substantive sections, maybe we combine Required and Desired into one "Requirements" section, and then have a "Skills" section for skill-based items. But we already have Responsibilities covering duties. Could also have "Qualifications" for both required and desired, and skip Skills. But we need to follow the headings list; it's okay to omit some headings if no content. So we can have About the role, Responsibilities, Requirements (combined required+desired), Benefits, Pay, Schedule. That's 6 sections. Let's see if we have content for Schedule: "Ability to work a schedule that will include Saturdays". That's specific. Also maybe "Job Expectations: Ability to work a schedule that will include Saturdays". So we can create Schedule section with that sentence. Pay: we have "$20.00 - $26.00" plus description about base pay range, may vary, incentive opportunities. That's substantive. Benefits: list of benefits. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to remove boilerplate: EEO, disability, drug policy, recruitment requirements, reference number, etc. Also remove lines like "We Value Equal Opportunity", "Employees support our focus...", "Applicants With Disabilities", "Drug and Alcohol Policy", "Wells Fargo Recruitment And Hiring Requirements", "Third-Party recordings are prohibited...", "Reference Number R-575418". Also remove "Posting End Date: 30 Oct 2026" maybe we can keep as minor metadata? Could drop. But we might include as short p under About the role? The instruction says fold minor metadata into a short

    or drop it. So we could include location and