Teller Part Time Emmett
or drop it." The "Why Wells Fargo: Are you looking for more? Find it here." is not a heading; it's a paragraph. We could keep it as part of About the role? But we have a section About the role; we could include that marketing text there. However the instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role includes that intro plus description of role. Responsibilities separate. Requirements/Qualifications separate. Skills maybe separate. Benefits separate. Pay separate. Schedule separate. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all details from the posting that are not boilerplate. Let's extract substantive 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 substantive. 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." Responsibilities (In this role you will: 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. 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: - 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. Job Expectations: - Ability to work a schedule that will include Saturdays - This position is not eligible for Visa sponsorship Posting Location(s): 102 W. Main St. Emmett, ID 83617 @RWF22 Posting End Date: 27 Sep 2026 *Job posting may come down early due to volume of applicants. We need to drop location, end date, visa sponsorship maybe? Visa sponsorship is a condition; could be considered metadata but maybe we keep as part of Schedule? It's not schedule. It's a job expectation. Could be included in Schedule section? Probably not. Could be a short paragraph under Schedule? But rule: fold minor metadata into a short
or drop it. Visa sponsorship is minor metadata; we could drop it. The schedule expectation is substantive: Ability to work a schedule that will include Saturdays. So we keep that. Now Benefits: from intro: "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." Also "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." Also "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." That's more about recognition. Thus Benefits section can include robust benefits, programs for work-life balance, community investment rewards, authenticity celebration, empowerment to grow, recognition as top workplace. Pay: "competitive compensation" is mentioned. Could also include "competitive compensation". We'll include Pay section with that statement. Schedule: "Ability to work a schedule that will include Saturdays". We'll include Schedule section. Now we need to output HTML fragment with headings
for each section. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which content goes into which section.
About the role: include the introductory marketing paragraph plus the "About this role:" paragraph. Could combine.
Responsibilities: the bullet list under "In this role you will:".
Requirements: maybe combine Required Qualifications and Desired Qualifications? But we have separate headings Requirements and Qualifications and Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = required qualifications. Qualifications = desired qualifications? Skills = maybe skills list. But we can map: Requirements = Required Qualifications. Qualifications = Desired Qualifications. Skills = maybe the skill-based items from desired qualifications (communication, collaboration, etc). However to avoid thin sections, we could combine Requirements and Qualifications into one section? But we have to follow instruction: "Prefer a few substantive sections over many thin ones." So we could combine Required and Desired into a single "Requirements" section, and maybe not use Qualifications or Skills if they'd be thin. However we have headings list as examples, not mandatory to use all. We can choose to include only sections with substantive content. So we could have About the role, Responsibilities, Requirements (combining required and desired), Benefits, Pay, Schedule. That's six sections. That seems reasonable.
We must not create Qualifications or Skills sections if they'd be thin. So we will not include them.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
Now we need to format.
Let's craft HTML:
About the role
for prose. We need to decide which content goes into which section. About the role: include the introductory marketing paragraph plus the "About this role:" paragraph. Could combine. Responsibilities: the bullet list under "In this role you will:". Requirements: maybe combine Required Qualifications and Desired Qualifications? But we have separate headings Requirements and Qualifications and Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements = required qualifications. Qualifications = desired qualifications? Skills = maybe skills list. But we can map: Requirements = Required Qualifications. Qualifications = Desired Qualifications. Skills = maybe the skill-based items from desired qualifications (communication, collaboration, etc). However to avoid thin sections, we could combine Requirements and Qualifications into one section? But we have to follow instruction: "Prefer a few substantive sections over many thin ones." So we could combine Required and Desired into a single "Requirements" section, and maybe not use Qualifications or Skills if they'd be thin. However we have headings list as examples, not mandatory to use all. We can choose to include only sections with substantive content. So we could have About the role, Responsibilities, Requirements (combining required and desired), Benefits, Pay, Schedule. That's six sections. That seems reasonable. We must not create Qualifications or Skills sections if they'd be thin. So we will not include them. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to format. Let's craft HTML: