Teller Part Time Charlotte

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 need to parse the posting. The posting includes: - Intro about Wells Fargo (company description) – maybe "About the role"? Actually "About This Role" heading present. So we can put that under

About the role

with prose. - Then "In This Role You Will" list of duties – that is responsibilities. - Then "Required Qualifications:" and "Desired Qualifications:" – these are qualifications. Could separate into Requirements? The instructions: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have "Required Qualifications:" and "Desired Qualifications:" – these are qualifications. Could also treat "Job Expectations:" as maybe Requirements? But we have "Job Expectations: Ability to work a schedule that will include Saturdays". That's schedule info. We also have "Posting Location(s):" etc – minor metadata, can be short p. We have no explicit Benefits, Pay details besides generic statement earlier: "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 a description of benefits and compensation but not specific. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention robust benefits, competitive compensation, programs for work-life balance. That's somewhat generic but still states benefits and compensation exist. However the instruction says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The text "robust benefits, competitive compensation" is not placeholder; it's a statement. So we could include Benefits and Pay sections with that content. However we need to see if there is specific detail: It says "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." That's somewhat generic but still substantive. We could include Benefits: robust benefits, programs for work-life balance. Pay: competitive compensation. Might be acceptable. Schedule: "Ability to work a schedule that will include Saturdays" under Job Expectations. So we can include Schedule section with that. Now we need to avoid repeating job title as heading. Not include Job ID etc. We need to remove boilerplate: EEO, legal, etc. Also remove navigation, cookie, etc. Also remove duplicated lines. We need to preserve all substantive information. Let's extract substantive content: Company 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 substantive. 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." In This Role You Will: list bullet points (the sentences after). We'll convert to

• . 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: list of many bullet-like sentences. Job Expectations: "Ability to work a schedule that will include Saturdays" Posting Location(s): "8700 J M Keynes Dr Charlotte, NC 28262-8427 @RWF22" Posting End Date: "23 Sep 2026" Job posting may come down early due to volume of applicants. (maybe minor, could drop as boilerplate? It's not EEO but maybe still considered administrative. Might drop.) We also have "We Value Equal Opportunity" etc – drop. Now map to headings: - About the role: combine company intro and About This Role? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need separate headings for each. We could put company intro under About the role? Actually About the role likely refers to description of the role, not company. But we have both company description and role description. Could split: About the role could be the "About This Role" paragraph. Company intro could be maybe a brief preamble but not a heading. Since we need to output only HTML fragment, we could include a

  for company intro before any heading? The instruction didn't forbid that. It said use

  for section headings. It didn't say we cannot have prose outside headings. So we can start with a

  containing the company intro (Why Wells Fargo...). Then

  About the role

  with the About This Role paragraph. Then

  Responsibilities

  with the In This Role You Will list. Then

  Qualifications

  with Required and Desired qualifications (maybe combine). Could also split into Requirements and Qualifications but we have only Qualifications heading. The instruction list includes Requirements and Qualifications separate. We could put Required Qualifications under Requirements heading, and Desired Qualifications under Qualifications heading. But we need to decide. We have both Required and Desired. Could treat Required as Requirements, Desired as Qualifications. That seems logical. Thus: -

  Requirements

  with Required Qualifications paragraph. -

  Qualifications

  with Desired Qualifications list. Then Skills: we could extract skills from Desired Qualifications? But we already have Qualifications. The instruction includes Skills heading separate. We could maybe put some skill-based items under Skills. But we risk duplication. Better to follow the instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should attempt to fill each if we have content. We have content for About the role (role description). Responsibilities (list). Requirements (required qualifications). Qualifications (desired qualifications). Skills maybe we can pull out skill statements from desired qualifications: strong verbal communication, active listening, ability to follow policies, cash-handling, etc. But those are already in qualifications. Could still create Skills section with those skill statements. However we must not invent or summarize away detail; we can just move some bullet points to Skills. But we need to preserve all substantive information; moving is okay as long as we keep the info. Benefits: we have statement about robust benefits, programs for work-life balance. Pay: competitive compensation. Schedule: ability to work schedule that includes Saturdays. We also have location and posting date; we can put them in a

  after headings maybe as metadata. We must not include boilerplate like EEO, drug policy, etc. Now craft HTML. Start with company intro

  . Then

  About the role

  ... (About This Role paragraph).

  Then

  Responsibilities

  • ... each bullet.
  We need to extract bullet points from "In This Role You Will". The text after that heading includes multiple sentences each starting with a verb. 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. We'll put each as
• . Now Requirements: Required Qualifications paragraph: "6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education". We'll put as

  . Qualifications: Desired Qualifications list. The text after "Desired Qualifications:" includes many sentences each starting with a capital letter. Let's list them: - 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
  . Now Skills: we could extract skill statements from Desired Qualifications that are more skill-oriented: strong verbal communication and active listening skills; ability to follow policies; proven cash-handling experience; professional integrity-driven approach; ability to recognize risk; ability to understand customer needs; strong collaboration and relationship-building skills; organized and adaptable; ability to resolve routine concerns. But that's basically same as qualifications. To avoid duplication, maybe we can skip Skills section if no distinct content. But instruction says prefer a few substantive sections over many thin ones. If we create Skills with same content as Qualifications, it's thin duplication. Better to omit Skills if not distinct. However the instruction list includes Skills as possible heading but not required. We can omit if