Teller Part Time ROCHESTER MN

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 remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key parts: - 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:" follows. So we can put company overview maybe as a paragraph before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. We need to include sections only when posting has real specific content. So we need to decide which sections have content. - About the role: The posting has "About this role:" with description. So we can create

About the role

and then a

with that description. - Responsibilities: The posting includes "In this role you will:" list of duties. So we can create

Responsibilities

with

• items. - Requirements: There's "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" maybe part of requirements. We can combine into Requirements section? The instruction lists separate headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. The posting includes Required Qualifications, Desired Qualifications, Job Expectations (schedule includes Saturdays). Also includes "Ability to work a schedule that will include Saturdays". That's schedule info. We also have Pay: "$20.00 - $26.00" and description about pay range. Benefits: list of benefits. Skills: maybe we can extract from Desired Qualifications etc. But we could also put skills under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we could combine Required and Desired Qualifications into a Qualifications section, and maybe Skills separate? But we have many skill-like items. Could create a Skills section with bullet list of desired qualifications. But we must not create sections with filler like "commensurate with experience". We have actual content. Thus possible sections: - About the role - Responsibilities - Qualifications (combining Required and Desired) - Skills (maybe from Desired Qualifications? but that overlaps) - Benefits - Pay - Schedule But we need to avoid duplication. Let's think: 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 (experience in customer-facing roles, strong attention to detail, ability to accurately process transactions across multiple systems in fast-paced environments, strong verbal communication and active listening skills, 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 essentially skills and qualifications. Could combine into Qualifications section with sub-bullets for required and desired? But we need to follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not mandatory to use all. We can choose which to include. We could have: - About the role - Responsibilities - Qualifications (including required and desired) - Benefits - Pay - Schedule That's 6 sections. Skills could be omitted as part of Qualifications. Check if we have any content for Requirements separate from Qualifications? The posting uses "Required Qualifications" and "Desired Qualifications". So we can treat that as Qualifications. Thus we will not include a separate Requirements heading. Now we need to extract the About the role content: The paragraph after "About this role:" up to before "In this role you will:"? Actually the text: "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 the About this role content. We'll put that in a

  . Now Responsibilities: The list after "In this role you will:" includes bullet-like sentences each starting with a verb. We'll extract each as

  . 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. Now Qualifications: We'll combine Required and Desired. 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 as above. We'll output as

  • for each item. Could separate required and desired? Might be okay to just list all. But we need to preserve all substantive information. So we need to include the required qualification statement exactly. We'll create a
    with two top-level items? Could do:
    • Required: 6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
    Then each desired qualification as separate
    • . Now Benefits: The posting lists benefits after "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below. Visit Benefits - Wells Fargo Jobs for an overview of the following benefit plans and programs offered to employees." Then bullet 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 We'll output as
      • . Pay: The posting includes: "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. $20.00 - $26.00" We'll output a

        with that info. Schedule: The posting includes: "Job Expectations: Ability to work a schedule that will include Saturdays". Also maybe other schedule info? Not much else. So we can create Schedule section with that sentence. We must not include boilerplate like EEO, legal, etc. So we will omit those paragraphs. Also need to drop "Posting Location(s): 3360 55th St NW ROCHESTER, MN 55901 @RWF22" maybe minor metadata; we could fold into a short

        or drop. The instruction: fold minor metadata into a short

        or drop it. Since it's location, could be relevant but not a heading. We could include a

        for location maybe under About the role? But better to drop? The instruction says fold minor metadata into a short

        or drop it. So we could include a short

        with location. However location is not a section heading; we can just add a

        after About the role maybe. Also "Posting End Date: 4 Oct 2026 * Job posting may come down early due to volume of applicants." That's metadata; we could drop or fold into short

        . Probably drop. Also "Reference Number R-577920" drop. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

        About the role

        ... (including location maybe?)

        Responsibilities

        ...

        Qualifications

        ...

        Benefits

        ...

        Pay

        ...

        Schedule

        Ability to work a schedule that will include Saturdays

        Optionally include location paragraph after About the role? Could add a

        Location: 3360 55th St NW Rochester, MN 55901

        but not required. Might be considered minor metadata; we can include as a short

        after About the role. Let's decide to include a short

        for location after About the role. Now ensure we don't repeat job title (Teller) as heading; we didn't. Now check for any placeholders like "commensurate with experience" - none. Now