Teller Part Time Hartford

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

for each heading. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. 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 general company description; could be part of "About the role"? Actually "About This Role" heading appears later. The intro is more about company; we could put under "About the role" maybe. But we need to follow 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 the company description plus maybe the role overview. Then "About This Role" section: "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" bullet list: list of duties. Those are responsibilities. So we can put under Responsibilities. Then "Required Qualifications:" line: "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 a qualification. Then "Desired Qualifications:" list of many bullet-like sentences. Those could be split into Requirements, Qualifications, Skills. We need to decide mapping. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to allocate content appropriately, not invent sections. We have: - About the role: company description + role overview (maybe combine both intros). Could be just the "About This Role" paragraph. - Responsibilities: the bullet list under "In This Role You Will". Also maybe some duties from earlier paragraphs? But we can include those bullet points. - Requirements: maybe the "Required Qualifications:" line. - Qualifications: maybe the "Desired Qualifications:" list? But that includes many items that could be skills or qualifications. We could split: Qualifications for desired qualifications (like experience, etc.) and Skills for specific skill items. But we must not create sections with filler. We need to ensure each section has real specific content. Let's extract Desired Qualifications list: "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." These are a mix of qualifications and skills. We could put them under "Qualifications" (maybe as a list) and also have a "Skills" section for specific skill items like communication, cash handling, etc. But to avoid duplication, we could put all under "Qualifications" and skip Skills if not enough distinct content. However instruction says prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But we have to use headings exactly as given? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; we include only those with real content. So we could include Qualifications and maybe not Skills if content overlaps. But we need to decide. We also have Job Expectations: "Ability to work a schedule that will include Saturdays". That's schedule info. Also "This position is not eligible for Visa sponsorship". That's maybe metadata; we could drop or put in a short p. Pay: "$22.00 - $27.50" plus description: "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." Benefits: list: "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". Also mention "Visit Benefits - Wells Fargo Jobs for an overview..." We should include Benefits section with that list. Schedule: we have "Ability to work a schedule that will include Saturdays". That's the only schedule info. Could also mention maybe typical branch hours? Not given. So we can include Schedule section with that statement. Now we need to ensure we don't include boilerplate like "Posting End Date:", "Job posting may come down early...", "We Value Equal Opportunity", etc. Remove those. Also remove "Posting Location(s): 10 State House Sq HARTFORD, CT 06103-3604 @RWF22". Could be minor metadata; we could fold into a short p or drop. Probably drop as not essential. Also remove "Pay Range Reflected is the base pay range offered for this position..." Actually that's part of pay description; we keep. Now we need to output only HTML fragment, no /, no markdown fences. Structure:

About the role

... company description + role overview ...

Responsibilities

• ...
...

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

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.

We could also have Skills section but maybe not needed. However we have many skill-like items; but we already put them under Qualifications. Could we split into Qualifications and Skills? The instruction says prefer a few substantive sections over many thin ones. So maybe keep Qualifications only and omit Skills. 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

Pay:

Pay

$22.00 - $27.50 base pay range; pay may vary based on prior performance, skills, experience, or work location; employees may also be eligible for incentive opportunities.

Schedule:

Schedule

Ability to work a schedule that will include Saturdays.

We might also include a short p for Job Expectations about Visa sponsorship not eligible; but that's minor metadata; could drop. Now check for any duplicated lines: we have not included the intro "Why Wells Fargo..." etc. We included company description in About the role. Let's craft About the role paragraph: We can combine the initial company description and the "About This Role" paragraph. About the role paragraph: "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! 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