Teller Part Time Thomasville

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 must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. Must not include placeholder sections like Pay/Schedule/Benefits unless posting actually states them. The posting mentions "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." Also mentions "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." So we have benefits and compensation info. Also schedule: "Ability to work a schedule that will include Saturdays". So schedule is present. Pay: not specific amount, just "competitive compensation". That's vague but maybe considered not specific? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation" and "robust benefits". So we can include Benefits and Pay sections with that content. However "competitive compensation" is vague but it's stated. The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . "competitive compensation" is not exactly filler? Might be considered vague but it's actual statement. I'd include Pay section with that sentence. Also we have "About This Role" paragraph. That's about the role. So we can have

About the role

with that paragraph. Responsibilities: The "In This Role You Will" list of duties. Those are responsibilities. So we can make

Responsibilities

with

• each bullet. Requirements: There's "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" (schedule). Also there are many desired qualifications bullet-like sentences. We need to separate Requirements vs Qualifications vs Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where. Likely: - Requirements: maybe the mandatory qualifications (6+ months interacting with customers experience, or equivalent). Also Job Expectations (schedule) could go under Schedule section. - Qualifications: maybe desired qualifications? Or we could combine Required and Desired under Qualifications? But we have both Requirements and Qualifications headings available. We need to decide distribution. Better: Requirements = Required Qualifications (mandatory). Qualifications = Desired Qualifications (preferred). Skills could be extracted from desired qualifications that are skill-based (communication, attention to detail, etc). But we might just put desired qualifications under Qualifications. Skills maybe not needed if overlapping. But we must not create thin sections. Let's see content: 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 requirement. Desired Qualifications: a long list of bullet-like sentences (each starts with a capital). Those are 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, 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; Ability to understand customer needs, identify referral and service opportunities, and educate customers on digital banking tools; Strong collaboration and relationship-building skills; Organized and adaptable, with ability to prioritize effectively; Ability to resolve routine customer concerns with sound judgment and professionalism. These are skills and qualifications. Could split: Qualifications heading for the desired qualifications list; Skills heading for maybe communication, attention to detail, etc. But many overlap. Given instruction to prefer a few substantive sections over many thin ones, we could combine Desired Qualifications and Skills into one section called Qualifications (or Skills). But we have both headings available; we could use Qualifications for the desired qualifications list, and maybe not use Skills if it would be thin. Alternatively, we could put Required Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe not use Skills. Schedule: we have "Ability to work a schedule that will include Saturdays". So Schedule section with that sentence. Benefits: we have robust benefits, competitive compensation, programs for work-life balance. So Benefits section with that sentence. Pay: we have competitive compensation (already mentioned in Benefits). Could combine Pay and Benefits? But we have separate headings. Could put Pay: "competitive compensation". Benefits: "robust benefits and programs designed to help you find work-life balance and well-being." However the posting says "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." So we could split: Benefits: robust benefits and programs for work-life balance; Pay: competitive compensation. But we must avoid filler. "competitive compensation" is maybe okay. Now About the role: we have the paragraph starting "At Wells Fargo, we're more than a financial services leader..." Actually that's more about company. The "About This Role" section starts after that: "Wells Fargo is seeking a Teller to join our National Branch Network..." So we should use that as About the role content. Thus:

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

  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'll put each as
• . Requirements: Required Qualifications paragraph.

  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: Desired Qualifications list. We'll list each as
• . Let's extract each desired qualification sentence: - 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 Qualifications. Skills: maybe we could omit if thin. But we could combine some skill-specific items under Skills. However many of those are skills. To avoid thin sections, we could skip Skills heading altogether. Benefits: we have robust benefits, programs for work-life balance. Extract: "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." We can split: Benefits: robust benefits and programs designed to help you find work-life balance and well-being. Pay: competitive compensation. Schedule: Ability to work a schedule that will include Saturdays. Now ensure we don't include boilerplate like EEO, etc. Also remove "Job Expectations:" line (we used schedule). Also remove "Posting Location(s):", "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. Also remove "Reference Number". Also remove "At Wells Fargo, we're more than a financial services leader..." that's before About This Role; we might keep that as part of About the role? Actually the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The introductory fluff about Wells Fargo could be considered minor metadata? It's not about the role. Might be considered boilerplate? It's describing company culture. Could be considered part of About the role? But we already have About the role content from "About This Role". The introductory paragraph is more generic company description. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This intro is not exactly those, but it's not specific to the role. Might be okay to keep? However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The intro is substantive about company values. Might be okay to include in About the role section? But we already have About the role content; we could combine both paragraphs. However the instruction about sections: use

  for section headings (e.g. About the role, Responsibilities, etc). So About the role heading should contain the role description. The company intro could be considered part of About the role as well. But we might keep it as a short paragraph before the heading? The instruction says output ONLY the HTML fragment, no /. It didn't forbid extra paragraphs outside headings. But better to include it under About the role. Thus About the role will have two paragraphs: first the generic Wells Fargo description, then the role-specific description. Let's craft:

  About the role

  At Wells Fargo, we're more than a financial