Service Desk Technician I
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only when posting has real specific content. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Application Deadline: The sooner you apply..." etc. Also remove "Work Authorization Criteria", "Workspace Requirements And Remote Work Policy", "Our Commitment to a Diverse Workforce" etc. Those are EEO/diversity and legal boilerplate; remove them. Also remove "FLSA Status: Salaried, Non-Exempt" maybe considered metadata? It's not a heading; but it's minor metadata; we can fold into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph for things like location, schedule, pay, benefits if they exist. But we also have dedicated sections for Pay, Schedule, Benefits if posting actually states them. The posting includes: "Location and Work Expectations This position is 100% onsite at our office location in Lombard, Illinois. Schedule: Monday to Friday, 8:00am to 5:00pm CST". So we have location and schedule. Also "The base pay range for this position is expected to be between $35,000 and $50,000." So we have pay. Also "The total compensation package for this position also includes medical benefits, 401(k) eligibility, and PTO." So we have benefits. Thus we should have sections: About the role (maybe from intro?), Responsibilities (the "What You Will Be Doing" list), Requirements (maybe "You'll be successful in this role if you have:" list), Qualifications (maybe "Bonus points for:" and "Desired Certifications:"?), Skills (maybe combine?), Benefits, Pay, Schedule. However we must not create sections with filler/placeholder text. Must ensure each section has substantive content. We need to decide which headings to use. The list of allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. - About the role: Could be the introductory paragraph(s) describing the role impact: "How You’ll Make An Impact As the Service Desk Technician, you will be at the forefront..." That's a description of role. So we can put that under About the role. - Responsibilities: The list under "What You Will Be Doing" includes many bullet points. Also the AI adoption part. So we can put that as Responsibilities. - Requirements: The list under "You'll be successful in this role if you have:" includes many items. That seems like requirements/qualifications. Could be Requirements. - Qualifications: Could be the "Bonus points for:" and "Desired Certifications:" etc. Or we could treat those as Qualifications. - Skills: Could be overlapping; maybe we can combine some. But we need to avoid thin sections. Perhaps we can put "Bonus points for:" and "Desired Certifications:" under Qualifications, and maybe Skills could be omitted if not enough distinct content. However we need to include sections only when posting has real specific content. If we don't have distinct content for Skills, we should omit it. But we have many skill-like items in Requirements already. Could we split? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. Qualifications and Skills could be omitted if content overlaps. But we have "Bonus points for:" and "Desired Certifications:" which are additional qualifications/preferred qualifications. Could be placed under Requirements as well, maybe as a sub-list. But we need to preserve all substantive info; we can include them under Requirements as part of the list. Thus we can have:
About the role
... (the impact paragraph)
Responsibilities
- ... each bullet
Requirements
- ... the "You'll be successful..." list
- ... Bonus points for: ...
- ... Desired Certifications: ...
after About the role. But we have Schedule and Pay and Benefits sections. Schedule: we have schedule details. Pay: we have base pay range. Benefits: medical benefits, 401(k) eligibility, PTO. Thus we will have sections: About the role (includes impact paragraph and location maybe) Responsibilities Requirements Benefits Pay Schedule We must not create sections with filler/placeholder text. All have content. Now we need to strip boilerplate: remove EEO, diversity, work authorization, workspace requirements, application deadline, etc. Also remove duplicated lines. We need to preserve all substantive info: that includes the list of responsibilities, requirements, bonus points, desired certifications, pay, benefits, schedule, location. We must not invent or summarize away detail. So we need to keep each bullet exactly as in posting? We can keep the substance but maybe we can trim redundant phrasing? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, not omit any. However we can rephrase? It says do not invent or summarize away detail. Summarizing away detail would be removing details. So we must keep all details. That means we cannot condense bullet points; we need to keep each point. However we can combine multiple sentences into one bullet if they are originally separate? The original has bullet points separated by line breaks but not necessarily bullet formatting. We need to output
- for any list of duties/requirements/benefits. So we need to split into list items. We must ensure we don't lose any detail.
Thus we need to extract each distinct item.
Let's parse the posting.
First, intro: "Are you looking for limitless career opportunities with a company that values growth, innovation, and teamwork? At Ntiva, we’re more than a Managed Services Provider, we’re a community dedicated to helping each other, our clients, and their businesses thrive both personally and professionally. Ntiva is a culture of people who are passionate about the work…and each other. Our clients view us as an essential part of their teams, relying on us for strategic guidance, fast solutions to complex challenges, and proactive support. With strategic locations across the U.S. and leadership from our founder, Steven Freidkin, we’re on the front lines of a fast-paced industry, facing cybersecurity threats and rapid technology changes together. If you thrive in a dynamic, supportive environment and enjoy going above and beyond, we’d love to meet you. Come explore one of our many opportunities and grow with us!"
That's generic fluff; but it's part of the posting. Should we keep? It's substantive? It's about company culture. Might be considered boilerplate? Not exactly EEO, but it's generic marketing. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This intro is not explicitly listed as boilerplate to remove. It's part of the "About the role" maybe. We can keep it under About the role.
Then "How You’ll Make An Impact As the Service Desk Technician, you will be at the forefront of delivering top-tier customer service and technical expertise. You are not just a technician; you are the first line of defense, ensuring our clients' technology experience is nothing short of exceptional. In addition to answering incoming phone calls and providing elite customer service by troubleshooting Windows and Apple devices, you will also be interacting with AI to validate and correct automated resolutions."
That's more specific to role. We'll include that.
Then "Location and Work Expectations This position is 100% onsite at our office location in Lombard, Illinois. Schedule: Monday to Friday, 8:00am to 5:00pm CST"
We'll handle location maybe in About the role or separate short p. Since we have Schedule section, we can put schedule there. Location we can include in About the role paragraph.
Then "What You Will Be Doing Handle traditional Tier 1 service desk responsibilities, including:" then a list.
We need to extract each bullet:
- Answer incoming client troubleshooting calls and emails
- Manage client service tickets from triage through resolution or escalation while meeting SLOs
- Follow up on open tickets and keep clients informed of status updates
- Provision and deprovision user accounts and prepare laptops and desktops for deployment
- Maintain accurate, up-to-date client documentation
- Record clear, detailed case notes in the Ntiva ticketing system
- Identify and communicate potential issues or failure points in client systems and processes
- Review, improve, and create Standard Operating Procedures (SOPs)
- Receive and verify inbound packages, label assets, and update ConnectWise.
- Package, label, and stage outbound shipments for carrier pickup.
- Lead AI adoption and continuous improvement as a core part of the role: (then sub-bullets)
- Use AI-assisted tools as the default first step for triage, troubleshooting, and drafting client communications
- Test new internal AI features and workflows before broader rollout, documenting successes, issues, and tuning needs
- Identify recurring ticket patterns that could benefit from AI automation and help refine related prompts or logic
- Provide structured feedback to internal AI tooling teams on accuracy, tone, and missed edge cases
- Coach fellow technicians on using AI tools effectively in daily ticket work
- Validate AI-suggested resolutions before applying them to client systems, using sound judgment and appropriate skepticism
We need to keep all these as list items. The "Lead AI adoption..." could be a parent bullet with sub-items; but we only need flat list? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can keep flat by making each sub-item a separate li. However we might lose the grouping. But we can keep the lead AI adoption as a li and then sub-items as nested ul. That's still a list. Probably acceptable. We'll keep nested. Then "You'll be successful in this role if you have:" list: - At least 1 year of professional work experience in the IT industry - Client-focused mindset with a positive, service-oriented attitude - Strong problem-solving skills and curiosity about emerging AI tools and workflows - Comfort testing evolving AI tools as an early adopter and providing specific, actionable feedback - Strong organization and time-management skills, with the ability to balance client cases and AI testing responsibilities - Excellent written and verbal communication skills - Ability to assess the business impact of technical issues and solutions - Ability to contribute to a collaborative, supportive team environment - Strong attention to detail when validating AI-suggested resolutions before implementation - Basic understanding of how AI tools generate responses and where technician review is required - Ability to document processes, outcomes, and AI tool feedback clearly - Ability to explain complex technical concepts in simple terms for non-technical users - Familiarity with Office