Onsite Desktop Support II- Cincinnati, OH

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must include location, schedule, pay, benefits if present. The posting includes: "Onsite in Cincinnati Monday through Friday 8am to 5pm" (schedule). Pay: "$28.00 an hour plus full benefits". So we have Pay and Benefits (full benefits). Also location: "Onsite in Cincinnati". Could be part of location paragraph. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only those with real content. We have content for About the role (paragraph after "About The Role"). Responsibilities: bullet list under "Along The Way, You Will Get To". Those are duties. Requirements/Qualifications/Skills: The "What We’re Looking For" section includes experience, education, skills. Could split into Requirements (experience), Qualifications (education), Skills (technical). But we can combine maybe. However we need to follow instruction: use headings only when posting has real specific content. We can create sections for each if content exists. We have "What You Can Expect" about culture, values, maybe not needed as a section; but could be part of Benefits? Not exactly. Probably we ignore. We have Pay and Benefits: we can make separate sections. Schedule: we have schedule line. Location: maybe include in a short p under a heading? There's no heading for location; we can just include in a p after maybe a brief intro? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and schedule in a p? But schedule we need its own section if we have content. We'll make a Schedule section with p. Pay section: p with "$28.00 an hour plus full benefits". Benefits section: maybe we can mention full benefits; but we already said benefits in pay. Could combine? But instruction: prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But we have separate headings for Pay and Benefits. If we combine, we would need to choose one heading. However we have both pay and benefits content; we could make a Pay section that includes pay and mention full benefits. Then we could skip Benefits section. Or we could make Benefits section with "full benefits". But that would be thin. Better to combine into Pay section: "$28.00 an hour plus full benefits". Then we don't need Benefits heading. Schedule: we have schedule. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Pay, Schedule. We need to decide what to put under Requirements vs Qualifications vs Skills. The "What We’re Looking For" includes experience, education, technical skills, soft skills. We could split: Requirements: experience (5+ years, installing/configuring, Office 365, mobile devices, ITSM ticketing). Qualifications: Bachelor’s degree in computer science or relevant field is a plus. Skills: exceptional customer service, analytics, problem-solving, technical knowledge, communication, etc. We'll create three sections: Requirements, Qualifications, Skills. Now we need to extract bullet points for responsibilities from "Along The Way, You Will Get To". Let's list them: - Providing level 2 desktop support as needed - Ensuring customer service is timely and accurate - Aligning service level agreements with business stakeholder priorities - Reporting on and driving performance against KPI’s and metrics - Handling customer concerns and complaints while overseeing 100% of incoming service desk requests, incidents, and issues - Gauging the effectiveness and efficiency of service delivery; develop and implement strategies for improving desktop service delivery - Developing and manage a broad range of technical IT projects. - Providing timely updates to senior helpdesk leaders and stakeholders on regular basis - Delivering enterprise level technical support covering a wide breadth of technical matters - Meeting with clients and managing technical resources as needed - Handling escalations from Systems Engineering and Systems Administration stakeholder teams We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet as is. Now for Requirements bullet list: - 5+ years of commensurate and progressive growth experience in a Service Desk or Help Desk technical support environment - Experience in installing and configuring computer systems, diagnosing and solving hardware/software faults, and logging and tracking any additional troubleshooting that may occur - Experience with Office 365 - Experience with mobile devices (both Android and iPhone) - Experience with ITSM ticketing systems such as ServiceNow is a plus Qualifications bullet list: - Bachelor’s degree in computer science or relevant field is a plus Skills bullet list: - Exceptional customer service, analytics, and problem-solving skills to ensure the best client solutions. - Expert technical knowledge with an understanding for managing multiple diverse environments - Excellent communication skills demonstrated ability to create comprehensive technology analysis documents, instruction sheets, and process documentation for current and potential programs. - Ability to facilitate technical meetings, and convey technical information to non-technical staff - Proactive communicator with all levels of staff and management with the ability to maintain open communication with others - Self-motivated with directed exceptional customer service orientation and dedication to meeting deadlines - Excellent organization, time management and analytical skills - History of balancing multiple priorities and the ability to adapt and change focus as deadlines or customer needs shift We need to ensure we don't include boilerplate like EEO etc. Remove those. Also remove "Insight at a Glance" bullet list (global stats) as it's boilerplate? It's not exactly boilerplate but it's company info; maybe we can keep as part of About the role? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Insight at a Glance" is not exactly those but could be considered company overview; but it's not required to keep. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "Insight at a Glance" is substantive info about company; but it's not about the role. However it's not explicitly prohibited. It might be considered boilerplate? Not sure. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say remove company overview. So we could keep it. But we need to decide where to place it. Could be a short p after the heading? There's no heading for company overview. Could be part of About the role? Might be weird. Probably better to omit as it's not directly about the role and could be considered filler. However it's substantive info about the company; but the instruction says preserve ALL substantive information; but also "Prefer a few substantive sections over many thin ones." The company overview is not about the role; but it's still substantive. However typical job postings include such info; but we are to reformat job posting into clean HTML; likely we should keep it as a paragraph maybe under a heading like "About Insight"? But we don't have a heading for that. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. It says "include a section ONLY when the posting has real, specific content for it". So we could add a section "About Insight" if we have content. The posting has "Insight at a Glance" bullet list. That is specific content. So we could add a section "About Insight" with ul li. However the instruction list of example headings does not include About Insight, but it's not prohibited. It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not exclusive. So we can add About Insight. But we need to avoid duplication: The "Insight at a Glance" bullet list includes: 14,000+ engaged teammates globally, $8.2 billion in revenue in 2025, Certified as a Great Place to work in 9 Countries in 2025, Fortune 500 Company (No. 447) in 2025, Received 25+ industry and partner awards in the past year, $1.4M+ total charitable contributions in 2024 by Insight globally. We'll keep that. Now also there is a paragraph after that: "Now is the time to bring your expertise to Insight. We are not just a tech company; we are a people-first company..." That's also substantive about company values. Could be part of About Insight as well. Thus we could have About Insight section with paragraphs and ul. Then About the role section. Then Responsibilities. Then Requirements, Qualifications, Skills. Then Pay (including schedule? Actually schedule separate). We'll have Pay section with p: "$28.00 an hour plus full benefits". Then Schedule section with p: "Onsite in Cincinnati Monday through Friday 8am to 5pm". Location maybe included in schedule paragraph? Could add location: "Onsite in Cincinnati". We'll combine: "Onsite in Cincinnati Monday through Friday 8am to 5pm". That covers location and schedule. Now we need to ensure we don't repeat job title. No heading for job title. Now output HTML fragment only. Let's craft:

