Teller FRIDLEY, 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. Remove boilerplate. We need to parse the posting. First, "Why Wells Fargo" is marketing fluff; we can include as "About the role"? Actually "About this role:" is present. So we can put that as About the role section. Responsibilities: The bullet list under "In this role you will:" includes many duties. Those are responsibilities. Requirements: "Required Qualifications:" line. Desired Qualifications: maybe "Qualifications" or "Skills". We have both required and desired. Could combine into Qualifications section. Skills: maybe separate? The desired qualifications include many skill statements. Could put under Skills. Benefits: The posting lists benefits after "Benefits Wells Fargo provides eligible employees...". So we have Benefits section. Pay: The posting includes "$23.00 - $28.50" and description. So Pay section. Schedule: The posting includes "Ability to work a schedule that will include Saturdays" under Job Expectations. That's schedule info. So Schedule section. We need to avoid repeating job title as heading. No Job ID. We need to use

for each section heading. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We must not include boilerplate like EEO, equal opportunity, etc. Also remove "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. Also remove "Reference Number". Also remove "Job Expectations" maybe we incorporate schedule. We need to include the location? The posting includes "Posting Location(s): 6315 University Ave NE FRIDLEY, MN 55432 @RWF22". That's location metadata; maybe we can fold into a short

  under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include location in a short paragraph. Also "Pay Range Reflected is the base pay range offered for this position..." we can include in Pay section. Now let's extract content. About the role: The paragraph after "About this role:" includes description: "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." We can put that as prose

  . Responsibilities: The list under "In this role you will:" includes multiple bullet-like sentences. We'll convert each to

• . 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. We need to ensure we keep all details. Requirements: "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 the requirement. We could also include "Desired Qualifications:" as part of Qualifications or Skills. Let's treat Qualifications section to include both required and desired? The instruction: Use headings for Requirements, Qualifications, Skills. So we can have Requirements (required), Qualifications (desired?), Skills (skill statements). But we need to avoid thin sections. Perhaps combine required and desired into Qualifications, and put skill statements under Skills. However the desired qualifications list includes many skill-like statements. Might be better to have Requirements (required), Qualifications (desired), Skills (maybe not needed). But we need to avoid empty sections. Let's examine 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 skill statements. Could be placed under Skills. Thus: Requirements: required qualifications (6+ months...). Qualifications: maybe we could put "Desired Qualifications" as a heading? But the instruction says use headings for Qualifications (maybe generic). We'll put

  Qualifications

  and list the desired qualifications as
  • ... . Skills: maybe we could omit if we already used Qualifications for desired. But we need to avoid thin sections. Could combine desired qualifications and skills into one Qualifications section. However the instruction says we can have sections for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It's okay to have Qualifications and Skills both if they have content. But we need to decide content. We could treat Qualifications as "Desired Qualifications" (the list) and Skills as maybe "Key Skills" extracted from same list? That would duplicate. Better to put desired qualifications under Qualifications, and maybe Skills section could be empty -> we must not emit empty heading. So we should not include Skills if we don't have distinct content. But we have many skill statements; they could be considered Skills. However the desired qualifications already are skill-based. Could we split: Qualifications = education/experience requirements (maybe required + desired experience), Skills = abilities like communication, cash-handling, etc. But the required qualifications only mention experience; desired qualifications list many skill statements. So we could put Qualifications = desired qualifications (experience in customer-facing roles, etc.) and Skills = the specific skill statements (communication, cash-handling, etc.) but they overlap. Given the instruction to prefer a few substantive sections over many thin ones, maybe we combine Qualifications and Skills into one Qualifications section that includes both desired qualifications and skill statements. But then we would have only Requirements, Qualifications, Benefits, Pay, Schedule, About the role, Responsibilities. That's fine. Thus we will have: - About the role (prose) - Responsibilities (ul) - Requirements (ul? Actually it's a single sentence; we can still use

    or

    • . The instruction: Use
      • for any list of duties/requirements/benefits. For a single item, we could still use
        • or

          . Safer to use

          for prose. But it's a requirement; we can put

          . - Qualifications (ul) containing desired qualifications list (the bullet points). We'll treat each bullet as

        • . - Benefits (ul) containing list of benefits. - Pay (p) containing pay range and description. - Schedule (p) containing schedule expectation. We also need to include location maybe as a short p under About the role or separate? Could add a short p after About the role: "Location: 6315 University Ave NE, Fridley, MN 55432". That's minor metadata. Now ensure we don't include boilerplate: remove EEO, etc. Also remove "Posting End Date", "Job posting may come down early", "We Value Equal Opportunity", etc. Also remove "Reference Number". Also remove "Job Expectations" (we used schedule). Also remove "Ability to work a schedule that will include Saturdays" we used. Now let's craft HTML. We'll start with

          About the role

          then

          ... plus location p maybe. Then

          Responsibilities

          with li. Then

          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

          Then

          Qualifications

          with each desired qualification. Then

          Benefits

          with benefits list. Then

          Pay

          $23.00 - $28.50 base pay range; pay may vary depending on factors including demonstrated prior performance, skills, experience, or work location; employees may also be eligible for incentive opportunities.

          Then

          Schedule

          Ability to work a schedule that will include Saturdays.

          Check that we preserved all substantive information. Let's verify we didn't miss any details: From About this role: we captured all sentences. Responsibilities: captured all bullet points. Requirements: captured required qualifications. Qualifications: we need to include all desired qualifications bullet points exactly as in text. Let's list them exactly: - 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. Check we didn't miss any: The original also had "