Jobs · Finance · North Carolina

Teller Part Time Belmont Abbey Plaza

Wells Fargo · Shelby, NC · 1 mo ago
FinancePart-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as needed. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate. Must include sections only if real specific content. Let's parse the posting. Content: - Intro about Wells Fargo (company description) maybe part of About the role? Actually "About This Role" heading present. So we can have

About the role

with paragraph(s) describing role. - Then "In This Role You Will" list of duties. Those are responsibilities. So

Responsibilities

with
  • each bullet. - Then "Required Qualifications:" bullet? Actually it's a 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 qualification. Could go under Requirements or Qualifications. We'll treat as Requirements. - Then "Desired Qualifications:" list of many bullet-like sentences. Those are desired qualifications/skills. Could go under Qualifications or Skills. We'll separate: maybe

    Qualifications

    for required, and

    Skills

    for desired? But we need to avoid thin sections. Could combine required and desired under Qualifications. However we have also "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 but not required to keep? It's substantive but not a heading. Could be a short paragraph. - Posting locations list: many addresses. That's location info; could be a short paragraph. - Posting End Date etc. Might be metadata; we can drop as per instruction: do not put Job ID/requisition numbers as headings; fold minor metadata into short

    or drop it. So we can include location and schedule etc in a paragraph. - Benefits, Pay: not mentioned explicitly. There's mention of robust benefits, competitive compensation earlier in intro but not specific. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. The intro says "robust benefits, competitive compensation". That's a statement about benefits and compensation but not specific details. Is that enough to create sections? Likely not, because it's generic. The instruction says "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 not placeholder but still vague. However they said "Prefer a few substantive sections over many thin ones." Might be better to not create Benefits or Pay sections because no concrete details. So we omit Benefits, Pay. - Schedule: we have "Ability to work a schedule that will include Saturdays". That's specific schedule expectation. Could create Schedule section with that detail. It's substantive. So we can have

    Schedule

    with

    Ability to work a schedule that will include Saturdays.

    - Also "This position is not eligible for Visa sponsorship" could be a note; maybe include in a paragraph under Requirements or separate note. Could fold into a short

    under Requirements. - Locations: list of addresses. Could be a paragraph. - Posting End Date etc: maybe drop. - Also "Due to timing and resource needs, positions may not be available at all branch locations outlined in the posting". Could be note. - Also "Job posting may come down early due to volume of applicants." drop. - Also EEO etc drop. Thus sections: About the role: paragraph(s) from "About This Role" and maybe the earlier Wells Fargo intro? The intro about Wells Fargo is more company overview; could be part of About the role? Probably yes: we can include that as description of company and role. But the instruction: "Do NOT repeat the job title as a heading (the page already shows it)". Not about company intro. We'll include company overview as part of About the role. Thus About the role: combine the Wells Fargo intro paragraph(s) and the "About This Role" paragraph. Let's extract: 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!" That's a bit weird with "Why Wells Fargo Are you looking for more? Find it here." Might be a heading but we can treat as part of intro. 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'll combine. Responsibilities: list from "In This Role You Will" bullet points. Each sentence ends with period. We'll make each as

  • . Let's list them: - 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 9 items. Requirements: Required Qualifications line: "6+ months of interacting with customers experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education". Also maybe include "This position is not eligible for Visa sponsorship". Also maybe include "Ability to work a schedule that will include Saturdays" but that's schedule. We'll put Required Qualifications as a

    . Skills: Desired Qualifications list: many bullet-like sentences. We'll make each as

  • under Skills. Let's extract Desired Qualifications sentences: - 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. That's 11 items. Schedule: "Ability to work a schedule that will include Saturdays". We'll make a

    . Locations: list of addresses. We'll make a

    with them separated by commas or line breaks? Use
    maybe but we can just separate with semicolons. We'll keep as a paragraph. Also note about positions may not be available at all branch locations; we can include as a sentence. We'll not include posting end date etc. Now produce HTML fragment:

    About the role

    ... combined intro ...

    Responsibilities

    • ...
    • ...

    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. This position is not eligible for Visa sponsorship.

    Skills

    • ...
    • ...

    Schedule

    Ability to work a schedule that will include Saturdays.

    Location

    maybe not required but we have location info. There's no heading for Location in the list but we could treat as part of Requirements or a separate section. The instruction only lists specific headings; we can add others if needed but better to stick to given headings. Location could be folded into a short paragraph under Requirements or maybe under About the role? Probably better to add a

    after Requirements but not as a heading. Since we must not invent headings not listed unless we have real content; we could add a

    for location without heading. That's allowed. Thus after Requirements we can add a

    with location list and note. Let's craft location paragraph: "Posting locations include: 2803 Freedom Dr, Charlotte, NC 28208-3855; 403 Cox Rd, Oak Tree Plaza, Gastonia, NC 28054; 231 S Washington St, Shelby, NC 28150-4668; 101 S Main St, Mount Holly, NC 28120-1618; 5641 Hovis Road, Charlotte, NC 28216-3307; 4111 N Tryon St, Charlotte, NC 28206-2066; 110 E Franklin Blvd, Gastonia, NC 28052-4105; 635 Park St, Belmont, NC 28012-2777; 750 S New Hope Rd, Gastonia, NC 28054; 10210 Couloak Dr, Charlotte, NC 28216; 301 S Tryon St, Charlotte, NC 28282; 2610 W. Sugar Creek, Charlotte

Similar jobs