Head Universal Banker, Maspeth Branch

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules carefully: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - The first paragraph describes the role (About the role) - There's a long "Responsibilities:" section with many bullet points - "Qualifications:" section with experience, required skills, preferred skills, education - Job Family Group, Job Family, Time Type, Primary Location - these are metadata - Primary Location Full Time Salary Range - this is Pay information - Benefits information is provided - Most Relevant Skills, Other Relevant Skills - these are boilerplate - Anticipated Posting Close Date - metadata - Automated Processing and AI - boilerplate - EEO statement - boilerplate I need to create sections for: 1. About the role (the first paragraph) 2. Responsibilities (the long list) 3. Qualifications (experience, required skills, preferred skills, education) 4. Pay (salary range is given) 5. Benefits (benefits are described) 6. Schedule (Time Type: Full time is given) 7. Location (Primary Location is given) I should not create sections for Job Family Group/Family, Most Relevant Skills, Other Relevant Skills, Anticipated Posting Close Date, Automated Processing, EEO statement. Let me structure the HTML: -

  About the role

  with

  for the description -

  Responsibilities

  with
  • for each responsibility -

    Qualifications

    with subsections for Experience, Required Skills, Preferred Skills, Education - but the rules say use

    for section headings. I could use

    for Qualifications and then

    • for the items, or maybe use

      for prose and

      for lists. The qualifications section has mixed content: "2-4 years relevant experience" (prose), then "Required Skills:" with list, "Preferred Skills:" with list, "Education:" with prose. I'll use

      Qualifications

      then

      for experience, then maybe

      for sub-sections? But the rules only mention

      for section headings. I think I should keep it as one Qualifications section with

      • for the skill lists and

        for the rest. Actually, looking at the rules: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Qualifications is a section heading. I'll use

        Qualifications

        and then structure the content with

        and

        • as appropriate. For Pay: "Primary Location Full Time Salary Range: $56,500.00 - $73,700.00 In addition to salary, Citi's offerings may also include, for eligible employees, discretionary and formulaic incentive and retention awards." This is substantive pay info. For Benefits: "Citi offers competitive employee benefits, including: medical, dental & vision coverage; 401(k); life, accident, and disability insurance; and wellness programs. Citi also offers paid time off packages, including planned time off (vacation), unplanned time off (sick leave), and paid holidays. For additional information regarding Citi employee benefits, please visit citibenefits.com. Available offerings may vary by jurisdiction, job level, and date of hire." This is substantive benefits info. For Schedule: "Time Type: Full time" - this is schedule info. For Location: "Primary Location: Maspeth New York United States" - this could be a Location section or folded into a metadata paragraph. The rules don't mention Location as a standard heading, but it's substantive. I could include it as a short

          in an "About the role" or separate section. Since the rules say "Prefer a few substantive sections over many thin ones", I might fold location into a metadata paragraph at the end or beginning. But the rules also say "fold minor metadata into a short

          or drop it". Location is not minor metadata - it's important. However, the standard headings don't include Location. I'll create a short

          with location and time type at the end or beginning. Let me draft the HTML. First, About the role:

          About the role

          The Head Universal Banker is a leadership role responsible for providing exceptional service delivery to our internal and external customers while guiding and supporting the branch team. This role not only executes all service transactions (e.g. deposits, payments, address changes, replacement card orders, disputes, etc.) and sales (including opening accounts, credit cards, etc.) but also leads, coaches, and mentors team members. The Head Universal Banker plays a key role in championing risk and control, driving lobby leadership, and ensuring consistent delivery of client and team experiences aligned with the bank's standards.

          Responsibilities: There are many bullet points. I need to list each as
        • . The text has line breaks but they are all part of the responsibilities list. I'll extract each bullet point. The posting uses line breaks but not bullet characters. I'll treat each line as a separate responsibility. There are many. I'll include all. Qualifications: - Experience: 2-4 years relevant experience - Required Skills: list of 5 items - Preferred Skills: Retail experience - Education: High School diploma or equivalent I'll structure as:

          Qualifications

          2-4 years relevant experience

          Required Skills

          but rules only allow

          for section headings. I should not use

          . I'll use

          Required Skills:

          then

          • ... or just include in the list. Better to use
            • for each skill. Similarly for Preferred Skills and Education. Pay:

              Pay

              Primary Location Full Time Salary Range: $56,500.00 - $73,700.00. In addition to salary, Citi's offerings may also include, for eligible employees, discretionary and formulaic incentive and retention awards.

              Benefits:

              Benefits

              Citi offers competitive employee benefits, including: medical, dental & vision coverage; 401(k); life, accident, and disability insurance; and wellness programs. Citi also offers paid time off packages, including planned time off (vacation), unplanned time off (sick leave), and paid holidays. Available offerings may vary by jurisdiction, job level, and date of hire.

              Schedule:

              Schedule

              Full time

              Location: I'll add a short paragraph at the end or beginning. Since the rules say "fold minor metadata into a short

              ", I'll add a

              at the end with location and maybe job family info? But job family is not minor. I'll include location and time type in Schedule? Actually Schedule is separate. I'll create a

              after the sections:

              Primary Location: Maspeth, New York, United States. Job Family: Consumer Sales / Branch Sales.

              But the rules say output ONLY the HTML fragment with sections. I think it's okay to have a final

              with metadata. But the rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

              or drop it." So I can fold metadata into a short

              . I'll add a

              at the end with location and job family. Now, I need to ensure I don't include boilerplate: Automated Processing, EEO, Anticipated Posting Close Date, Most Relevant Skills, Other Relevant Skills. Let me write the HTML. I'll start with About the role, then Responsibilities, then Qualifications, then Pay, then Benefits, then Schedule, then a final paragraph for location. For Responsibilities, I need to list each item. The text has many lines. I'll copy each line as a separate

            • . Some lines are long. I'll keep them as is. Let me count the responsibilities lines from the text: 1. Lead, coach, and support Universal Bankers and Tellers by modeling excellent service behaviors and mentoring on sales, service, and compliance routines. 2. Guide both clients and team members in the branch, providing support in complex transactions and ensuring an exceptional client experience. 3. Champion risk and control by monitoring day-to-day operations, ensuring compliance with policies, supporting the Branch Manager 4. Exhibits strong sales and service skills, presenting products and services while proactively educating clients on utilizing available access channels (ex: ATM, Online, Mobile, etc.) 5. Act as a subject matter expert for the branch and remain flexible in position based on branch coverage needs. 6. Continuously learns new and existing products through sales aids (features, benefits, fees, etc.) demonstrating positive, can- do attitude and customer first culture. 7. Provide exceptional service delivery to our internal and external customers to resolve account service issues and respond to customer inquiries promptly and effectively. 8. Is knowledgeable about the client's accounts and business with the bank and uses sound judgment with customers and transactions 9. Energetically greet and interact with clients on the bank floor to proactively identify and address client sales and service needs; appropriately convert service requests into sales or referrals 10. Required to approach and engage clients in the branch lobby to demonstrate expertise in digital capabilities and to identify the financial needs of the clients. May require standing 60-70% of the work day 11. Ability to use the various marketing tools and digital technology available in the branch to present product offers and financial solutions to existing and potential clients (e.g. sales wall, tablet, smart phone, workbench, iPads, etc.) 12. Connect clients to the appropriate partners as necessary (e.g. leverage video conference for FA, mortgage specialist, etc.) 13. Take full ownership of clients' problems to resolve client complaints/issues promptly and effectively to ensure complete client satisfaction with resolution 14. Recognize transaction needs of clients, direct them to the alternative self-service channels and provide assistance with self- service as needed 15. Educate clients on self-service capabilities and encourage use of digital service channels (e.g. Online, Mobile, ATM, TCR, Teller Assist Unit, if applicable, etc.) 16. Exercises ownership and ensure all follow-up items are complete or handled off to the appropriate individual(s) and work harmoniously with multiple team members 17. Engage the Citi client by welcoming them with a warm friendly smile, pleasant demeanor, using the client name, whenever possible, and thanking them for doing business with Citi 18. Executes financial transactions in accordance with bank policies and procedures while maintaining an acceptable record in daily drawer balancing 19.