CSR/Teller - Wixom - Part Time

We need to output HTML fragment with sections only if real content. The posting includes sections: GENERAL FUNCTION (maybe as a heading?), but we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting doesn't have explicit headings like "About the role". We need to map content to appropriate headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should create headings based on content: maybe "About the role" for general function description, "Responsibilities" for essential duties, "Requirements" for minimum knowledge, skills, abilities, "Qualifications" maybe overlapping, "Skills" maybe separate, "Benefits" if present, "Pay" if present, "Schedule" if present. We must not repeat job title as heading. Job title is "CSR/Teller - Wixom - Part Time". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove the "Attention search firms..." etc. Also remove EEO statement. We must preserve all substantive information. We need to decide what sections to include. Content: - GENERAL FUNCTION: Provide excellent customer service... etc. That's about role. - Customer Experience ESSENTIAL DUTIES AND RESPONSIBILITIES: list of duties. - Operations: more duties. - Referrals: duties. - SUPERVISORY RESPONSIBILITIES: None. (We could ignore as not substantive? It says none, but we might not include a heading for supervisory responsibilities because it's not a standard heading; we could omit.) - Minimum Knowledge, Skills And Abilities Required: list. - Working Conditions: Normal office environment... etc. - Benefits: mention of Total Rewards, comprehensive benefits, differentiated compensation, base salary reflective of range, extensive benefits programs, link to benefits page. This is substantive benefits info. - Pay: "The base salary for this position is reflective of the range of salary levels for all roles within this pay grade across the U.S. Individual salaries within this range will vary based on factors such as role, relevant skillset, relevant experience, education and geographic location." That's pay info but not specific numbers. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they do state base salary reflective of range, individual salaries vary based on factors. That is somewhat vague but still states something about pay. It's not a specific number but it's not filler like "varies"? It says "will vary based on factors". That is somewhat vague but still mentions pay. The instruction says never create Pay section unless posting actually states them. It does state something about pay (base salary reflective of range). So we can include a Pay section with that prose. - Schedule: "Need to have flexibility in scheduling." That's schedule info. So we can include Schedule section. - Benefits: we have benefits description. - Skills: maybe we can extract from Minimum Knowledge, Skills And Abilities Required: includes high school diploma/GED, cash handling, public interaction, dress code, ability to interact comfortably, knowledge of retail policies, initiative, sound judgment, core values, flexibility in scheduling. That's more like requirements/qualifications/skills. We could put them under Requirements or Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one section maybe "Requirements". But we have separate headings allowed; we could just use "Requirements" for all that. - About the role: we can use GENERAL FUNCTION as About the role. - Responsibilities: combine Customer Experience ESSENTIAL DUTIES AND RESPONSIBILITIES, Operations, Referrals. We must not duplicate lines. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

Provide excellent customer service in all interactions. Refer customers to the appropriate business partner for a consultative conversation. Responsible and accountable for risk by openly exchanging ideas and opinions, elevating concerns, and personally following policies and procedures as defined. Accountable for always doing the right thing for customers and colleagues and ensures that actions and behaviors drive a positive customer experience. While operating within the Bank's risk appetite, achieves results by consistently identifying, assessing, managing, monitoring, and reporting risks of all types.

Responsibilities

• Deepen relationships and treat customers with genuine care by listening to their specific needs, asking questions to gain deeper understanding, and seamlessly guide them to where their financial needs can be met
• Provide follow up to customer questions and find solutions to address issues
• Be responsive and timely with correspondence to keep lines of communication open and clear
• Maintain a position of trust and responsibility by keeping all customer business confidential
• Follow the Bancorp Code of Business Conduct and Ethics and other related policies, always maintaining ethical behavior
• Perform daily office responsibilities, working with the platform team, to maintain the efficient operation of the office
• Maintain a balancing record that is in line with policy
• Find and correct outages and enlist help as needed
• Maintain knowledge of the bank policies and financial center procedures and take responsibility to keep up to date on any changes
• Handle consumer and business customer problems with professionalism, directing more complex issues seamlessly to the Lead Customer Service Representative or other leadership as necessary
• Demonstrate sound judgment in decision making, abiding to established guidelines and procedures
• During customer interactions and Customer Outreach identify customer needs and refer customers to Bankers and business partners, as appropriate, for a consultative conversation
• Build and maintain a working knowledge of the Retail products and services offered
• Utilize appropriate tools for all referrals sent to personal bankers and business partners for tracking purposes
• Perform other duties as assigned

Requirements

• High school diploma/GED
• Work involves extensive cash handling
• Work involves contact with the public, adhere to dress code guidelines
• Ability to interact comfortably and confidently with the public
• Knowledge of retail policies and procedures to perform essential duties
• Ability to take initiative and demonstrate sound judgment in decision‑making and problem resolution
• Demonstrate the company’s core values: work as one bank, take accountability, be respectful & inclusive, act with integrity
• Flexibility in scheduling

Benefits

Fifth Third offers a Total Rewards program that includes comprehensive benefits and differentiated compensation offerings to support employees’ physical, financial, emotional and social well‑being. Details of the benefits programs can be found on the 53.com Careers page: https://www.53.com/content/fifth-third/en/careers/benefits.html or by consulting with your talent acquisition partner.

Pay

The base salary for this position reflects the range of salary levels for all roles within this pay grade across the U.S.; individual salaries within this range vary based on role, relevant skillset, experience, education and geographic location.

Schedule

This part‑time role requires flexibility in scheduling.

We need to ensure we didn't include any boilerplate like EEO, search firms, etc. We removed those. Check for duplicated lines: we didn't duplicate. Check for any placeholders like "commensurate with experience": none. Check for "not specified": none. Check for "N/A": none. Check for "varies": we used "vary" but that's okay because it's actual statement. Check for "TBD": none. Check for "Schedule": we have schedule section with actual statement. Check for "Pay": we have pay section with actual statement. Check for "Benefits": we have benefits section with actual statement. Check for "About the role": we used GENERAL FUNCTION content. Check for "Responsibilities": we combined duties. Check for "Requirements": we used Minimum Knowledge, Skills And Abilities Required plus flexibility in scheduling (though scheduling also appears in schedule section; but we included flexibility in scheduling under Requirements as it's a requirement; also schedule section mentions flexibility. Might be duplication but it's okay; we could remove from Requirements to avoid duplication. However the instruction says preserve ALL substantive information; duplication is okay if it's in original? The original mentions flexibility in scheduling under Minimum Knowledge, Skills And Abilities Required and also under Working Conditions? Actually it's under Minimum Knowledge, Skills And Abilities Required: "Need to have flexibility in scheduling." So it's a requirement. The schedule section we derived from that same line. To avoid duplication, we could keep it only in Requirements and not have a separate Schedule section. But the instruction says prefer a few substantive sections over many thin ones. Having both Requirements and Schedule may be thin. However schedule section would be just a sentence; maybe better to incorporate schedule info into Requirements and not create a Schedule section. But we need to decide: The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule flexibility, so we could create a Schedule section. But we also have that same content in Requirements. Duplication is not prohibited; we just need to preserve all substantive information. Duplication preserves it twice, which is okay but maybe not ideal. However we could keep schedule section and keep requirement line as is; it's still preserving all info. It's not prohibited to duplicate. However the instruction says "Prefer a few substantive sections over many thin ones." Having a Schedule section with just one sentence might be thin. Might be better to omit Schedule section and keep flexibility under Requirements. But then we would not have a Schedule section even though posting states schedule info. The instruction says never create Schedule section unless posting actually states them. It does state them, so we could create it, but we could also choose not to, as it's not mandatory to create it. The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid thin sections. So we should not create a separate Schedule section; instead include schedule info under Requirements. Similarly, Pay section might be thin but it's substantive; we could keep Pay. Benefits section is substantive. Thus final sections: About the role, Responsibilities, Requirements (including schedule flexibility), Benefits, Pay. We should not include Schedule heading. Let's adjust Requirements to include flexibility. We'll keep Benefits and Pay. Now ensure we didn't include any boilerplate like "Attention search firms..." etc. We'll produce final HTML. Check for any leftover boilerplate: The posting had "While operating within the Bank's risk appetite, achieves results by consistently identifying, assessing, managing, monitoring, and reporting risks of all types." That's fine. We need to ensure we didn't include "SUPERVISORY RESPONSIBILITIES: None." We omitted. We need to ensure we didn't include "Working Conditions Normal office environment. Extensive viewing of computer screens." That's substantive; maybe we could include under Requirements or a separate section? It's about working conditions. Not a standard heading but we could incorporate into Requirements or maybe a separate section like "Working Conditions". But the instruction only gave examples of headings; we could add other headings if needed, but we prefer few sections. Working