Teller Village at Sandhill

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, EEO, etc. Must preserve all substantive info. 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 about company, could be "About the role"? Actually "About this role:" later. The intro is more about company. Could be part of "About the role"? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and maybe company overview? The posting includes "About this role:" then description. So we can put that under About the role. Then responsibilities: The bullet list after "In this role you will:" includes many items. Those are responsibilities. Then "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" etc. We need to map to sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - Responsibilities: list of duties (the "In this role you will:" items). Use

• . - Requirements: maybe "Required Qualifications:" and "Job Expectations:"? Or "Required Qualifications" is requirements. "Desired Qualifications" could be skills? Or we could have Qualifications section combining required and desired? The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide distribution. We could put: - About the role: company intro + role overview (the paragraph after "About this role:" maybe). - Responsibilities: the list of duties. - Requirements: Required Qualifications (6+ months interacting with customers experience, etc.) - Qualifications: Desired Qualifications (the list of desired qualifications). Or maybe Qualifications is for required, Skills for desired? But we have both Requirements and Qualifications sections; we can treat Requirements as mandatory, Qualifications as preferred. - Skills: maybe we can extract skills from desired qualifications (strong verbal communication, active listening, etc.) but they are already in desired qualifications. Could put them under Skills. - Benefits: The posting mentions robust benefits, competitive compensation, programs for work-life balance, etc. In the intro: "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." Also later: "You’ll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow." Also mention recognition. So we have some benefits info. We should include Benefits section with that content. - Pay: The posting does not give specific pay. It mentions competitive compensation but no numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "competitive compensation" but not specific pay. Is that enough? The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive compensation" is vague but still a statement about pay. However it's not a specific number or range. Might be considered filler? The rule says avoid placeholder like "commensurate with experience". "competitive compensation" is similar vague. I'd interpret that we should not create a Pay section unless there is actual pay info (like salary range, hourly rate). Since none given, we omit Pay section. - Schedule: The posting includes "Job Expectations: Ability to work a schedule that will include Saturdays". That's schedule info. So we can include Schedule section with that. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We must not include Pay. Now we need to extract content. About the role: Should include the company intro and role overview? The "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." We could also include the earlier "Why Wells Fargo" paragraph as part of About the role? It's more about company. Might be okay to include under About the role as overview. But we must not repeat job title as heading. It's fine. Thus About the role content: combine the "Why Wells Fargo" paragraph and the "About this role:" paragraph. Ensure we preserve all substantive info, no fluff. Now Responsibilities: list items after "In this role you will:" (the bullet list). Let's extract each: - 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. Now 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 it. Now Qualifications: Desired Qualifications list: many bullet points. Let's extract: - 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. Now Skills: Could we separate some of these as skills? The desired qualifications already include skills. But we have a Skills section; we could put the same list there, but that would duplicate. Perhaps we treat Qualifications as required, Skills as desired. But we already used Qualifications for desired. Let's think: The instruction list includes both Qualifications and Skills as possible headings. We need to decide distribution to avoid duplication and thin sections. We could put Required Qualifications under Requirements, and Desired Qualifications under Skills. Then we would not have a Qualifications section. But we have both Requirements and Qualifications headings allowed; we could use Requirements for required, Qualifications for desired, and omit Skills. Or we could use Requirements for required, Skills for desired, and omit Qualifications. Which is better? The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid having both Qualifications and Skills if they'd be thin. But we have substantial content for desired qualifications; we could put them under Skills. Then we would have Requirements (required) and Skills (desired). That's two sections plus About the role, Responsibilities, Benefits, Schedule. That's 5 sections. That seems good. Thus: - About the role: company intro + role overview. - Responsibilities: list of duties. - Requirements: Required Qualifications. - Skills: Desired Qualifications (list). - Benefits: benefits info from intro. - Schedule: Ability to work a schedule that will include Saturdays. We must not include Pay. Now Benefits: extract from intro: "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." Also maybe mention "robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being." That's benefits. We should not include "competitive compensation" as pay; it's part of benefits description. It's okay. Now Schedule: "Ability to work a schedule that will include Saturdays" from Job Expectations. Also Job Expectations includes "This position is not eligible for Visa sponsorship" and posting location etc. Those are minor metadata; we can drop or fold into short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short p for posting location and end date maybe? But they said drop minor metadata. Safer to drop them. We'll not include location, posting end date, etc. Also drop Visa sponsorship note? It's minor; could drop. We'll focus on substantive. Now we need to output HTML fragment only, no /, no markdown. We'll produce:

  About the role

  ...combined text...

  Responsibilities

  • ...
  ...

  Requirements