Teller Hilton Head North Island

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

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to 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" heading appears later. The intro is about Wells Fargo, not role. We can include as a

  maybe under a heading "About Wells Fargo"? But only allowed headings are listed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We shouldn't add other headings. So we need to fit content into those sections. The intro about Wells Fargo could go under "About the role"? Usually "About the role" describes the role. But we have "About This Role" later. The earlier paragraph is about company culture. Could be considered part of "About the role"? Might be okay to include as prose under "About the role". The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to include a section only when posting has real, specific content for it. So we need to decide which sections have content. We have: - About the role: we have "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's substantive. - Responsibilities: we have "In This Role You Will" bullet list: 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 responsibilities. - Required Qualifications: "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 items. - Job Expectations: "Ability to work a schedule that will include Saturdays" and "This position is not eligible for Visa sponsorship". Also posting location and end date etc. Those could go under Schedule? The schedule: ability to work schedule that includes Saturdays. That's schedule info. Also maybe location not needed. - Benefits: The intro mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's benefits and pay. So we can have Benefits section with those details. Pay: mention competitive compensation but not specific numbers. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention robust benefits, competitive compensation, programs for work-life balance and well-being. So we can include Benefits and maybe Pay? It says competitive compensation but not specific. That's still stating compensation exists. Might be okay to include Pay section with "competitive compensation" but that's vague. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive compensation" is not filler? It's vague but still a statement. Might be acceptable. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being. So we can include Benefits and Pay sections with that info. Schedule: ability to work schedule that includes Saturdays. That's specific enough. Thus we will have sections: About the role, Responsibilities, Required Qualifications, Desired Qualifications (maybe under Qualifications?), Skills, Benefits, Pay, Schedule. But we have both Required and Desired qualifications. Could combine under Qualifications? The instruction list includes Qualifications as a heading. Could split into Required Qualifications and Desired Qualifications as subheadings? But only allowed headings are those exact ones. We could put both under Qualifications heading, with sub-lists maybe using

  or

  . But we need to preserve all info. We could do:

  Qualifications

  Required: 6+ months of interacting with customers experience, or equivalent demonstrated through work experience, training, military experience, education.

  Desired: ... list. That seems okay. Skills: The desired qualifications list includes many skill-like items. Could treat as Skills section. But we already have Qualifications. Might be redundant. However we can still include Skills if we have content. The desired qualifications list includes skills like strong verbal communication, active listening, ability to follow policies, proven cash-handling experience, etc. Those are skills. So we could put Skills section with those items. Then Qualifications could just be required qualifications. But we need to avoid duplication. Let's think: The posting has "Required Qualifications:" and "Desired Qualifications". The desired qualifications are essentially skills and experience preferences. We could treat Required Qualifications as Qualifications section, and Desired Qualifications as Skills section. That seems logical. Thus: - About the role: intro paragraph(s) about role. - Responsibilities: list of duties. - Qualifications: required qualifications (6+ months...). - Skills: desired qualifications list (the bullet items). - Benefits: robust benefits, competitive compensation, programs for work-life balance and well-being. - Pay: maybe we can combine with Benefits? But we have separate Pay heading. Could put competitive compensation there. - Schedule: ability to work schedule that includes Saturdays. We should not include location, posting end date, visa sponsorship note? The visa sponsorship note is "This position is not eligible for Visa sponsorship". That's not a heading; could be placed under Qualifications or maybe as a note. But it's substantive. We could include it under Qualifications as an extra note. Or maybe under Responsibilities? Better to add a

  under Qualifications: "This position is not eligible for Visa sponsorship." But that's not a qualification. Could be under a separate heading? Not allowed. Could add as a

  after Qualifications before Skills. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Visa sponsorship is not minor metadata? It's a condition. Could be placed as a short

  after Qualifications. Also posting location and end date: minor metadata, we can drop or fold into a short

  . Probably drop. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

  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

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

  Qualifications

  Required: 6+ months of interacting with customers experience, or equivalent demonstrated through work experience, training, military experience, or education.

  This position is not eligible for Visa sponsorship.

  Skills

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