Teller Part Time Broward North

Wells Fargo · Tamarac, FL · 1 mo ago

FinancePart-time

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, there is an introductory "Why Wells Fargo" paragraph. That's not a section heading per rules; we can include as prose maybe under

. The "About this role:" is a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create

About the role

and then content. We need to extract "About this role:" 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 can put that under

About the role

. Next, "In this role you will:" list of duties. That's responsibilities. So we need

Responsibilities

with

items. 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. That's responsibilities. Next, "Required Qualifications:" and "Desired Qualifications:" plus "Job Expectations:" etc. We need to decide 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". That's a requirement. Desired Qualifications: a list of many bullet-like sentences. Those could go under Qualifications or Skills. The instruction says we can have Qualifications and Skills sections. We need to decide where to put content. We have "Job Expectations: Ability to work a schedule that will include Saturdays". That's schedule info. Also "This position is not eligible for Visa sponsorship". That's maybe metadata; we can drop or put in short p. We have location list; we can drop as minor metadata. We have posting end date etc; drop. We have EEO etc; drop. We have "We Value Equal Opportunity" etc; drop. We have "Drug and Alcohol Policy" etc; drop. We have "Wells Fargo Recruitment and Hiring Requirements:" etc; drop. We have "Reference Number R-565307-6"; drop. We have no explicit Benefits, Pay info. The posting mentions "robust benefits, competitive compensation" in the introductory Why Wells Fargo paragraph. That's generic but not specific. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention "robust benefits, competitive compensation" but not specific details. It's vague. Should we include Benefits and Pay? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "robust benefits, competitive compensation" which is a statement about benefits and pay, albeit generic. Is that enough? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them in general terms. However later they say: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "robust benefits, competitive compensation" is somewhat vague but not placeholder like "commensurate with experience". It's a statement but not specific details. I'd lean to not create Benefits or Pay sections because they lack specific detail. The schedule we have: "Ability to work a schedule that will include Saturdays". That's specific schedule info. So we can create Schedule section. Thus sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications), Qualifications (maybe Desired Qualifications), Skills (maybe we can extract skills from desired qualifications), Schedule. We need to avoid duplication. Let's parse 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. These are skills/qualifications. We could put them under Qualifications (desired) or Skills. Since we already have Required Qualifications, we could have Qualifications section for desired qualifications. Or we could split: Requirements (required), Qualifications (desired), Skills (maybe extract skills like communication, cash-handling, etc). But to avoid many thin sections, we could combine desired qualifications into Qualifications section and maybe not have separate Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Check if we need Benefits/Pay: not specific, skip. Now we need to output HTML fragment only, no /. Use
for each section heading. Use
- for lists. Use
  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to include the location list? It's minor metadata; we can drop per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
  or drop it." Location list could be considered minor metadata; we could drop it. But maybe we should include as a short p under maybe "Locations"? Not a defined heading. Safer to drop. We need to include "Job Expectations: Ability to work a schedule that will include Saturdays" as schedule. Also "This position is not eligible for Visa sponsorship" maybe minor metadata; we can drop or include in a short p under maybe "Additional Info". But not required. We'll include schedule section with that sentence. Now craft HTML. First, maybe include introductory "Why Wells Fargo" paragraph as a
  before any heading? The instruction says use
  for section headings; we can have prose outside headings. It's okay. Thus:
  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 the role
  with paragraph. Then
  Responsibilities
  with

Teller Part Time Broward North

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create

About the role

About the role

Responsibilities

About the role

Responsibilities

Requirements

Qualifications

Schedule

About the role

Similar jobs