Teller Part Time Marion

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. We must not repeat job title. Must not include Job ID etc. Must 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!" This is about company culture/benefits. Could go under Benefits? It mentions robust benefits, competitive compensation, programs for work-life balance, etc. But we need to only include sections if posting has real specific content. This is somewhat generic but still mentions benefits, compensation, programs. Might be considered Benefits section. However we also have a separate "Benefits" section maybe we can include. - About this role: description of Teller role. - In this role you will: list of duties (bullet-like sentences). That's responsibilities. - 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. - Job Expectations: Ability to work a schedule that will include Saturdays. This position is not eligible for Visa sponsorship. Posting Location(s): 340 7th Ave MARION IA 52302 @RWF22. Posting End Date: 27 Sep 2026 *Job posting may come down early due to volume of applicants. We need to include sections: About the role (maybe "About this role" as heading). Responsibilities (the "In this role you will:" list). Requirements (maybe combine Required Qualifications). Qualifications (maybe Desired Qualifications). Skills (maybe from desired qualifications). Benefits (from intro). Pay (none specific). Schedule (from Job Expectations: Ability to work a schedule that will include Saturdays). Also location and posting date maybe minor metadata; we can fold into a short p or drop. We must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers as headings; we can drop them. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraphs, drug policy, recruitment requirements, etc. We must preserve all substantive information. Thus we need to extract substantive info: Company culture/intro: robust benefits, competitive compensation, programs for work-life balance and well-being, rewarded for investing in community, celebrated for authentic self, empowered to grow, recognized top five LinkedIn Top Companies 2026. We could put that under Benefits section (maybe also under About the role? but we have separate About this role). The intro is more about Wells Fargo overall, not role-specific. Could be placed under a section like "About Wells Fargo" but not in allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put the company intro under Benefits (since it mentions benefits, compensation, programs). Or we could put under About the role? But About the role should be role-specific. The intro is not role-specific. However we could still include it as a paragraph under Benefits (makes sense). The Benefits section should contain substantive benefits info: robust benefits, competitive compensation, programs for work-life balance and well-being, rewarded for investing in community, celebrated for authentic self, empowered to grow, recognized top five LinkedIn Top Companies 2026. We must not invent or summarize away detail. We need to preserve all substantive information; we can keep the sentences as is. Responsibilities: list of duties from "In this role you will:" each sentence. We'll put each as

. 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". That's a requirement. Desired Qualifications: list of many bullet-like sentences. We could split into Qualifications and Skills sections. But we have both Qualifications and Skills headings allowed. We need to decide what goes where. The posting lumps them as "Desired Qualifications". Could treat them as Qualifications (desired) and maybe Skills separate? But we have both headings; we could put all desired qualifications under Qualifications (since they are qualifications). Or we could separate skills like "Strong verbal communication and active listening skills", "Ability to follow policies...", etc. But we risk splitting arbitrarily. The instruction: Prefer a few substantive sections over many thin ones. So maybe we just have one Qualifications section that includes both required and desired? But we have separate Required Qualifications heading in posting; we could have a Required Qualifications subsection? Not allowed headings. We could combine Required and Desired under Qualifications heading, but we need to preserve all info. We could have two subsections? Not allowed; only headings list. Could we have both Required Qualifications and Desired Qualifications as separate sections using the same heading? Not allowed; headings are fixed. We could use

for "Requirements" and

for "Qualifications". Use Requirements for required qualifications, Qualifications for desired qualifications. That seems appropriate. Thus: -

Requirements

: Required Qualifications content. -

Qualifications

: Desired Qualifications content. Skills: maybe we could extract skills from desired qualifications but we already have Qualifications; we could leave Skills empty? But we must not create a section unless posting has real specific content for it. If we don't have specific skills separate, we should omit Skills section. However we could treat some items as skills: "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 skills/qualifications. Could put them under Skills section. But then Qualifications would be empty. Better to put all desired qualifications under Qualifications and omit Skills. Since we have both headings allowed, we can choose to omit Skills if no specific content. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills. Benefits: from intro. Pay: none specific; omit. Schedule: from Job Expectations: Ability to work a schedule that will include Saturdays. Also maybe mention not eligible for Visa sponsorship (but that's not schedule). We'll include schedule info. We also have location and posting date; we can fold into a short p under maybe a generic section? Not allowed headings; we could just include a

at end with location and posting date. 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

with location and posting date. We must not include boilerplate like EEO etc. Now construct HTML. We'll start with

About the role

maybe? Actually we have "About this role:" heading in posting. We'll use

About the role

and put the paragraph describing the role (the paragraph after "About this role:"). Then

Responsibilities

with

of duties. Then

Requirements

with

for required qualifications. Then

Qualifications

with
for desired qualifications. Then

Benefits

with

for benefits intro. Then

Schedule

with

for schedule info. Then a final

for location and posting date. Check that we don't repeat content. Let's extract exact sentences. About this 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." We'll keep that. Responsibilities list (from "In this role you will:" bullet points). Let's list each sentence: - 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'll put each as

• . 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" We'll put as

  . Qualifications (desired): list each sentence: - 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,