Late Shift Contact Center Representative (Tue-Sat, 3pm-Midnight) w/Onsite Training- Nashville, TN

We need to output only HTML fragment, using

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

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. Let's read the posting: - Opening paragraph: "Thank you for your interest in a career at Regions. At Regions, we believe associates deserve more than just a job. We believe in offering performance-driven individuals a place where they can build a career --- a place to expect more opportunities. If you are focused on results, dedicated to quality, strength and integrity, and possess the drive to succeed, then we are your employer of choice. Regions is dedicated to taking appropriate steps to safeguard and protect private and personally identifiable information you submit. The information that you submit will be collected and reviewed by associates, consultants, and vendors of Regions in order to evaluate your qualifications and experience for job opportunities and will not be used for marketing purposes, sold, or shared outside of Regions unless required by law. Such information will be stored in accordance with regulatory requirements and in conjunction with Regions’ Retention Schedule for a minimum of three years. You may review, modify, or update your information by visiting and logging into the careers section of the system." This is generic boilerplate about privacy, data retention. Should we remove? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is privacy/data retention, maybe considered legal boilerplate. Likely we should remove it. However, we need to preserve substantive information. This seems not substantive about the job. So we can drop it. - "Job Description" heading then paragraph: "If you are passionate about making a difference in the lives of others, you’ll excel with a company that focuses on the financial wellbeing of its customers. As a banker in the Regions’ Contact Center, you will gain a foundation of banking knowledge by working in the heart of our customer service operations. Our Leadership Team takes an active role in your career growth by investing in your development through ongoing coaching and mentoring. Our core values motivate and drive us to do the best for our customers and associates every day. Our Contact Center Bankers Help enrich our customer’s lives by answering questions, solving problems, and providing solutions to ensure an effortless banking experience for our customers.Be the expert in a wide range of banking products and services. We use our banking expertise to help customers identify the next step to accomplish their financial goals. We believe in providing customers with advice, guidance, and education.Put the customer first. We value their relationship and show our commitment by implementing our core values into our everyday conversations. Our Bankers strive to provide solutions for immediate and long-term needs on every contact." This is description of role. Could be "About the role" or "Responsibilities". We need to decide which heading to use. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have "What’s In It For You" section: "The foundation you need to start your career in banking - a skillset you can use to improve customer’s lives by helping them make better financial decisions.Comprehensive and ongoing training that provides you with opportunities to learn and grow.Ongoing feedback/coaching, mentoring and development from leaders that care.Benefits including dynamic healthcare plans, tuition reimbursement, paid time off and regular performance reviews with salary elevations." That's benefits and maybe "What's in it for you" could be Benefits section. Then "Who We Are": "Our Core Values define our culture. Put People First, Focus on your Customer, Reach Higher, Do What is Right, and Enjoy Life. Our mission is to Make Life Better.We serve our communities. We encourage associates to invest in their communities by offering opportunities to volunteer, teach financial education, and give back with United Way.An industry leader in Associate Engagement and Customer Engagement. (Awards and Recognition by Gallup/JD Power) This position requires the tracking of time and is eligible for overtime under the non-exempt FLSA classification for hours worked in excess of 40 per week." That includes core values, mission, community involvement, awards, overtime note. Could be "About the company" but not in list of allowed headings. Could be omitted or maybe we can put under "About the role"? But we need to keep substantive info. Perhaps we can include a section "About the role" that includes description and maybe core values? However the instruction says we can only use those headings; we can also not include a heading if no real content. But we need to preserve all substantive info. We could embed the "Who We Are" content within a

  under a heading like "About the role" or maybe "Responsibilities". But "Who We Are" is about company, not role. However we could still include it as part of "About the role" maybe not ideal but we need to keep it. Alternatively we could create a section "About the role" for job description, and another section "Requirements" for requirements, "Skills And Competencies" for skills, "Benefits" for benefits, "Pay" for compensation details, "Schedule" for schedule info (Onsite 7-Week Training Schedule, After Training Work Schedule). Also we have "Preferences" (One (1) year customer service or production experience). That could be under Requirements or Qualifications. We also have technical specs for remote work: download/upload speed etc. That's part of Requirements (if remote). Should be included. We also have "Position Type Full time". That could be under Schedule or maybe a short p. We also have "Location Details Perimeter Hill Location: Nashville, Tennessee". That's location; could be a short p. We also have "Equal Opportunity Employer/including Disabled/Veterans" - that's EEO boilerplate, should be removed. We also have "Job applications at Regions are accepted electronically through our career site for a minimum of five business days from the date of posting. Job postings for higher-volume positions may remain active for longer than the minimum period due to business need and may be closed at any time thereafter at the discretion of the company." That's application instructions/boilerplate, should be removed. We also have "Start here, go anywhere! Our contact center associates have the opportunity to explore a wide variety of opportunities. Make this your day to kick start your Regions career!" That's motivational fluff; could be part of description but maybe we keep as part of "What's In It For You"? It's not specific benefit; maybe we can keep under "What's In It For You" as prose. We need to avoid filler/placeholder text like "commensurate with experience". Not present. Now we need to decide which sections to include. We have: - About the role / Responsibilities: job description paragraph(s). Could be combined. - Requirements: includes high school diploma or GED, onboarding training, abilities to observe text, detect verbal info, operate keyboard/mouse, work at computer extended periods, remote tech specs (download/upload speed, ethernet, etc). Also maybe "Ability to accurately observe stable and scrolling on-screen text and images" etc. Also "Ability to accurately detect verbal information and communicate verbally using a headset or speaker and microphone". Also "Ability to operate a keyboard and mouse to type and make on-screen selections". Also "Ability to work at a computer for extended periods of time". Also remote specs. - Skills And Competencies: list of abilities: adhere to policies, recommend products, multi-task, solve problems, work flexible schedule, basic computer skills, time management, excellent communication, general knowledge of basic banking, electronic banking and/or credit card services. - Preferences: "One (1) year customer service or production experience". Could be under Requirements or Qualifications. - Benefits: "Benefits including dynamic healthcare plans, tuition reimbursement, paid time off and regular performance reviews with salary elevations." Also later "Benefits Information Regions offers a benefits package that is flexible, comprehensive and recognizes that "one size does not fit all" for benefits-eligible associates. Listed below is a synopsis of the benefits offered by Regions for informational purposes, which is not intended to be a complete summary of plan terms and conditions. Paid Vacation/Sick Time 401K with Company Match Medical, Dental and Vision Benefits Disability Benefits Health Savings Account Flexible Spending Account Life Insurance Parental Leave Employee Assistance Program Associate Volunteer Program". So we have a list of benefits. - Pay: "Compensation Details Pay ranges are job specific and are provided as a point-of-market reference for compensation decisions. Other factors which directly impact pay for individual associates include: experience, skills, knowledge, contribution, job location and, most importantly, performance in the job role. As these factors vary by individuals, pay will also vary among individual associates within the same job. The target information listed below is based on the Metropolitan Statistical Area Market Range for where the position is located and level of the position. Minimum Job Range Target: $35,748.02 USD Median $42,940.00 USD Incentive Pay Plans This job is not incentive eligible." Thus we have pay range specifics. - Schedule: "Onsite 7-Week Training Schedule Monday-Friday 8:00am-5:00pm After Training Work Schedule Tuesday-Saturday 3pm-12am CST". Also maybe "Ability to work a flexible schedule which includes all hours of the contact center" (under skills). Also "This position requires the tracking of time and is eligible for overtime under the non-exempt FLSA classification for hours worked in excess of 40 per week." That's schedule/overtime. Thus we have schedule details. We also have location: "Perimeter Hill Location: Nashville, Tennessee". Could be a short p. We also have "Position Type Full time". Could be a short p. We need to avoid creating sections with filler. All sections we propose have real content. We need to output only HTML fragment, using

  for headings,

  • for lists,

    for prose. We must not repeat the job title as a heading. Not needed. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: privacy, EEO, application instructions, etc. We must preserve all substantive information. Now we need to decide which headings to use. Let's map: - About the role: could include job description paragraph(s) and maybe "Who We Are" (core values, mission, community involvement, awards). But "Who We Are" is about company; still could be part of "About the role" but maybe better to have a separate section "About the company"? Not in allowed headings. However we could incorporate it into "About the role" as prose. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples