Technical Support Specialist I

We need to output HTML fragment with sections: About the role? Actually we have sections: About Amplix (company description) maybe not needed? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only sections that have real content. The posting includes: Job Summary (maybe treat as About the role?), Duties and Responsibilities, Key Competencies (maybe Skills), Education/Experience (Qualifications), Certifications (maybe none), Compensation (Pay). Also there is a description of Amplix (About Amplix) maybe could be About the role? But they said do NOT repeat the job title as a heading. They gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About Amplix: company overview. Could be placed under "About the role"? Actually "About the role" is more about the job, not company. But we could include a short paragraph about the role under "About the role". The job summary is essentially about the role. So we can put that under

About the role

with a

containing the job summary. - Duties and Responsibilities:

Responsibilities

with

• items. - Key Competencies: could be Skills. So

  Skills

  with list. - Education/Experience: Qualifications. So

  Qualifications

  with list. - Certifications: None required. Since no specific content, we should not create a Certifications section (as per rule: only include section when posting has real, specific content). So skip. - Compensation: Pay. So

  Pay

  with

  containing compensation range. - Benefits: Not mentioned, so skip. - Schedule: Not explicitly mentioned, though hours mentioned: 8:00 a.m. to 8:00 p.m. EST, after-hours calls if needed. That is schedule info. Could be considered Schedule. The posting says "you'll provide friendly phone support for wireless requests from 8:00 a.m. to 8:00 p.m. EST." That's schedule. So we can include Schedule section with that detail. - Also there is mention of working with TSS II and SrTSS etc. That's duties. We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. We must remove cookie/navigation/legal/EEO etc. The posting includes an EEO statement at end: "Amplix does not discriminate...". That's boilerplate; we should remove it. Also we need to remove duplicated lines. Let's extract content: Job Title: Technical Support Specialist I (not to be used as heading) Department: Mobility Managed Services (maybe minor metadata; we can fold into short p or drop). Probably we can include in a short p under About the role? Not required but we can include as metadata. Reports To: Technical Support Specialist Operations Manager (metadata) About Amplix: paragraphs. Job Summary: "As a Technical Support Specialist I, you'll provide friendly phone support for wireless requests from 8:00 a.m. to 8:00 p.m. EST. You'll troubleshoot issues, assist with MDM support, process activations, and manage warranty replacements, while also being available for after-hours calls if needed. You'll work with TSS II and SrTSS to handle client orders within a 4-hour service level agreement (SLA), implement process improvements, and manage inventory requests while ensuring we meet data security policies." Duties and Responsibilities list: - Handle incoming wireless requests via telephone from 8:00 a.m. to 8:00 p.m. EST. - Assist with troubleshooting, MDM support, activations, and warranty replacements. - Be available for after-hours call outs as needed. - Manage client order activities, ensuring timely completion within a 4-hour service level agreement (SLA) in collaboration with TSS II and SrTSS. - Identify, document, and implement at least one measurable process improvement initiative annually. - Handle inventory requests. - Ensure all optimization plan changes are completed before the next billing cycle for assigned clients. - Maintain awareness of and comply with company policies related to Data Security (DS) and Personal Information (PI). - Report any suspicious activities concerning DS or PI to management promptly. Key Competencies list: - Excellent interpersonal, communication and time management skills. - Excellent customer service skills. - Strong active listening skills. - Astute learner with competent troubleshooting skills. - Excellent organizational skills with ability to prioritize multiple tasks. - High functioning computer literacy including Microsoft Office Suite, SharePoint, Excel. Measurements: Not a section we need; it's about performance assessment. Could be considered part of Qualifications? But it's not a heading we have; we could ignore or maybe include under Qualifications? The instruction says use headings from list; we can ignore Measurements as not required. Education/Experience: - High school diploma required. - Previous customer service experience preferred but not required. Certifications: None required. Compensation: - The compensation range for this position is $19.00-$20.00 USD. - The target hiring range for this role may vary based on geographic location and other factors, including merit or performance, demonstrated proficiency, skills for the role, education, travel requirements, and experience. - The posted range reflects our ability to hire at different titles and levels depending on background and experience. - The company reserves the right to offer additional compensation at its discretion, for example, in the form of a discretionary bonus or sales commission. We need to preserve all substantive information; we can include that as a paragraph under Pay. Schedule: from Job Summary: 8:00 a.m. to 8:00 p.m. EST, after-hours calls if needed. Also maybe mention 4-hour SLA but that's not schedule. We'll put schedule details. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

  About the role

  [Job Summary]

  Responsibilities

  • ...
  ...

  Skills

  • ...
  ...

  Qualifications

  • High school diploma required.
  • Previous customer service experience preferred but not required.

  Pay

  The compensation range for this position is $19.00-$20.00 USD. The target hiring range for this role may vary based on geographic location and other factors, including merit or performance, demonstrated proficiency, skills for the role, education, travel requirements, and experience. The posted range reflects our ability to hire at different titles and levels depending on background and experience. The company reserves the right to offer additional compensation at its discretion, for example, in the form of a discretionary bonus or sales commission.

  Schedule

  Work hours are from 8:00 a.m. to 8:00 p.m. EST, with availability for after-hours calls as needed.

  We might also include department/reports-to as a short p under About the role? Could add after job summary: "Department: Mobility Managed Services. Reports to: Technical Support Specialist Operations Manager." But that's metadata; we can include as a short p. We must not repeat the job title as heading; fine. We must not include boilerplate EEO; we removed. Check for any duplicated lines: we have not. Now ensure we preserve all substantive information: Did we miss anything? The "Measurements" section about performance assessment: we omitted. Is that substantive? It's about how performance will be assessed. Could be considered part of Qualifications or maybe a separate section like "Performance Metrics". But not in allowed headings. Since we cannot create new headings not in list, we could incorporate into Qualifications or Skills? Probably better to add a short paragraph under Qualifications about performance assessment? But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use those for section headings. Likely we should only use those headings. So we cannot add a Measurements heading. We could incorporate that info into Qualifications or Skills as a sentence. But we must preserve all substantive information; we can add a

  under Qualifications about performance assessment. However Qualifications currently is a list; we could add a

  after list. That's okay. Similarly, "Measurements" includes: Performance will be assessed based on adherence to service level agreements. Evaluation will include the average duration of customer interactions. Metrics will reflect the percentage of error-free orders processed. Assessment will be conducted on the quality of calls handled. We can add a

  under Qualifications: "Performance will be assessed based on adherence to service level agreements, including average duration of customer interactions, percentage of error-free orders processed, and quality of calls handled." Now also there is a line about "Ensure all optimization plan changes are completed before the next billing cycle for assigned clients." That's in duties; we have it. Also "Identify, document, and implement at least one measurable process improvement initiative annually." included. Now also "Manage inventory requests." included. Now also "Maintain awareness of and comply with company policies related to Data Security (DS) and Personal Information (PI)." included. Now also "Report any suspicious activities concerning DS or PI to management promptly." included. Now also "Be available for after-hours call outs as needed." included. Now also "Handle incoming wireless requests via telephone from 8:00 a.m. to 8:00 p.m. EST." included. Now also "Assist with troubleshooting, MDM support, activations, and warranty replacements." included. Now also "Manage client order activities, ensuring timely completion within a 4-hour service level agreement (SLA) in collaboration with TSS II and SrTSS." included. Now also "You'll work with TSS II and SrTSS to handle client orders within a 4-hour service level agreement (SLA), implement process improvements, and manage inventory requests while ensuring we meet data security policies." That's in job summary; we have some of that. Now also "Through thousands of advisory engagements, we've influenced and optimized hundreds of millions of dollars in IT spend..." That's company description; we might include under About the role? Actually we have About Amplix description; we could incorporate that into About the role section as a brief company overview. The instruction: About the role heading could include company description? It's ambiguous but we can include it as part of About the role. Thus About the role

  will contain the Amplix overview plus job summary? Might be too long but okay. We need to not repeat the job title as heading; fine. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now output HTML. Let's craft:

  About the role

  Amplix is a leading technology advisory firm that helps organizations accelerate business transformation through innovative technology. With 3,500+ customers nationwide, we deliver increased speed to value and reduced risk across the full IT ecosystem — from CX, IT infrastructure, cloud, and security to mobility and beyond. Through thousands of advisory engagements, we've influenced and optimized hundreds of millions of dollars in IT spend, helping clients build flexible, scalable, and resilient technology solutions that give them a strategic advantage. Headquartered in Norwood, MA, with offices and remote employees across the country, Amplix is a national company with a close-knit culture. Our people share a common set of values and a passion for helping clients, partners, and each other succeed. As a Technical Support Specialist