Teller Eastwick Branch
About the role
with paragraph describing role: "Wells Fargo is seeking a Teller to join our National Branch Network..." etc. - Then "In This Role You Will" list of duties. That's responsibilities. - Then "Required Qualifications:" bullet list (actually just one 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"). - Then "Desired Qualifications:" list of many items. - Then "Job Expectations: Ability to work a schedule that will include Saturdays". Also "This position is not eligible for Visa sponsorship". Also location and posting date etc. Those are metadata; we can fold minor metadata into a shortor drop it. Should we include location? Probably not needed as heading; we can include a short paragraph with location and posting end date maybe. But instructions: "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 end date. - Benefits: The intro mentions "robust benefits, competitive compensation, and programs designed to help you find work-life balance and well-being." Also later: "You'll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow." Also mention "recognized for it - Wells Fargo once again ranked in the top five on the 2026 LinkedIn Top Companies list". That's more about company. Benefits section: we have mention of robust benefits, competitive compensation, programs for work-life balance. Also maybe "competitive compensation" could be Pay. But we should only create Pay/Schedule/Benefits sections if posting actually states them. It does mention benefits and compensation. So we can create Benefits section with those details. Pay: "competitive compensation" is mentioned but not specific numbers. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive compensation" is vague but not exactly placeholder? It's still vague. Might be considered filler? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation" and "robust benefits". That's stating them, albeit vague. I think we can include Benefits and Pay sections with that info. However we need to avoid filler like "commensurate with experience". "competitive compensation" is not exactly filler but still vague. Might be okay. Schedule: "Ability to work a schedule that will include Saturdays". That's specific enough for Schedule section. Thus we will have sections: - About the role (paragraph) - Responsibilities (ul li) - Requirements (maybe combine Required Qualifications? Could be Requirements section) - Qualifications (maybe Desired Qualifications) - Skills (maybe we can extract skills from desired qualifications? But we already have Qualifications sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (required qualifications), Qualifications (desired qualifications), Skills (maybe we can pull out skill statements). However we might combine required and desired into Qualifications? But we have both headings available. Let's do:
About the role
...
Responsibilities
- ...
Requirements
6+ months of interacting with customers experience, or equivalent demonstrated through work experience, training, military service, or education.
Qualifications
- ...
Skills
Maybe we can extract skill statements from desired qualifications: strong verbal communication, active listening, ability to follow policies, proven cash-handling, ability to build accuracy, professional integrity-driven approach, ability to recognize risk, ability to understand customer needs and educate on digital tools, strong collaboration, organized and adaptable, ability to resolve routine concerns. That's essentially same as desired qualifications. Could be redundant. Perhaps we skip Skills section to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we might omit Skills if content overlaps with Qualifications. We'll keep Qualifications as desired qualifications and maybe not have Skills.Benefits
Robust benefits, competitive compensation, programs designed to help you find work‑life balance and well‑being, recognition for community investment and authenticity, and opportunities for growth.
Pay
Competitive compensation (specific amount not disclosed). but we need
. Actually heading
Pay
thenCompetitive compensation (specific amount not disclosed).
. However "specific amount not disclosed" is filler? Might be considered placeholder. Better to just state "Competitive compensation" without adding "specific amount not disclosed". That's still vague but it's what posting says. We'll just put that.Schedule
Ability to work a schedule that includes Saturdays.
We also need to include location/posting date as minor metadata in a short. Perhaps after About the role or at end. We'll add a
with location and posting end date. Now ensure we remove boilerplate: EEO, drug policy, etc. Let's craft HTML. Check for duplicate lines: In responsibilities list we have many items. We'll list each as
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. 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
- 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.