Teller Part Time Hayward California
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key content:
- Intro about Wells Fargo: "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; could be part of "About the role"? Actually "About This Role" heading appears later. The intro is about Wells Fargo, not role specifics. Might be considered "About the role"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" section containing description of role and maybe company overview. But we should not repeat job title as heading. So we can have About the role
then prose summarizing the role description.
Then "In This Role You Will" list of duties: bullet points.
Then "Required Qualifications:" and "Desired Qualifications:" maybe combine into Requirements/Qualifications/Skills.
We have "Job Expectations: Ability to work a schedule that will include Saturdays" and "This position is not eligible for Visa sponsorship". Also "Posting Location(s): 1172 A St Hayward, CA 94541 @RWF22". Also "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities. $22.00 - $27.50". Also "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then list of benefits.
Also "Posting End Date: 17 Oct 2026 Job posting may come down early due to volume of applicants." That's metadata; we can fold into short
or drop. Probably drop as minor metadata.
We need to remove boilerplate: EEO, disability, drug policy, recruitment requirements, reference number, etc.
We need to decide which sections to include: About the role (yes), Responsibilities (yes), Requirements (maybe combine Required and Desired qualifications), Qualifications (maybe same as Requirements?), Skills (maybe we can extract skills from desired qualifications), Benefits (yes), Pay (yes), Schedule (yes, from Job Expectations). We should avoid thin sections; maybe combine Requirements and Qualifications into one section? But the instruction list includes both; we can include both if they have substantive content. However we can combine to avoid thin sections. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Requirements & Qualifications (combined), Benefits, Pay, Schedule. Or we could have separate Requirements and Qualifications if they have distinct content. Let's see.
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: a long list of skills/experience.
We could treat Required Qualifications as Requirements, Desired Qualifications as Skills (or Qualifications). But we have both Qualifications and Skills headings available. Could put Required under Requirements, Desired under Skills. Or combine.
Better: Requirements section for Required Qualifications. Skills section for Desired Qualifications (since they are skills). Qualifications section maybe not needed if we already have Requirements and Skills. But we could also have Qualifications for both required and desired? Might be redundant.
Given we want few substantive sections, we could have: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 7 sections. Could be okay if each has substantive content.
Check each:
- About the role: we have company overview and role summary. Good.
- Responsibilities: the bullet list under "In This Role You Will". Good.
- Requirements: Required Qualifications (6+ months interacting with customers experience, or equivalent). Good.
- Skills: Desired Qualifications list (customer-facing roles, attention to detail, process transactions, communication, cash-handling, etc). Good.
- Benefits: list of benefits. Good.
- Pay: pay range $22.00 - $27.50 plus note about base pay and incentives. Good.
- Schedule: Ability to work a schedule that will include Saturdays. Also maybe mention not eligible for Visa sponsorship? That's not schedule. Could include schedule only. That's substantive enough.
We should not include location as heading; we can fold into a short
under About the role maybe.
We must not include Job ID/requisition numbers as headings; we can drop them.
We must not include application instructions, EEO, etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., "6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education". Keep that exactly.
For Desired Qualifications list, we need to keep each bullet. The list includes many items; we need to preserve them. We'll output as
- each.
For Benefits list: we need to preserve each benefit item exactly as listed: Health benefits, 401(k) Plan, Paid time off, Disability benefits, Life insurance, critical illness insurance, and accident insurance, Parental leave, Critical caregiving leave, Discounts and savings, Commuter benefits, Tuition reimbursement, Scholarships for dependent children, Adoption reimbursement.
We need to ensure we don't add extra info.
For Pay: we need to keep the sentence about base pay range and incentives. Could be a
.
For Schedule: we need to keep "Ability to work a schedule that will include Saturdays". Could be a
.
We also have "Posting Location(s): 1172 A St Hayward, CA 94541 @RWF22". Could be a short
under About the role maybe.
We also have "Posting End Date: 17 Oct 2026 Job posting may come down early due to volume of applicants." Could be a short
maybe under About the role or at end. But it's metadata; we can fold into a short
or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location and end date in a short
maybe under About the role or after.
We must not include boilerplate like EEO, disability, drug policy, recruitment requirements, reference number.
Now produce HTML fragment.
Structure:
About the role
Wells Fargo is a global trailblazer committed to driving innovation, empowering communities, and helping customers succeed. The company offers robust benefits, competitive compensation, and programs for work-life balance and well-being, and is recognized as a top workplace for career growth. 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, you represent the branch through strong service, attention to detail, and genuine care, building 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, 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.
Location: 1172 A St, Hayward, CA 94541. Posting end date: 17 Oct 2026 (may come down early due to volume of applicants).
Then Responsibilities:
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.
Then Requirements:
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
Then Skills:
Skills
- 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
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Intro about Wells Fargo: "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; could be part of "About the role"? Actually "About This Role" heading appears later. The intro is about Wells Fargo, not role specifics. Might be considered "About the role"? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" section containing description of role and maybe company overview. But we should not repeat job title as heading. So we can have About the role
then prose summarizing the role description.
Then "In This Role You Will" list of duties: bullet points.
Then "Required Qualifications:" and "Desired Qualifications:" maybe combine into Requirements/Qualifications/Skills.
We have "Job Expectations: Ability to work a schedule that will include Saturdays" and "This position is not eligible for Visa sponsorship". Also "Posting Location(s): 1172 A St Hayward, CA 94541 @RWF22". Also "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities. $22.00 - $27.50". Also "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then list of benefits.
Also "Posting End Date: 17 Oct 2026 Job posting may come down early due to volume of applicants." That's metadata; we can fold into short
or drop. Probably drop as minor metadata. We need to remove boilerplate: EEO, disability, drug policy, recruitment requirements, reference number, etc. We need to decide which sections to include: About the role (yes), Responsibilities (yes), Requirements (maybe combine Required and Desired qualifications), Qualifications (maybe same as Requirements?), Skills (maybe we can extract skills from desired qualifications), Benefits (yes), Pay (yes), Schedule (yes, from Job Expectations). We should avoid thin sections; maybe combine Requirements and Qualifications into one section? But the instruction list includes both; we can include both if they have substantive content. However we can combine to avoid thin sections. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Requirements & Qualifications (combined), Benefits, Pay, Schedule. Or we could have separate Requirements and Qualifications if they have distinct content. Let's see. 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: a long list of skills/experience. We could treat Required Qualifications as Requirements, Desired Qualifications as Skills (or Qualifications). But we have both Qualifications and Skills headings available. Could put Required under Requirements, Desired under Skills. Or combine. Better: Requirements section for Required Qualifications. Skills section for Desired Qualifications (since they are skills). Qualifications section maybe not needed if we already have Requirements and Skills. But we could also have Qualifications for both required and desired? Might be redundant. Given we want few substantive sections, we could have: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. That's 7 sections. Could be okay if each has substantive content. Check each: - About the role: we have company overview and role summary. Good. - Responsibilities: the bullet list under "In This Role You Will". Good. - Requirements: Required Qualifications (6+ months interacting with customers experience, or equivalent). Good. - Skills: Desired Qualifications list (customer-facing roles, attention to detail, process transactions, communication, cash-handling, etc). Good. - Benefits: list of benefits. Good. - Pay: pay range $22.00 - $27.50 plus note about base pay and incentives. Good. - Schedule: Ability to work a schedule that will include Saturdays. Also maybe mention not eligible for Visa sponsorship? That's not schedule. Could include schedule only. That's substantive enough. We should not include location as heading; we can fold into a short
under About the role maybe. We must not include Job ID/requisition numbers as headings; we can drop them. We must not include application instructions, EEO, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., "6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education". Keep that exactly. For Desired Qualifications list, we need to keep each bullet. The list includes many items; we need to preserve them. We'll output as
- each.
For Benefits list: we need to preserve each benefit item exactly as listed: Health benefits, 401(k) Plan, Paid time off, Disability benefits, Life insurance, critical illness insurance, and accident insurance, Parental leave, Critical caregiving leave, Discounts and savings, Commuter benefits, Tuition reimbursement, Scholarships for dependent children, Adoption reimbursement.
We need to ensure we don't add extra info.
For Pay: we need to keep the sentence about base pay range and incentives. Could be a
. For Schedule: we need to keep "Ability to work a schedule that will include Saturdays". Could be a
. We also have "Posting Location(s): 1172 A St Hayward, CA 94541 @RWF22". Could be a short
under About the role maybe. We also have "Posting End Date: 17 Oct 2026 Job posting may come down early due to volume of applicants." Could be a short
maybe under About the role or at end. But it's metadata; we can fold into a short
or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location and end date in a short
maybe under About the role or after. We must not include boilerplate like EEO, disability, drug policy, recruitment requirements, reference number. Now produce HTML fragment. Structure:
About the role
Wells Fargo is a global trailblazer committed to driving innovation, empowering communities, and helping customers succeed. The company offers robust benefits, competitive compensation, and programs for work-life balance and well-being, and is recognized as a top workplace for career growth. 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, you represent the branch through strong service, attention to detail, and genuine care, building 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, 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.
Location: 1172 A St, Hayward, CA 94541. Posting end date: 17 Oct 2026 (may come down early due to volume of applicants).
Then Responsibilities: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.
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
Then Skills:Skills
- 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