Teller Part Time Weaver Lake Road

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Must not include placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Here we have Pay Range: $23.00 - $28.50. Benefits listed. Schedule: "Ability to work a schedule that will include Saturdays". So we can include Schedule section. We need sections: About the role (maybe from "About This Role" paragraph). Responsibilities (list from "In This Role You Will ..." bullet points). Requirements (maybe "Required Qualifications:" and "Job Expectations:"? Actually Job Expectations includes schedule and visa sponsorship note; we can treat schedule separate. Requirements could be "Required Qualifications:" and maybe "Desired Qualifications:"? But we have separate sections for Qualifications and Skills. The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About This Role: paragraph about role. - In This Role You Will: list of duties (responsibilities). So Responsibilities section. - Required Qualifications: list (6+ months interacting with customers experience, or equivalent...). That's Requirements? Could be Requirements. - Desired Qualifications: list of many items (experience in customer-facing roles, strong attention to detail, etc.) Could be Qualifications or Skills. The headings: Qualifications and Skills separate. We need to decide what goes where. Typically Qualifications could be required/desired qualifications; Skills could be specific skills like communication, cash-handling, etc. But we have both lists overlapping. Perhaps we put Required Qualifications under Requirements, Desired Qualifications under Qualifications, and then maybe extract skills from Desired Qualifications into Skills? But we must not invent or summarize away detail; we must preserve all substantive information. We could keep Desired Qualifications as Qualifications section, and then maybe Skills section could be empty? But we must not emit a heading followed by filler/placeholder text. So we cannot have a Skills section with no content. So we need to decide if we have specific skills content separate from qualifications. The Desired Qualifications list includes many skill-like items: strong verbal communication, active listening, ability to follow policies, proven cash-handling experience, ability to build accuracy, professional integrity-driven approach, ability to recognize risk, ability to understand customer needs, identify referral opportunities, educate on digital tools, strong collaboration, organized and adaptable, ability to resolve routine concerns. Those are skills. So we could put those under Skills heading. Meanwhile Qualifications heading could contain the Required Qualifications? But we already used Requirements for required qualifications. Hmm. We could treat: - Requirements: Required Qualifications (6+ months experience etc.) - Qualifications: Desired Qualifications (list of experience, etc.) but that overlaps with skills. - Skills: maybe we could extract specific skill statements from Desired Qualifications that are skill-focused, but we would be splitting the list, potentially losing some info if we don't include all. But we must preserve ALL substantive information; we cannot omit any detail. So we need to include all content from Desired Qualifications somewhere. If we split into Qualifications and Skills, we must ensure we include all items, not missing any. Could duplicate? Duplication is not prohibited but we should avoid duplicated lines. Better to keep Desired Qualifications under Qualifications heading, and not have a Skills section (since we don't have separate skill content beyond that). However the instruction says we can have Skills section if posting actually states them. It does state skills implicitly but not as a separate "Skills" heading. The posting does not have a explicit "Skills" section; it's embedded in Desired Qualifications. Should we create a Skills heading? The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating a Skills section if it would be thin or just a subset. Better to keep Qualifications heading containing the Desired Qualifications list (which includes skill-like items). Then we don't need a separate Skills heading. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include Job ID etc. Also we must not include "Posting Location(s):" maybe we can keep location as part of a short paragraph? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Location is minor metadata; we could include it in a short p under About the role maybe. But we must preserve ALL substantive information; location is substantive? It's location of job. Might be considered substantive. We could include it in a paragraph after About the role. But we must not create a heading for it. So we can add a

with location. Also "Posting End Date: 22 Sep 2026" is metadata; could be folded into a short p or dropped? It's substantive? Might be considered minor metadata; we could drop? The instruction says preserve ALL substantive information; does posting end date count as substantive? Probably yes, but it's minor metadata. Could include in a short p. We also have "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." That's substantive about pay; we should include that in Pay section. Benefits: list of benefits. Schedule: "Ability to work a schedule that will include Saturdays". Also "This position is not eligible for Visa sponsorship" maybe could be under Requirements? It's a job expectation. Could be part of Requirements or a separate note. We'll include under Requirements maybe as a bullet. Now we need to output HTML fragment only, no /, no markdown. We'll 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.

Location: 13765 83rd Way, Maple Grove, MN 55369

Posting end date: 22 Sep 2026

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.

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
• Ability to work a schedule that will include Saturdays
• This position is not eligible for Visa sponsorship

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.

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

Pay

$23.00 - $28.50 base pay range. 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.

Schedule

Ability to work a schedule that will include Saturdays.

Check for any duplicated content: Schedule appears also in Requirements; we have duplicated the schedule bullet. Might be considered duplication. We should avoid duplicating lines. The schedule appears both as a requirement and as schedule section. We could keep schedule only under Schedule section and remove from Requirements. But the requirement list includes schedule as a job expectation; we could keep it there but then schedule section would be duplicate. Better to keep schedule only under Schedule section and not duplicate. However the requirement list also includes "Ability to work a schedule that will include Saturdays" which is a requirement. If we remove it from Requirements, we lose that requirement info. But we could keep it in Requirements and not have a separate Schedule section, but we have schedule info anyway. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". We have schedule content, so we could have Schedule section. But we must avoid duplication. We could keep schedule only under Schedule section and not list it under Requirements. However the requirement list also