Head Teller - Exit 11 Branch - NY

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: Why Join Us? maybe we can incorporate into Benefits? Actually "Why Join Us?" is a paragraph about culture; we could put under About the role? But we have a section "About The Head Teller Role". That is content. We'll include

About the role

with that paragraph. Responsibilities: we have "Key Responsibilities" with bullet points. We'll list as

• . Qualifications: there is "Qualifications Required" and "Preferred". We'll combine into Requirements? Actually we have sections: Qualifications, Skills, Requirements. The instruction says use headings for those categories. We need to decide what goes where. Typically "Qualifications" includes education, experience. "Skills" includes abilities like communication, organizational. "Requirements" maybe similar to qualifications. But we can map: Required qualifications under "Qualifications". Preferred maybe also under Qualifications or Skills? We'll put required under Qualifications, preferred under Skills? Or we can put both under Qualifications and note preferred. But we need to avoid thin sections. Let's see content: Required: - High school diploma or equivalent. - Supervisory experience. - Strong customer service and cash-handling experience. - Excellent verbal communication and interpersonal skills in person, by phone, and via email. - Fluent in English; bilingual a plus - Access to reliable transportation - Strong organizational skills with the ability to manage multiple priorities. - Ability to work effectively in a collaborative team environment. - Willingness to participate in ongoing training and development. - Ability to lift 10–20 lbs., stand for extended periods. Preferred: - Bachelor’s degree. - Previous banking or financial services experience. We could have a Qualifications section with required and preferred listed. Skills maybe not needed separate. But we need to follow instruction: use headings for those categories if content exists. We could have Qualifications (required) and Skills (preferred). However "Skills" could include communication, interpersonal, organizational etc. But those are already in required. Might be redundant. Better: Use Qualifications for education/experience, Skills for abilities like communication, organizational, etc. Let's split: Qualifications: - High school diploma or equivalent. - Supervisory experience. - Strong customer service and cash-handling experience. - Access to reliable transportation. - Willingness to participate in ongoing training and development. - Ability to lift 10–20 lbs., stand for extended periods. - Preferred: Bachelor’s degree. - Preferred: Previous banking or financial services experience. Skills: - Excellent verbal communication and interpersonal skills in person, by phone, and via email. - Fluent in English; bilingual a plus. - Strong organizational skills with the ability to manage multiple priorities. - Ability to work effectively in a collaborative team environment. That seems reasonable. Benefits: we have a paragraph listing benefits: medical, dental and vision insurance, HSA with employer contribution, 401(k) with match, paid time off plus 11 paid federal holidays, training and professional development programs, tuition reimbursement, reduced fees and rates on certain loan products, and much more! We'll include that. Pay: Not mentioned. So we should NOT include Pay section. Schedule: we have schedule details: Full-time Position With Hours Aligned To Branch Operations Mon–Wed: 8:30 AM – 5:00 PM Thu–Fri: 8:30 AM – 6:00 PM Sat: 8:30 AM – 1:00 PM (rotating schedule) Sun: Closed Employees may need to remain 15–30 minutes after closing. Occasional travel for training, meetings, or branch support. We'll include Schedule section. Also we have "About The Head Teller Role" paragraph. We'll put under About the role. We must not include boilerplate like "Why Join Us?" but we could incorporate that into Benefits? Actually "Why Join Us?" is about culture and benefits; we already have Benefits section. The paragraph about supportive workplace etc could be part of About the role? But we already have About the role description. Could add a short paragraph about culture under About the role? But we must not invent content; we can include that paragraph as part of About the role if we want, but it's not under About The Head Teller Role heading. However we can treat "Why Join Us?" as a separate section? Not in allowed headings. Could fold into About the role as extra prose. The instruction: "Prefer a few substantive sections over many thin ones." So we can merge that into About the role. Thus About the role section will contain two paragraphs: the "Why Join Us?" culture paragraph and the "About The Head Teller Role" description. Ensure we preserve all substantive info. We must not include the EEO statement, etc. Now produce HTML:

  About the role

  At Trustco Bank, we’re committed to fostering a supportive and inclusive workplace where our employees can grow their careers. We believe that our people are our greatest asset and consider our employees as family. We value each team member’s contribution and offer a supportive, collaborative work environment. In this role, you’ll have the opportunity to lead a talented team, make a positive impact in our community, and be rewarded for your success. We believe that investing in our employees means investing in the future of our company. As a valued team member, you will be eligible for a generous compensation and benefits package that includes: medical, dental and vision insurance, a health savings account with an annual employer contribution, a 401(k)-retirement plan with generous employer match, paid time off plus 11 paid federal holidays, training and professional development programs, tuition reimbursement, reduced fees and rates on certain loan products, and much more!

  The Head Teller provides exceptional customer service while accurately and efficiently completing customer transactions. This role ensures adherence to all bank operational, security, compliance, and privacy policies, maintaining the highest standards of confidentiality. The Head Teller oversees daily teller operations, supervises teller staff, and ensures that branch cash handling procedures are followed.

  Responsibilities

  • Deliver Outstanding Customer Service: Create a warm, professional, and efficient environment where every customer feels valued. Proactively understand their needs and confidently recommend Trustco Bank products that support their goals.
  • Leadership & Team Growth: Supervise, mentor, and coach tellers to ensure accuracy, efficiency, and exceptional service. Uphold strict compliance with all policies, acting as a role model. Oversee daily cash balancing and maintain detailed audit logs for accuracy. Manage cash shipments, including ordering, verifying, and distributing funds as needed.
  • Transaction Handling: Process a variety of customer transactions—deposits, withdrawals, loan payments, check cashing—with precision. Handle verification, money orders, bank checks, and receipts efficiently. Manage credit card payments, safe deposit access, ATM maintenance, and night deposits smoothly.
  • Reporting & Compliance: Prepare and submit detailed reports accurately and on time. Keep thorough transaction records in line with audit standards and regulations.

  Qualifications

  • High school diploma or equivalent.
  • Supervisory experience.
  • Strong customer service and cash-handling experience.
  • Access to reliable transportation.
  • Willingness to participate in ongoing training and development.
  • Ability to lift 10–20 lbs., stand for extended periods.
  • Preferred: Bachelor’s degree.
  • Preferred: Previous banking or financial services experience.

  Skills

  • Excellent verbal communication and interpersonal skills in person, by phone, and via email.
  • Fluent in English; bilingual a plus.
  • Strong organizational skills with the ability to manage multiple priorities.
  • Ability to work effectively in a collaborative team environment.

  Benefits

  Medical, dental and vision insurance, a health savings account with an annual employer contribution, a 401(k)-retirement plan with generous employer match, paid time off plus 11 paid federal holidays, training and professional development programs, tuition reimbursement, reduced fees and rates on certain loan products, and much more!

  Schedule

  Full-time Position With Hours Aligned To Branch Operations Mon–Wed: 8:30 AM – 5:00 PM Thu–Fri: 8:30 AM – 6:00 PM Sat: 8:30 AM – 1:00 PM (rotating schedule) Sun: Closed Employees may need to remain 15–30 minutes after closing. Occasional travel for training, meetings, or branch support.

  Check for any repeated content: The benefits paragraph appears also in About the role; we duplicated benefits. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It didn't say we cannot repeat. But we might want to avoid duplication. However the About the role paragraph already includes benefits list; we could keep it there and not have a separate Benefits section. But we need to decide if we include Benefits section. The posting has a benefits list; we could put it under Benefits section and not duplicate in About the role. However the About the role paragraph also includes a sentence about benefits; we could keep that sentence but maybe we should not duplicate the list. The instruction: "Preserve ALL substantive information". If we remove the benefits sentence from About the role, we lose that sentence (which is substantive). But we could keep the sentence but not the list? The sentence: "As a valued team member, you will be eligible for a generous compensation and benefits package that includes: medical, dental and vision insurance, a health savings account with an annual employer contribution, a 401(k)-retirement plan with generous employer match, paid time off plus 11 paid federal holidays, training and professional development programs, tuition reimbursement, reduced fees and rates on certain loan products, and much more!" That's the benefits list. If we move that to Benefits section, we still preserve it. The About the role would then lose that sentence; we could keep a generic sentence about being eligible for a generous compensation and benefits package without listing. But that would be summarizing away detail (the list). Better to keep the list in Benefits section and remove from About the role, but keep a short sentence about being eligible for a generous compensation and benefits package (without list) to preserve the idea that they mention it. However that would be altering detail (removing the list from that sentence). The instruction says do NOT invent or summarize away detail. Summarizing away detail would be removing the list. So we should keep the list somewhere; we can keep it in Benefits section and also keep the sentence in About the role but maybe we can keep the sentence without the list? That would be summarizing away detail (the list) from that sentence, but the list still appears elsewhere, so overall detail is preserved. However the sentence itself would be changed (we removed the colon and list). That is altering the original text. Might be considered summarizing away detail from that sentence but overall we still have the list. The instruction likely means do not omit any substantive information from the posting; we can reorganize but must keep all details. So we can keep the list in Benefits section and keep a brief sentence in About the role that mentions eligibility for a generous compensation and benefits package (without listing). That still conveys that they mentioned a package, but we lost the specifics from that sentence. However the specifics are present elsewhere, so overall we haven't lost any detail. I think it's acceptable. Alternatively, we could keep the entire paragraph in About the role and not have a separate Benefits section, but then we would not have a Benefits heading, which is okay if we prefer