About Insight

Now is the time to bring your expertise to Insight. We are not just a tech company; we are a people-first company. We believe that by unlocking the power of people and technology, we can accelerate transformation and achieve extraordinary results. As a Fortune 500 Solutions Integrator with deep expertise in cloud, data, AI, cybersecurity, and intelligent edge, we guide organizations through complex digital decisions.

• 14,000+ engaged teammates globally
• $8.2 billion in revenue in 2025
• Certified as a Great Place to work in 9 Countries in 2025
• Fortune 500 Company (No. 447) in 2025
• Received 25+ industry and partner awards in the past year
• $1.4M+ total charitable contributions in 2024 by Insight globally

About the Role

This position will be the technical escalation point for the Level 2 Service Desk and onsite support users. The role requires a high level of technical proficiency and an individual with executive presence and good communication skills. Must quickly and effectively diagnose, and resolve issues related to desktop, laptops, mobile devices, printers, and video conferencing. The organization is looking for an individual who is customer focused, passionate about the end user experience, enjoys challenging themselves constantly to improve, and empowering the end user community by providing IT knowledge and tools.

Responsibilities

• Providing level 2 desktop support as needed
• Ensuring customer service is timely and accurate
• Aligning service level agreements with business stakeholder priorities
• Reporting on and driving performance against KPI’s and metrics
• Handling customer concerns and complaints while overseeing 100% of incoming service desk requests, incidents, and issues
• Gauging the effectiveness and efficiency of service delivery; develop and implement strategies for improving desktop service delivery
• Developing and manage a broad range of technical IT projects.
• Providing timely updates to senior helpdesk leaders and stakeholders on regular basis
• Delivering enterprise level technical support covering a wide breadth of technical matters
• Meeting with