Teller Part Time Pine Hill
About the role
with the paragraph(s) describing role. Then "In This Role You Will" bullet list of duties. That is responsibilities. So we can putResponsibilities
with- each bullet.
Then "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" etc. We need to map to sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have 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: list of many items (experience in customer-facing roles, strong attention to detail, ability to accurately process transactions across multiple systems in fast-paced environments, strong verbal communication and active listening skills, ability to follow policies, proven cash-handling experience, demonstrated ability to quickly build accuracy, confidence, and consistency in customer transactions, professional, integrity-driven approach, ability to recognize potential risk, ability to understand customer needs, identify referral and service opportunities, educate customers on digital banking tools, strong collaboration and relationship-building skills, organized and adaptable, ability to prioritize effectively, ability to resolve routine customer concerns with sound judgment and professionalism.)
Job Expectations: Ability to work a schedule that will include Saturdays. This position is not eligible for Visa sponsorship. Posting location(s): address. Posting End Date etc. Also "We Value Equal Opportunity" etc (boilerplate to remove). Also drug policy etc (boilerplate). So we need to keep substantive info: schedule includes Saturdays, location, posting end date maybe? 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 posting end date in a short
maybe under a generic paragraph? But we have no section for metadata; we could include a
after responsibilities before qualifications. We need to decide sections: About the role (we have). Responsibilities (we have). Requirements (maybe required qualifications). Qualifications (maybe desired qualifications). Skills (maybe combine some of desired qualifications that are skills). Benefits, Pay, Schedule: we have schedule (Ability to work a schedule that will include Saturdays). No explicit benefits or pay mentioned. So we should not create Benefits or Pay sections unless posting actually states them. There's mention of "robust benefits, competitive compensation" in the introductory fluff about Wells Fargo (the "Living the Well Life" paragraph). That is generic company benefit statement, not specific to role. The instruction: "Prefer a few substantive sections over many thin ones." Also "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The generic statement about robust benefits, competitive compensation is not specific to the role; it's company-wide. Should we include Benefits section? It says "You'll be rewarded for investing in your community, celebrated for being your authentic self, and empowered to grow." That's also generic. The instruction: do not create Benefits section unless posting actually states them. The posting does mention "robust benefits, competitive compensation" as part of the company description, but not specific to role. I'd argue it's still content, but it's generic. However the rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is not exactly filler but it's generic. I'd lean to not create Benefits section because it's not specific to the role; but we could include it under About the role? The introductory paragraph about Wells Fargo could be considered "About the role"? Actually "About This Role" heading is present, we can put the description of role there. The earlier fluff about Wells Fargo is more about company; we could drop it as boilerplate? It's not navigation/legal/EEO etc. It's company marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company marketing is not explicitly listed to remove, but it's not specific to role. Might be okay to keep as part of About the role? But the heading "About This Role" is present, we can put the paragraph that starts "Wells Fargo is seeking a Teller..." as the role description. The earlier fluff about Wells Fargo could be omitted as not directly about the role. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The earlier fluff is substantive about company but not role. Might be considered boilerplate? Not sure. Safer to keep it as a brief intro before the role heading? But we cannot add arbitrary headings besides the specified ones. We could include a
before the first heading? The instruction says output ONLY the HTML fragment; we can include paragraphs not under headings? Probably yes, but better to keep under a heading. There's no "About the company" heading allowed. So maybe we incorporate that intro into About the role section as a preamble. Thus About the role section will contain: the company description paragraph(s) plus the role description paragraph. Let's extract: Company description: "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!" 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." We can combine. Now Responsibilities: list from "In This Role You Will" bullet points. Let's extract each bullet: - 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. Now 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: list many items. Let's extract each as bullet: - 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. Job Expectations: "Ability to work a schedule that will include Saturdays. This position is not eligible for Visa sponsorship" Posting Location(s): "6306 W. Colonial Dr. Orlando, FL 32818 @RWF22" Posting End Date: "21 Sep 2026" We may include location and end date as a short paragraph. Now sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (desired qualifications), Skills (maybe we could treat some of desired qualifications as skills, but we already have Qualifications section; maybe we can combine desired qualifications into Qualifications and not have separate Skills). The instruction says we can use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have: - About the role: yes. - Responsibilities: yes. - Requirements: we have required qualifications -> yes. - Qualifications: we have desired qualifications -> yes. - Skills: maybe we could extract specific skills from desired qualifications (like strong verbal communication, active listening, cash handling, etc.) but that would be redundant. Better to not create Skills if we already have Qualifications covering them. However we could split: Requirements = required qualifications, Qualifications = desired qualifications, Skills = maybe we could list specific skill bullets like "Strong verbal communication and active listening skills", "Proven cash-handling experience", etc. But that would be splitting the same list. The instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections. So we can omit Skills section. - Benefits: we have generic statement about robust benefits, competitive compensation in company description. Could we treat that as Benefits section? It's not specific to role but it's a statement about benefits. The instruction: "include a section ONLY when the posting has real, specific content for it". The phrase "robust benefits, competitive compensation" is specific enough? It's a claim about benefits. I'd say we can include Benefits section with that sentence. However we also have "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 a description of benefits. So we could include Benefits section with that sentence. - Pay