Teller Bilingual Downtown Mesa
Wells Fargo · Mesa, AZ · 1 mo ago
FinanceFull-time
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.
We need to 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 general company description; could be part of "About the role"? Actually "About this role:" follows. The intro is more about company; but we can include it under "About the role" maybe. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section that includes the description of the role and maybe company overview? Usually "About the role" includes description of role. The intro about Wells Fargo could be considered part of "About the role" or maybe we could omit because it's generic fluff? But we must preserve ALL substantive information; do not invent or summarize away detail. The intro is substantive? It's marketing fluff but still part of posting. Should we include? The instruction: "Prefer a few substantive sections over many thin ones." We could include it in About the role.
Then "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."
That's role description.
Then "In this role you will:" bullet list of duties.
Then "Required Qualifications:" list.
Then "Desired Qualifications:" list.
Then "Job Expectations:" includes ability to work schedule that will include Saturdays; not eligible for Visa sponsorship; must take and pass required language assessment.
Then "Posting Location(s): 305 E Main. MESA, AZ 85201 @RWF22" and "Posting End Date: 15 Oct 2026 *Job posting may come down early due to volume of applicants."
Then EEO etc which we must remove.
We need to decide sections.
We have:
- About the role: could combine company intro + role description.
- Responsibilities: the bullet list under "In this role you will:" (duties). Could also include some from earlier description but we can put them there.
- Requirements: maybe "Required Qualifications" and "Job Expectations" (schedule, visa, language assessment) could be under Requirements.
- Qualifications: maybe "Desired Qualifications" could be under Qualifications? Actually they separate Required and Desired. Could map Required Qualifications to Requirements, Desired Qualifications to Qualifications.
- Skills: maybe we could extract skills from Desired Qualifications? But we could also have a Skills section if we have explicit skills list. The Desired Qualifications list includes many skill-like items. Could put them under Skills.
- Benefits: The intro mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's substantive. So we can have Benefits section with those details.
- Pay: Not explicitly stated; no salary range. So we should NOT create Pay section.
- Schedule: The Job Expectations includes ability to work schedule that will include Saturdays. That's schedule info. So we can have Schedule section with that detail.
We must not create sections with filler like "commensurate with experience". Avoid.
Thus sections:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section that includes the description of the role and maybe company overview? Usually "About the role" includes description of role. The intro about Wells Fargo could be considered part of "About the role" or maybe we could omit because it's generic fluff? But we must preserve ALL substantive information; do not invent or summarize away detail. The intro is substantive? It's marketing fluff but still part of posting. Should we include? The instruction: "Prefer a few substantive sections over many thin ones." We could include it in About the role.
Then "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."
That's role description.
Then "In this role you will:" bullet list of duties.
Then "Required Qualifications:" list.
Then "Desired Qualifications:" list.
Then "Job Expectations:" includes ability to work schedule that will include Saturdays; not eligible for Visa sponsorship; must take and pass required language assessment.
Then "Posting Location(s): 305 E Main. MESA, AZ 85201 @RWF22" and "Posting End Date: 15 Oct 2026 *Job posting may come down early due to volume of applicants."
Then EEO etc which we must remove.
We need to decide sections.
We have:
- About the role: could combine company intro + role description.
- Responsibilities: the bullet list under "In this role you will:" (duties). Could also include some from earlier description but we can put them there.
- Requirements: maybe "Required Qualifications" and "Job Expectations" (schedule, visa, language assessment) could be under Requirements.
- Qualifications: maybe "Desired Qualifications" could be under Qualifications? Actually they separate Required and Desired. Could map Required Qualifications to Requirements, Desired Qualifications to Qualifications.
- Skills: maybe we could extract skills from Desired Qualifications? But we could also have a Skills section if we have explicit skills list. The Desired Qualifications list includes many skill-like items. Could put them under Skills.
- Benefits: The intro mentions robust benefits, competitive compensation, programs for work-life balance, etc. That's substantive. So we can have Benefits section with those details.
- Pay: Not explicitly stated; no salary range. So we should NOT create Pay section.
- Schedule: The Job Expectations includes ability to work schedule that will include Saturdays. That's schedule info. So we can have Schedule section with that detail.
We must not create sections with filler like "commensurate with experience". Avoid.
Thus sections:
About the role
with paragraph(s) containing company intro and role overview.
Responsibilities
with - for each duty from "In this role you will:" list.
Requirements
with Required Qualifications and Job Expectations (schedule, visa, language assessment). Could combine.
Qualifications
with Desired Qualifications.
Skills
maybe we could extract skill bullet points from Desired Qualifications? But Desired Qualifications already includes skill-like items; maybe we can put them under Qualifications and not have separate Skills. But we need to decide if we want Skills section. The instruction: Prefer a few substantive sections over many thin ones. If we put Desired Qualifications under Qualifications, we might not need Skills. However we have Benefits and Schedule sections.
Thus we could have: About the role, Responsibilities, Requirements (Required Qualifications + Job Expectations), Qualifications (Desired Qualifications), Benefits, Schedule.
That's 6 sections.
Check if any content missing: The intro about Wells Fargo (benefits etc) we used for Benefits section. But we also used some of that for About the role? We need to avoid duplication. Let's split: About the role includes role description (the paragraph after "About this role:" up to before "In this role you will:" maybe). Benefits section includes the benefits description from the intro: robust benefits, competitive compensation, programs for work-life balance, community investment, authentic self, growth, recognition.
We must preserve all substantive info; we must not lose the company intro about being a global trailblazer etc. That could go under About the role as well. But we can incorporate that into About the role as a brief overview. However we must not duplicate. Let's think: The intro includes: "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 a lot of content. We could put that under About the role as a preamble, then also have Benefits section that extracts the benefits specifics. But that would duplicate some content (benefits). To avoid duplication, we could put the whole intro under About the role, and then Benefits section could be omitted or just mention that benefits are described there. But the instruction says include a section ONLY when the posting has real, specific content for it. Benefits section: the posting does mention robust benefits, competitive compensation, programs for work-life balance, etc. That's specific enough. So we should have Benefits section with those details. Then About the role could focus on role description and maybe not repeat benefits. But we still need to preserve the other parts of intro (global trailblazer, innovation, empowering communities, helping customers succeed, meaningful career, etc). Those are also substantive. We could include them in About the role as a brief overview, but we must not lose them. So we can include them in About the role, but we must avoid repeating the benefits specifics that we will also put in Benefits section. We could rephrase: In About the role we mention "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." Then we skip the benefits specifics there, and put them in Benefits section. That preserves all substantive info (we kept the innovation etc, and we moved benefits specifics to Benefits). Good.
Now Responsibilities: list from "In this role you will:" each line starts with a verb. We'll make - items.
Requirements: Required Qualifications (list) plus Job Expectations (schedule, visa, language assessment). We'll combine.
Qualifications: Desired Qualifications (list).
Benefits: robust benefits, competitive compensation, programs designed to help you find work-life balance and well-being, rewarded for investing in community, celebrated for being authentic self, empowered to grow, recognized as top five on 2026 LinkedIn Top Companies list of best workplaces “to grow your career” in the U.S.
Schedule: ability to work a schedule that will include Saturdays.
We must not include Visa sponsorship or language assessment in Schedule; they belong to Requirements.
Now ensure we don't include any boilerplate like EEO, etc.
Now produce HTML fragment.
We need to use
for each section heading. Use
for prose. Use
- for lists.
We must not include any extra text outside HTML.
Let's craft.
About the role: combine two paragraphs: first about Wells Fargo (global trailblazer etc). Second about the role description (the paragraph after "About this role:" up to before "In this role you will:").
Let's extract that 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 put that as
.
Now Responsibilities: list items:
- 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.
-
Requirements
with Required Qualifications and Job Expectations (schedule, visa, language assessment). Could combine.Qualifications
with Desired Qualifications.Skills
maybe we could extract skill bullet points from Desired Qualifications? But Desired Qualifications already includes skill-like items; maybe we can put them under Qualifications and not have separate Skills. But we need to decide if we want Skills section. The instruction: Prefer a few substantive sections over many thin ones. If we put Desired Qualifications under Qualifications, we might not need Skills. However we have Benefits and Schedule sections. Thus we could have: About the role, Responsibilities, Requirements (Required Qualifications + Job Expectations), Qualifications (Desired Qualifications), Benefits, Schedule. That's 6 sections. Check if any content missing: The intro about Wells Fargo (benefits etc) we used for Benefits section. But we also used some of that for About the role? We need to avoid duplication. Let's split: About the role includes role description (the paragraph after "About this role:" up to before "In this role you will:" maybe). Benefits section includes the benefits description from the intro: robust benefits, competitive compensation, programs for work-life balance, community investment, authentic self, growth, recognition. We must preserve all substantive info; we must not lose the company intro about being a global trailblazer etc. That could go under About the role as well. But we can incorporate that into About the role as a brief overview. However we must not duplicate. Let's think: The intro includes: "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 a lot of content. We could put that under About the role as a preamble, then also have Benefits section that extracts the benefits specifics. But that would duplicate some content (benefits). To avoid duplication, we could put the whole intro under About the role, and then Benefits section could be omitted or just mention that benefits are described there. But the instruction says include a section ONLY when the posting has real, specific content for it. Benefits section: the posting does mention robust benefits, competitive compensation, programs for work-life balance, etc. That's specific enough. So we should have Benefits section with those details. Then About the role could focus on role description and maybe not repeat benefits. But we still need to preserve the other parts of intro (global trailblazer, innovation, empowering communities, helping customers succeed, meaningful career, etc). Those are also substantive. We could include them in About the role as a brief overview, but we must not lose them. So we can include them in About the role, but we must avoid repeating the benefits specifics that we will also put in Benefits section. We could rephrase: In About the role we mention "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." Then we skip the benefits specifics there, and put them in Benefits section. That preserves all substantive info (we kept the innovation etc, and we moved benefits specifics to Benefits). Good. Now Responsibilities: list from "In this role you will:" each line starts with a verb. We'll makefor each section heading. Use
for prose. Use
- for lists.
We must not include any extra text outside HTML.
Let's craft.
About the role: combine two paragraphs: first about Wells Fargo (global trailblazer etc). Second about the role description (the paragraph after "About this role:" up to before "In this role you will:").
Let's extract that 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 put that as
. Now Responsibilities: list items: - 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. -