Teller Marion
About the role
with paragraph(s) describing role. - "In This Role You Will" list of duties: many bullet-like sentences. Should be- each.
- "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 a qualification.
- "Desired Qualifications:" list of many bullet-like statements. Those could be under Requirements or Qualifications or Skills. We need to decide sections.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content.
- About the role: description of role (the paragraph after "About This Role").
- Responsibilities: the list under "In This Role You Will". Could be responsibilities.
- Requirements: maybe the Required Qualifications.
- Qualifications: maybe the Desired Qualifications? Or we could combine Required and Desired under Qualifications. But we need to avoid thin sections. Perhaps we have Requirements (required) and Qualifications (desired). Or we could have Skills (list of desired qualifications). Let's think.
The posting includes "Required Qualifications:" and "Desired Qualifications:" with many bullet items. Those could be split: Requirements = Required Qualifications; Qualifications = Desired Qualifications; Skills maybe not needed if we already have Qualifications. But we need to follow instruction: include a section only when posting has real specific content for it. So we can include Requirements and Qualifications sections.
We also have schedule info: "Job Expectations: Ability to work a schedule that will include Saturdays". That's schedule content. So we can include Schedule section.
Pay: not mentioned. Benefits: not mentioned (though earlier intro mentions robust benefits etc but that's generic company description; but we should not include Benefits unless specific. The intro says "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." That's somewhat generic but mentions benefits and compensation. However it's not specific details. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention robust benefits and competitive compensation but not specific. Is that considered stating them? It's vague but still states that there are robust benefits and competitive compensation. Might be considered stating them, but it's still generic. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "robust benefits, competitive compensation". So we could include Benefits and Pay sections with that content? But we need to avoid filler like "competitive compensation" maybe considered filler? It's not a specific number. The instruction about filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive compensation" is not in that list, but still vague. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them in general terms. I'd lean to include Benefits and Pay sections with the sentences from the intro that mention them. But we must not repeat job title. Also we must not include boilerplate like EEO etc.
We also have location list: multiple addresses. That's substantive info; could be placed maybe under a location paragraph. Not a defined section but we can include as a
under About the role or maybe separate? There's no section for location; we could just include as a paragraph after About the role. Also "Posting End Date 16 Oct 2026" and "Job posting may come down early due to volume of applicants." That's metadata; we could drop or fold into short
. 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 maybe. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the EEO paragraphs, drug policy, third-party recordings, etc. Now craft HTML. Structure:
About the 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.
Maybe also include the earlier company description? The intro before About This Role: "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 generic company marketing; could be part of About the role? But the instruction says 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 shortor drop it. It didn't say to remove company overview. However we might keep it as part of About the role? The "About This Role" heading already starts after that. The preceding paragraph is more about Wells Fargo generally. Could be considered part of About the role? Might be okay to include as a paragraph before the role-specific description. But we need to avoid duplication. The content about robust benefits and competitive compensation could be used for Benefits and Pay sections. Let's extract: - Benefits: robust benefits, programs designed to help you find work-life balance and well-being, rewarded for investing in your community, celebrated for being your authentic self, empowered to grow. Also mention ranked top five on LinkedIn Top Companies list. - Pay: competitive compensation. We could create Benefits section with those specifics. Pay section with "competitive compensation". However that's still vague but maybe acceptable. But we also have schedule: Ability to work a schedule that will include Saturdays. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Let's decide sections: - About the role: include the role-specific description (post "About This Role"). - Responsibilities: the list under "In This Role You Will". - Requirements: Required Qualifications. - Qualifications: Desired Qualifications (maybe rename to Skills? But we have Skills section; we could put desired qualifications under Skills. However we have both Qualifications and Skills sections; we need to decide which to use. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Required and Desired into Qualifications, and have Responsibilities and About the role. Then we could have Schedule section. Benefits and Pay maybe not needed if we already have generic statements in About the role? But we could incorporate them into About the role as well. But we need to follow the instruction: include a section ONLY when the posting has real, specific content for it. If we put Benefits and Pay sections with only vague statements, that might be considered thin/filler. The instruction about filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive compensation" is not in that list, but still vague. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them (robust benefits, competitive compensation). So we could include them. But we also have schedule stated explicitly. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. But that's many sections; maybe some are thin. However each has specific content: Benefits: robust benefits, programs for work-life balance, community investment recognition, authentic self celebration, growth empowerment, LinkedIn ranking. Pay: competitive compensation. Schedule: ability to work schedule that includes Saturdays. These are specific enough. We need to avoid duplication: The Benefits description appears also in the intro before About This Role. We'll use that for Benefits section. Pay: competitive compensation from same intro. Now we need to ensure we don't include boilerplate like EEO etc. Let's extract Benefits content precisely: 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. 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." Thus Benefits: robust benefits, programs designed to help you find work-life balance and well-being, rewarded for investing in your community, celebrated for being your authentic self, empowered to grow, ranked top five on 2026 LinkedIn Top Companies list. Pay: competitive compensation. Now schedule: "Ability to work a schedule that will include Saturdays" from Job Expectations. Now Responsibilities: list items from "In This Role You Will". Let's capture 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