Support Agent I

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Renaissance" then "Job Description". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: About Renaissance (company overview) maybe treat as "About the role"? Actually "About Renaissance" is about company, not role. Could map to "About the role"? Might be "About the role"? But we have "Job Description" which includes responsibilities. We have "Qualifications". We have "Bonus Points" maybe skills. We have "Additional Information" includes salary range (Pay) and benefits. So we need sections: About the role? Could use "About the role" for company overview? Might be okay. Or we could have "About Renaissance" as a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those headings if content matches. So we can have:

About the role

with paragraph about Renaissance mission etc.

Responsibilities

with

• list of duties from "In this role as Support Agent I, you will be responsible for:" bullet list.

  Qualifications

  with
  • list from "For this role as a Support Agent I, you should have:" bullet list.

    Skills

    maybe from Bonus Points? Could treat Bonus Points as skills. Or we could include them under Qualifications? But we have separate Bonus Points; we could put them under Skills.

    Pay

    with salary range paragraph.

    Benefits

    with list of benefits. We should not include Schedule (no info). Also not include Requirements (maybe same as Qualifications). We'll follow instruction: prefer few substantive sections over many thin ones. Could combine Bonus Points into Qualifications or Skills. But we have Qualifications already; Bonus Points could be considered "Preferred qualifications". Might be okay to add a section "Preferred Qualifications". But instruction only gave examples; we could still add a heading like "Preferred Qualifications" if content exists. However they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should stick to those headings. So we should map Bonus Points to Skills or Qualifications. Since they are "Bonus Points" (preferred), we could put them under Skills. Thus sections: About the role, Responsibilities, Qualifications, Skills, Pay, Benefits. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must strip out all the EEO paragraphs, accommodation, employment authorization, etc. Also remove "Additional Information" heading? We'll extract salary and benefits from there. We must not repeat the job title as a heading. The job title is Support Agent I; we won't add heading for it. We must not put Job ID/requisition numbers as headings (none present). We must output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role paragraph: combine the "About Renaissance" paragraph(s). Keep all info: global leader in pre-K–12 education technology, solutions help educators analyze, customize, plan personalized learning paths, allowing time for creating energizing learning experiences, fiercely passionate employees and educational partners have helped drive phenomenal student growth, solutions used in over one-third of US schools and >100 countries, mission values: trust each other, win together, strive for the best, own our actions, grow and evolve. We'll put that in

    . Responsibilities: list each bullet from the responsibilities block. Need to keep each duty exactly as written. The block includes many items separated by line breaks. We'll convert each line to

    . Ensure we keep punctuation. Responsibilities list: - Manage customer support interactions across multiple channels (phone, chat, email) with professionalism, empathy, and active listening to fully understand issues before proposing solutions - Troubleshoot common technical issues including login problems, browser compatibility, and basic connectivity within established SLA timelines - Resolve routine inquiries, conduct product walk-throughs, and provide accurate information through comprehensive research and knowledge base utilization - Develop and maintain working knowledge of supported products, their core features, and system interconnections - Troubleshoot customer issues across supported operating systems and browsers following established procedures - Navigate support tools and customer accounts to verify configurations and identify root causes - Document all customer interactions, troubleshooting steps, and resolutions accurately in the ticketing system - Adhere to case management guidelines and workflows to ensure proper ticket handling and routing - Escalate complex technical problems to senior support staff with clear, comprehensive documentation - Meet or exceed established metric goals including response time, resolution time, customer satisfaction, and quality assurance standards - Analyze customer needs and route requests to appropriate departments when specialized assistance is required - Contribute to department projects and continuous improvement initiatives We'll put each as

    . Qualifications: list from "For this role as a Support Agent I, you should have:" bullet list. - Exceptional customer service skills with demonstrated ability to deliver professional support via phone, email, and chat channels - Strong written and verbal communication skills with the ability to translate technical information into clear, user-friendly language for diverse audiences - Proven reliability, quality-focused mindset, and customer-centric approach to problem-solving - Ability to quickly learn complex systems, products, and integrations while identifying customer needs and implementing efficient solutions - Positive attitude with strong collaboration skills and commitment to fostering a supportive team culture - Familiarity with data analytics tools such as SQL or Power BI for basic reporting and data analysis We'll put as

    . Skills (Bonus Points): list: - Proficiency with Microsoft Suite products - Background in education technology or a background in education - Experience with Salesforce CRM and JIRA ticketing systems for case management and workflow tracking - Previous experience supporting customers in a SaaS environment, preferably with Renaissance products - Background in call center or high-volume support environments with demonstrated ability to manage multiple priorities We'll put as

    . Pay: Salary Range: $34,900-$40,200 This range is based on national market data and may vary by experience and location. We'll put in

    . Benefits: list from "Benefits For Eligible US Employees Include" bullet list. - World Class Health Benefits: Medical, Prescription, Dental, Vision, Telehealth - Health Savings and Flexible Spending Accounts - 401(k) and Roth 401(k) with company match - Paid Vacation and Sick Time Off - 12 Paid Holidays - Parental Leave (20 total weeks with 14 weeks paid) & Milk Stork program - Tuition Reimbursement - Life & Disability Insurance - Well-being and Employee Assistance Programs We'll put as

    • . We must not include the sentence "Benefits listed apply to eligible U.S. employees in accordance with Renaissance’s benefits eligibility criteria. Contractor and other non‑employee roles are not eligible for Renaissance employee benefits." That's boilerplate? It's still benefits info but maybe considered boilerplate? It's still substantive about eligibility. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This sentence is not exactly boilerplate but could be considered eligibility clarification. Might keep? It's not duplicated. It's about benefits eligibility. Might be considered part of benefits. Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence as well. However it's a sentence after the list. We'll include it as a

      after the list. Also we have "Frequently cited statistics show that some women, underrepresented individuals, protected veterans and individuals with disabilities may only apply to roles if they meet 100% of the qualifications. At Renaissance, we encourage all applications. Roles evolve over time, especially with innovation, and you may be just the person we need for the future!" That's EEO/boilerplate; remove. Also "Equal Opportunity Employer..." remove. Also "For California Residents, please see our Privacy Notice..." remove. Also "Reasonable Accommodations..." remove. Also "Employment Authorization..." remove. Also "For more information about Renaissance, visit: https://www.renaissance.com" maybe consider boilerplate? It's a link to company; could be considered navigation? Probably remove as it's not substantive to job. Thus final HTML:

      About the role

      When you join Renaissance®, you join a global leader in pre-K–12 education technology! Renaissance’s solutions help educators analyze, customize, and plan personalized learning paths for students, allowing time for what matters—creating energizing learning experiences in the classroom. Our fiercely passionate employees and educational partners have helped drive phenomenal student growth, with Renaissance solutions being used in over one-third of US schools and in more than 100 countries worldwide. Every day, we are connected to our mission by exemplifying our values: trust each other, win together, strive for the best, own our actions, and grow and evolve.

      Responsibilities

      • Manage customer support interactions across multiple channels (phone, chat, email) with professionalism, empathy, and active listening to fully understand issues before proposing solutions
      • Troubleshoot common technical issues including login problems, browser compatibility, and basic connectivity within established SLA timelines
      • Resolve routine inquiries, conduct product walk-throughs, and provide accurate information through comprehensive research and knowledge base utilization
      • Develop and maintain working knowledge of supported products, their core features, and system interconnections
      • Troubleshoot customer issues across supported operating systems and browsers following established procedures
      • Navigate support tools and customer accounts to verify configurations and identify root causes
      • Document all customer interactions, troubleshooting steps, and resolutions accurately in the ticketing system
      • Adhere to case management guidelines and workflows to ensure proper ticket handling and routing
      • Escalate complex technical problems to senior support staff with clear, comprehensive documentation
      • Meet or exceed established metric goals including response time, resolution time, customer satisfaction, and quality assurance standards
      • Analyze customer needs and route requests to appropriate departments when specialized assistance is required
      • Contribute to department projects and continuous improvement initiatives

      Qualifications

      • Exceptional customer service skills with demonstrated ability to deliver professional support via phone, email, and chat channels
      • Strong written and verbal communication skills with the ability to translate technical information into clear, user-friendly language for diverse audiences
      • Proven reliability, quality-focused mindset, and customer-centric approach to problem-solving
      • Ability to quickly learn complex systems, products, and integrations while identifying customer needs and implementing efficient solutions
      • Positive attitude with strong collaboration skills and commitment to fostering a supportive team culture
      • Familiarity with data analytics tools such as SQL or Power BI for basic reporting and data analysis

      Skills

      • Proficiency with Microsoft Suite products
      • Background in education technology or a background in education
      • Experience with Salesforce CRM and JIRA ticketing systems for case management