Teller Part Time Rosewick

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Must not include sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. Let's parse the posting: - 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..." This is about company culture, benefits, etc. Could be part of "About the role"? Actually "About this role:" heading appears later. The intro is more about Wells Fargo overall; could be considered "About the role"? But we have a section "About the role" maybe we can put that content there. However the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include an "About the role" section with description of role and maybe company overview. We need to preserve all substantive information: The posting includes: - 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. - Then "In this role you will:" list of duties (bullet points). Those are responsibilities. - 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 points. - Job Expectations: Ability to work a schedule that may include most Saturdays. This position is not eligible for Visa sponsorship. Posting Location(s): 100 Rosewick Rd. LA PLATA, MD 20646 @RWF22 - Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities. $24.00 - $31.00 - Benefits: list of benefits. - Posting End Date: 29 Sep 2026 * Job posting may come down early due to volume of applicants. - Then EEO etc which we must remove. We need to decide sections: - About the role: Could include the introductory paragraph about Wells Fargo and the role description (the "About this role:" paragraph). Might also include location? But location maybe part of metadata; we could include in a short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So location can be a short p. - Responsibilities: the list under "In this role you will:" (the bullet points). Use

• . - Requirements: maybe combine Required Qualifications and Desired Qualifications? The instruction says we can have sections Requirements, Qualifications, Skills. We need to decide what to put where. Typically "Required Qualifications" and "Desired Qualifications" could go under Requirements or Qualifications. Since we have both, we could put Required Qualifications under Requirements, Desired Qualifications under Qualifications (or Skills). But we also have many desired qualifications that are skills. Could split: Requirements = Required Qualifications; Qualifications = Desired Qualifications; Skills maybe not needed if covered. But we must not create sections with filler. We have content for Requirements and Qualifications, so we can include both. - Skills: maybe we could extract skill-based items from desired qualifications, but we already have Qualifications section; we could omit Skills to avoid thin sections. - Benefits: we have list. - Pay: we have pay range. - Schedule: we have "Ability to work a schedule that may include most Saturdays". That's schedule info. Also maybe mention not eligible for visa sponsorship? That's not schedule. So we can create Schedule section with that sentence. We must not include sections like "About the role" if we don't have content; we do have content. We must not repeat job title as heading. We must not include boilerplate like EEO, disability, drug policy, etc. We must not include "Posting End Date" maybe considered metadata; could be folded into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Posting End Date is minor metadata; we can include in a short p or drop. Probably drop it to keep concise. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, required qualifications, desired qualifications, benefits, pay, schedule, location maybe. We must not include "commensurate with experience" etc. Not present. Now craft HTML. 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.

  Maybe also include the introductory "Why Wells Fargo..." paragraph? That is about company culture, could be part of About the role as well. But we already have a lot; we could add it before the role description. The instruction: preserve ALL substantive information. So we should include that intro as well. Let's include it in About the role section, maybe as a preceding paragraph. Thus About the role section will have two paragraphs: first the "Why Wells Fargo..." paragraph, then the role description. Now Responsibilities:

  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.
  Now Requirements (Required Qualifications):

  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

  Now Qualifications (Desired Qualifications):

  Qualifications

  • 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 Benefits:

  Benefits

  • Health benefits
  • 401(k) Plan
  • Paid time off
  • Disability benefits
  • Life insurance, critical illness insurance, and accident insurance
  • Parental leave
  • Critical caregiving leave
  • Discounts and savings
  • Commuter benefits
  • Tuition reimbursement
  • Scholarships for dependent children
  • Adoption reimbursement
  Now Pay:

  Pay

  $24.00 - $31.00 (base pay range; may vary depending on prior performance, skills, experience, or work location; incentive opportunities may also be available)

  We need to preserve the exact wording: "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities. $24.00 - $31.00". We should keep that. So we can put a p with that sentence. Now Schedule:

  Schedule

  Ability to work a schedule that may include most Saturdays.

  We could also include the note about visa sponsorship? That's not schedule; maybe we could drop as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Visa sponsorship note is not schedule but maybe minor metadata; we could drop it. However it's substantive? It's about eligibility; maybe we could include in a short p under About the role or separate? But we have no section for "Eligibility". Could add a short p after schedule? But we must not create sections with filler. Could add a p under About the role? Might be okay to add a short p after schedule? But we already have schedule section; we could add another p under schedule? Might be messy. Better to drop the visa sponsorship note as minor metadata.