Teller Part Time Deptford Office
for each section.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. Job title is Teller.
We must not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop.
We need to preserve all substantive info.
Let's extract sections:
- About the role: The paragraph after "About This Role" maybe: "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 prose.
- Responsibilities: The "In This Role You Will" bullet list. Those are duties. So we can list them as
- .
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.
- 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.
We need to ensure we keep all.
- Required Qualifications: The line "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". That's a requirement. Could be a
list? It's a single sentence with options. Could be but we can list as
- each option? The instruction: Use
- for any list of duties/requirements/benefits. So we can treat the options as list.
Thus Required Qualifications section:
- 6+ months of interacting with customers experience
- or equivalent demonstrated through work experience
- training
- military experience
- education
maybe combine? But we need to preserve meaning. Could do: - 6+ months of interacting with customers experience, or equivalent demonstrated through work experience, training, military experience, or education
. That's still a single - . That's okay.
- Desired Qualifications: Many bullet points. Those are desired qualifications, could be under Requirements or Qualifications? The spec includes sections: Requirements, Qualifications, Skills. We need to decide where to put them. The posting has "Required Qualifications:" and "Desired Qualifications:" plus many bullet points under Desired Qualifications. We could combine Required and Desired under a "Qualifications" section, or separate into Requirements and Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could have a single "Qualifications" section that includes both required and desired. Or we could have "Requirements" for required, and "Qualifications" for desired. But we need to avoid thin sections. Let's think: We have Required Qualifications (one line) and Desired Qualifications (many bullet points). If we split, Required would be thin (just one line). Better to combine into Qualifications section.
Thus Qualifications section: include required and desired bullet points.
We need to list desired qualifications as
- each.
Desired qualifications list:
- 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.
We'll include required qualification as a
- as well.
- Skills: Not explicitly listed separate; but many of the desired qualifications are skills. Could we create a Skills section? The spec includes Skills as possible heading. We could extract skills from desired qualifications: strong attention to detail, ability to accurately process transactions, strong verbal communication, active listening, ability to follow policies, cash-handling, ability to build accuracy, professional integrity, risk recognition, customer needs understanding, collaboration, organization, adaptability, prioritize, resolve routine concerns. That's many. But we already have them in Qualifications. To avoid duplication, maybe we don't need a separate Skills section; we can put all under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we can skip Skills if content overlaps.
- Benefits: The posting lists benefits under "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then a list: 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 output a Benefits section with
- each.
- Pay: The posting includes "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. $23.00 - $28.50". That's specific pay range. So we need a Pay section with that info. Could be a
containing the range and note.
- Schedule: The posting includes "Job Expectations: Ability to work a schedule that will include Saturdays". Also maybe other schedule info? That's it. So we have schedule info: ability to work a schedule that will include Saturdays. That's specific. So we need a Schedule section with that.
We also have posting location and maybe job ID etc. We should fold minor metadata into a short
or drop. The location: "Posting Location(s): 1675 Clements Bridge Rd Deptford, NJ 08096 @RWF22". That's minor metadata; we can include in a
maybe under a generic "About the role" or separate? 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 in a
after About the role maybe.
Also "Posting End Date: 22 Sep 2026" and "Job posting may come down early due to volume of applicants." That's also metadata; we can drop or include in a short
. Probably drop as not substantive? It's about posting timeline; maybe not needed. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Is posting end date substantive? It's about when posting ends; maybe not essential to job description. Could drop. But to be safe, we could include a short
with "Posting location: 1675 Clements Bridge Rd, Deptford, NJ 08096. Posting end date: 22 Sep 2026." That's minor metadata.
We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "We Value Equal Opportunity" etc. Also remove "Applicants With Disabilities", "Drug and Alcohol Policy", "Wells Fargo Recruitment And Hiring Requirements", "Reference Number". Also remove "Why Wells Fargo Are you looking for more? Find it here." etc.
Now construct HTML.
We need sections only when posting has real specific content.
We have:
- About the role (prose)
- Responsibilities (list)
- Qualifications (list) (including required and desired)
- Benefits (list)
- Pay (prose)
- Schedule (prose)
We might also include a short metadata paragraph after About the role or at end.
Let's craft.
HTML fragment:
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.
Posting location: 1675 Clements Bridge Rd, Deptford, NJ 08096. Posting end date: 22 Sep 2026.
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
for prose. We must not repeat job title as heading. Job title is Teller. We must not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop. We need to preserve all substantive info. Let's extract sections: - About the role: The paragraph after "About This Role" maybe: "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 prose. - Responsibilities: The "In This Role You Will" bullet list. Those are duties. So we can list them as
- .
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.
- 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.
We need to ensure we keep all.
- Required Qualifications: The line "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". That's a requirement. Could be a
- list? It's a single sentence with options. Could be
- each option? The instruction: Use
- for any list of duties/requirements/benefits. So we can treat the options as list.
Thus Required Qualifications section:
- 6+ months of interacting with customers experience
- or equivalent demonstrated through work experience
- training
- military experience
- education maybe combine? But we need to preserve meaning. Could do:
- 6+ months of interacting with customers experience, or equivalent demonstrated through work experience, training, military experience, or education . That's still a single
- . That's okay.
- Desired Qualifications: Many bullet points. Those are desired qualifications, could be under Requirements or Qualifications? The spec includes sections: Requirements, Qualifications, Skills. We need to decide where to put them. The posting has "Required Qualifications:" and "Desired Qualifications:" plus many bullet points under Desired Qualifications. We could combine Required and Desired under a "Qualifications" section, or separate into Requirements and Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could have a single "Qualifications" section that includes both required and desired. Or we could have "Requirements" for required, and "Qualifications" for desired. But we need to avoid thin sections. Let's think: We have Required Qualifications (one line) and Desired Qualifications (many bullet points). If we split, Required would be thin (just one line). Better to combine into Qualifications section.
Thus Qualifications section: include required and desired bullet points.
We need to list desired qualifications as
- each. Desired qualifications list: - 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. We'll include required qualification as a
- as well.
- Skills: Not explicitly listed separate; but many of the desired qualifications are skills. Could we create a Skills section? The spec includes Skills as possible heading. We could extract skills from desired qualifications: strong attention to detail, ability to accurately process transactions, strong verbal communication, active listening, ability to follow policies, cash-handling, ability to build accuracy, professional integrity, risk recognition, customer needs understanding, collaboration, organization, adaptability, prioritize, resolve routine concerns. That's many. But we already have them in Qualifications. To avoid duplication, maybe we don't need a separate Skills section; we can put all under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we can skip Skills if content overlaps.
- Benefits: The posting lists benefits under "Benefits Wells Fargo provides eligible employees with a comprehensive set of benefits, many of which are listed below." Then a list: 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 output a Benefits section with
- each.
- Pay: The posting includes "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. $23.00 - $28.50". That's specific pay range. So we need a Pay section with that info. Could be a
containing the range and note. - Schedule: The posting includes "Job Expectations: Ability to work a schedule that will include Saturdays". Also maybe other schedule info? That's it. So we have schedule info: ability to work a schedule that will include Saturdays. That's specific. So we need a Schedule section with that. We also have posting location and maybe job ID etc. We should fold minor metadata into a short
or drop. The location: "Posting Location(s): 1675 Clements Bridge Rd Deptford, NJ 08096 @RWF22". That's minor metadata; we can include in a
maybe under a generic "About the role" or separate? 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 in a
after About the role maybe. Also "Posting End Date: 22 Sep 2026" and "Job posting may come down early due to volume of applicants." That's also metadata; we can drop or include in a short
. Probably drop as not substantive? It's about posting timeline; maybe not needed. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Is posting end date substantive? It's about when posting ends; maybe not essential to job description. Could drop. But to be safe, we could include a short
with "Posting location: 1675 Clements Bridge Rd, Deptford, NJ 08096. Posting end date: 22 Sep 2026." That's minor metadata. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove "We Value Equal Opportunity" etc. Also remove "Applicants With Disabilities", "Drug and Alcohol Policy", "Wells Fargo Recruitment And Hiring Requirements", "Reference Number". Also remove "Why Wells Fargo Are you looking for more? Find it here." etc. Now construct HTML. We need sections only when posting has real specific content. We have: - About the role (prose) - Responsibilities (list) - Qualifications (list) (including required and desired) - Benefits (list) - Pay (prose) - Schedule (prose) We might also include a short metadata paragraph after About the role or at end. Let's craft. HTML fragment:
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.
Posting location: 1675 Clements Bridge Rd, Deptford, NJ 08096. Posting end date: 22 Sep 2026.
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
- each.
- Pay: The posting includes "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. $23.00 - $28.50". That's specific pay range. So we need a Pay section with that info. Could be a
- for any list of duties/requirements/benefits. So we can treat the options as list.
Thus Required Qualifications section:
but we can list as
- each option? The instruction: Use