Teller Part Time Broward North

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate, EEO, etc. Must preserve all substantive info. Let's 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 about company culture/benefits. Could be placed under Benefits? But we need to only sections with real specific content. The posting mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's benefits info. Also mentions compensation but not specific numbers. We cannot create Pay section unless posting actually states them (specific pay). It says competitive compensation but no numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being. That's benefits info. So we can include a Benefits section with that content. Pay section: not specific numbers, so we should not include Pay. Schedule: mentions ability to work a schedule that will include Saturdays (under Job Expectations). That's schedule info. So we can include Schedule section. Now "About this role:" section: description of role. That's About the role. Then bullet list of duties: "In this role you will:" followed by list of duties. That's Responsibilities. Then "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" etc. We need to map to sections: Requirements, Qualifications, Skills. The posting includes Required Qualifications (6+ months interacting with customers experience...), Desired Qualifications (list of skills). Also Job Expectations includes ability to work schedule including Saturdays, not eligible for Visa sponsorship. Also posting locations list. We need to preserve all substantive info. So we need to include Required Qualifications, Desired Qualifications, Job Expectations (maybe under Requirements or Qualifications). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have flexibility: we can put Required Qualifications under Requirements heading, Desired Qualifications under Qualifications heading, and maybe Skills under Skills heading (but we might combine). However we must not create sections with filler. We need to decide what content goes where. We have: - About the role: intro paragraph about role. - Responsibilities: list of duties (the "In this role you will:" bullet points). - Requirements: maybe the Required Qualifications (6+ months interacting with customers experience, or equivalent). Also Job Expectations (schedule, visa sponsorship) could be under Requirements? But schedule we already have separate Schedule section. Visa sponsorship note is a requirement (not eligible for Visa sponsorship). Could be under Requirements. - Qualifications: Desired Qualifications list. - Skills: maybe we could extract skills from Desired Qualifications (strong verbal communication, active listening, etc.) but that's already there. Could put Skills heading with those skill items. However we already have Desired Qualifications which includes many skill-like items. To avoid duplication, we could treat Desired Qualifications as Qualifications section, and maybe not have Skills separate unless we have distinct skill list. The posting does not have a separate "Skills" heading; it's embedded. We could still create a Skills section pulling out skill-related items from Desired Qualifications. But we must not invent or summarize away detail; we must preserve ALL substantive information. If we move items to Skills, we still preserve them. It's okay to reorganize as long as we keep all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we can reformat but must keep all info. So we can create sections as we like, as long as we include all info. Thus we can have:

About the role

with paragraph(s) from "About this role:" plus maybe the introductory Wells Fargo culture? Actually the "Why Wells Fargo" part is company overview; could be part of About the role or Benefits. But we already have Benefits section for benefits. The "Why Wells Fargo" includes benefits, culture, recognition. Could be placed under Benefits (since it mentions robust benefits, competitive compensation, programs, recognition). However the instruction says include a section ONLY when the posting has real, specific content for it. The "Why Wells Fargo" includes specific content about benefits, compensation, programs, recognition. So we can put that in Benefits section. The "About this role:" is separate. Thus: - Benefits: include the Wells Fargo culture paragraph (starting "Why Wells Fargo: Are you looking for more? Find it here. At Wells Fargo, we're more than a financial services leader...") plus maybe the sentence about robust benefits, competitive compensation, programs, etc. Also mention recognition ranking. - About the role: the paragraph under "About this role:" describing the Teller role. - Responsibilities: the list under "In this role you will:" each bullet. - Requirements: maybe the Required Qualifications (6+ months interacting with customers experience, or equivalent) plus Job Expectations (ability to work schedule that will include Saturdays, not eligible for Visa sponsorship). Also maybe posting locations? That's location info; could be under Requirements or separate? Not a heading given. Could be placed under Requirements as part of job details. But we have no specific heading for location; we could put it in a paragraph under Requirements or maybe under About the role? Better to keep under Requirements as "Posting Locations:" list. - Qualifications: Desired Qualifications list. - Skills: maybe we could extract skill items from Desired Qualifications but that would duplicate. Could instead put Skills empty? Not allowed. So we might omit Skills section if no distinct skill content beyond what's already in Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if it would be thin. However we have Desired Qualifications which includes many skill-like items; we could treat that as Qualifications and not have Skills. - Schedule: include the schedule expectation (ability to work a schedule that will include Saturdays). Also maybe mention that schedule includes Saturdays. - Pay: not specific, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. Now we need to format using

for each heading, then content:

for prose,

• for lists. We must not include boilerplate like EEO, etc. Remove all that. We must preserve all substantive info: that includes the list of posting locations (multiple addresses). Must keep them. Also must keep the note: "Due to timing and resource needs, positions may not be available at all branch locations outlined in the posting @RWF22 Posting End Date: 1 Oct 2026 *Job posting may come down early due to volume of applicants." This is metadata; we can fold minor metadata into a short

  or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short

  for posting end date and note. Not as heading. Also the reference number at end: "Reference Number R-565307-1" - minor metadata, can be dropped or folded into short p. We must not include EEO, drug policy, etc. Now craft HTML. Let's extract content. **Benefits section**: From "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!" We'll put that in a

  (maybe multiple sentences but can be one paragraph). Ensure we keep all. **About the role**: Paragraph: "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." Make that a

  . **Responsibilities**: List items from "In this role you will:": - 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. Make each

• . **Requirements**: Content: 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" Job Expectations: "Ability to work a schedule that will include Saturdays" (but we have Schedule section separate; we could still mention schedule requirement here but better to put schedule in Schedule section. However we must preserve all info; we can mention schedule in Schedule section and not duplicate. The Required Qualifications does not include schedule; it's separate Job Expectations. So we can put schedule in Schedule section. Also Job Expectations includes: "