Desktop Support Technician (Windows 10/11)
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 include sections only if they have real content. The posting includes:
- Location: Windsor Locks, CT Onsite – Monday-Friday 8am-5pm (maybe schedule)
- About The Opportunity (prose)
- Responsibilities (list)
- Required Qualifications (list)
- Preferred Qualifications (list)
- What We're Looking For (prose)
- Skills (list)
- Pay And Benefits (pay range and benefits list)
- Workplace Type (fully onsite)
- Application Deadline (date)
- About TEKsystems (company description) – but that's boilerplate? It's about the company, maybe we can keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" is not exactly boilerplate but could be considered company description; but it's repeated later. Might be considered not essential? However we need to preserve ALL substantive information; but we can drop duplicated lines. The "About TEKsystems" appears twice with similar content. We could keep one concise paragraph? But we must not invent or summarize away detail. However we can drop duplicated lines. The repeated content is largely same; we could keep one instance. But is that considered substantive? It's about the company; maybe we can keep a short paragraph about TEKsystems. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we can combine company info into a short
under a section like "About the Company" but not listed as allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "About the Company". So we might omit that section entirely, as it's not required. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can omit the About TEKsystems section because it's not one of the prescribed headings and we don't have a heading for it. However we could fold it into a short
under something else? Probably better to omit.
We need to include schedule: The posting says "Onsite – Monday-Friday 8am-5pm". That's schedule info. So we can have a Schedule section with that.
Pay And Benefits: we have pay range and benefits list. So we need a Pay section? The instruction says use headings like Pay, Benefits, Schedule. Could combine Pay and Benefits under one heading? They said "Prefer a few substantive sections over many thin ones." So we could have a single section "Pay and Benefits" but the allowed headings list includes Pay and Benefits separately. However we can still use
Pay
and Benefits
but that would be thin. Better to combine into one section maybe "Pay and Benefits" but not in the list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. So we can use other headings if needed, but they gave examples. I think we can use "Pay and Benefits" as a heading; it's still an h3. That would be okay.
Similarly, we could have "Workplace Type" maybe as part of Schedule or separate. Could combine schedule and workplace type under "Schedule and Workplace". But we have separate info: schedule (Mon-Fri 8am-5pm) and workplace type (fully onsite). Could combine.
We need to preserve all substantive information: location, schedule, about opportunity, responsibilities, required qualifications, preferred qualifications, what we're looking for, skills, pay, benefits, workplace type, application deadline.
We must remove application instructions (like "Apply today if you're passionate...") Actually that is a call to action; maybe considered application instruction? It says "Apply today if you're passionate about technology, enjoy helping end users, and are looking for a long-term opportunity supporting enterprise IT environments." That's basically an encouragement to apply; could be considered application instruction. The instruction says remove application instructions. So we should drop that line.
Also remove duplicated lines: The "About TEKsystems" duplicated; we will drop.
Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate: The long EEO statements at end; drop.
Also remove "Job Type & Location This is a Contract position based out of Windsor Locks, CT." That's job type and location; we need to keep location and maybe job type? The location is already given; job type (Contract) is substantive. We should keep it. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Job type is not a heading; we can include in a short
.
We need to keep schedule: Monday-Friday 8am-5pm.
We need to keep pay range: $17.00 - $20.00/hr.
Benefits list: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave).
We need to keep workplace type: fully onsite.
Application deadline: Sep 18, 2026.
We need to keep "About The Opportunity" prose.
We need to keep responsibilities list.
We need to keep required qualifications list.
We need to keep preferred qualifications list.
We need to keep "What We're Looking For" prose.
We need to keep skills list.
Now structure:
We'll have sections:
About the Opportunity
... (the prose)
Responsibilities
- ... each line
Required Qualifications
- ... each line
Preferred Qualifications
- ... each line
What We're Looking For
... prose
Skills
- ... each skill (maybe comma separated? The list is given as a comma-separated list; we can split into items)
Pay and Benefits
Pay: $17.00 - $20.00/hr.
- Benefits items
Schedule and Workplace
Schedule: Monday‑Friday, 8 am – 5 pm (onsite).
Workplace Type: Fully onsite in Windsor Locks, CT.
maybe combine.
But we also have location already; we could include location in this section.
Application deadline: we could add a short under maybe a section "Important Dates" but not in list. Could add a
after schedule: "
Application deadline: September 18, 2026.
"
We need to avoid filler. All content is substantive.
Now ensure we don't repeat the job title. Not needed.
Now produce HTML fragment.
Let's extract the exact prose:
About The Opportunity: "We are seeking a customer-focused Desktop Support Technician to join a growing enterprise IT support team. This role is responsible for providing hands-on deskside support, troubleshooting hardware and software issues, deploying new equipment, supporting mobile devices, and delivering an exceptional end-user experience. This is an excellent opportunity for an IT professional who enjoys working directly with users, solving technical issues, and supporting a dynamic corporate environment."
We'll put that in .
Responsibilities list: each line:
- Provide onsite deskside support for Windows 10 and Windows 11 systems
- Diagnose and resolve hardware and software issues on desktops, laptops, and peripherals
- Perform PC installations, moves, adds, and changes (IMAC activities)
- Image, configure, deploy, and replace workstation devices
- Support Microsoft Office 365 applications including Outlook, Word, Excel, and PowerPoint
- Troubleshoot printing, connectivity, and peripheral device issues
- Support and configure iOS and Android mobile devices
- Assist users with email, VPN, wireless networking, and application-related issues
- Maintain accurate documentation and ticket updates within IT service management tools
- Perform asset management activities including tagging, inventory tracking, recovery, and disposal
- Provide walk-up technical support and maintain high levels of customer satisfaction
- Follow established IT support processes and best practices
Required Qualifications list:
- 2+ years of desktop or deskside support experience in a corporate environment
- Experience supporting Windows 10 and/or Windows 11
- Strong hardware troubleshooting and break/fix experience
- Experience imaging and deploying desktop and laptop systems
- Experience supporting Microsoft Office 365 applications
- Ability to troubleshoot basic networking issues, including VPN, wireless connectivity, and network adapters
- Experience supporting mobile devices including iPhone and Android
- Experience working with IT ticketing systems
- Strong communication, customer service, and problem-solving skills
- Ability to work independently while also collaborating within a team environment
Preferred Qualifications list:
- Enterprise-level desktop support experience
- Experience with asset management and inventory control
- Tech Bar or walk-up support experience
- Familiarity with IT service management practices
What We're Looking For prose: "We're looking for a technician who combines strong technical troubleshooting abilities with outstanding customer service skills. Successful candidates will be patient, professional, and comfortable supporting users with varying levels of technical knowledge while providing a high-quality support experience."
Skills list: given as "Windows 10/11Desktop SupportDesksideSupportOffice 365OutlookHardware Break/FixPC Imaging & DeploymentMobile Device Support (iOS/Android)VPN & Wireless TroubleshootingAsset ManagementPrinter SupportIT TicketingSystemsCustomer Service". It seems missing spaces. We need to parse: Probably they intend each skill separated by no space? Let's split logically: Windows 10/11, Desktop Support, Deskside Support, Office 365, Outlook, Hardware Break/Fix, PC Imaging & Deployment, Mobile Device Support (iOS/Android), VPN & Wireless Troubleshooting, Asset Management, Printer Support, IT Ticket
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 include sections only if they have real content. The posting includes: - Location: Windsor Locks, CT Onsite – Monday-Friday 8am-5pm (maybe schedule) - About The Opportunity (prose) - Responsibilities (list) - Required Qualifications (list) - Preferred Qualifications (list) - What We're Looking For (prose) - Skills (list) - Pay And Benefits (pay range and benefits list) - Workplace Type (fully onsite) - Application Deadline (date) - About TEKsystems (company description) – but that's boilerplate? It's about the company, maybe we can keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TEKsystems" is not exactly boilerplate but could be considered company description; but it's repeated later. Might be considered not essential? However we need to preserve ALL substantive information; but we can drop duplicated lines. The "About TEKsystems" appears twice with similar content. We could keep one concise paragraph? But we must not invent or summarize away detail. However we can drop duplicated lines. The repeated content is largely same; we could keep one instance. But is that considered substantive? It's about the company; maybe we can keep a short paragraph about TEKsystems. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we can combine company info into a short
under a section like "About the Company" but not listed as allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "About the Company". So we might omit that section entirely, as it's not required. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can omit the About TEKsystems section because it's not one of the prescribed headings and we don't have a heading for it. However we could fold it into a short
under something else? Probably better to omit. We need to include schedule: The posting says "Onsite – Monday-Friday 8am-5pm". That's schedule info. So we can have a Schedule section with that. Pay And Benefits: we have pay range and benefits list. So we need a Pay section? The instruction says use headings like Pay, Benefits, Schedule. Could combine Pay and Benefits under one heading? They said "Prefer a few substantive sections over many thin ones." So we could have a single section "Pay and Benefits" but the allowed headings list includes Pay and Benefits separately. However we can still use
Pay
andBenefits
but that would be thin. Better to combine into one section maybe "Pay and Benefits" but not in the list. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. So we can use other headings if needed, but they gave examples. I think we can use "Pay and Benefits" as a heading; it's still an h3. That would be okay. Similarly, we could have "Workplace Type" maybe as part of Schedule or separate. Could combine schedule and workplace type under "Schedule and Workplace". But we have separate info: schedule (Mon-Fri 8am-5pm) and workplace type (fully onsite). Could combine. We need to preserve all substantive information: location, schedule, about opportunity, responsibilities, required qualifications, preferred qualifications, what we're looking for, skills, pay, benefits, workplace type, application deadline. We must remove application instructions (like "Apply today if you're passionate...") Actually that is a call to action; maybe considered application instruction? It says "Apply today if you're passionate about technology, enjoy helping end users, and are looking for a long-term opportunity supporting enterprise IT environments." That's basically an encouragement to apply; could be considered application instruction. The instruction says remove application instructions. So we should drop that line. Also remove duplicated lines: The "About TEKsystems" duplicated; we will drop. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate: The long EEO statements at end; drop. Also remove "Job Type & Location This is a Contract position based out of Windsor Locks, CT." That's job type and location; we need to keep location and maybe job type? The location is already given; job type (Contract) is substantive. We should keep it. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Job type is not a heading; we can include in a short
. We need to keep schedule: Monday-Friday 8am-5pm. We need to keep pay range: $17.00 - $20.00/hr. Benefits list: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). We need to keep workplace type: fully onsite. Application deadline: Sep 18, 2026. We need to keep "About The Opportunity" prose. We need to keep responsibilities list. We need to keep required qualifications list. We need to keep preferred qualifications list. We need to keep "What We're Looking For" prose. We need to keep skills list. Now structure: We'll have sections:
About the Opportunity
... (the prose)
Responsibilities
- ... each line
Required Qualifications
- ... each line
Preferred Qualifications
- ... each line
What We're Looking For
... prose
Skills
- ... each skill (maybe comma separated? The list is given as a comma-separated list; we can split into items)
Pay and Benefits
Pay: $17.00 - $20.00/hr.
- Benefits items
Schedule and Workplace
Schedule: Monday‑Friday, 8 am – 5 pm (onsite).
Workplace Type: Fully onsite in Windsor Locks, CT.
maybe combine. But we also have location already; we could include location in this section. Application deadline: we could add a shortunder maybe a section "Important Dates" but not in list. Could add a
after schedule: "
Application deadline: September 18, 2026.
" We need to avoid filler. All content is substantive. Now ensure we don't repeat the job title. Not needed. Now produce HTML fragment. Let's extract the exact prose: About The Opportunity: "We are seeking a customer-focused Desktop Support Technician to join a growing enterprise IT support team. This role is responsible for providing hands-on deskside support, troubleshooting hardware and software issues, deploying new equipment, supporting mobile devices, and delivering an exceptional end-user experience. This is an excellent opportunity for an IT professional who enjoys working directly with users, solving technical issues, and supporting a dynamic corporate environment." We'll put that in. Responsibilities list: each line: - Provide onsite deskside support for Windows 10 and Windows 11 systems - Diagnose and resolve hardware and software issues on desktops, laptops, and peripherals - Perform PC installations, moves, adds, and changes (IMAC activities) - Image, configure, deploy, and replace workstation devices - Support Microsoft Office 365 applications including Outlook, Word, Excel, and PowerPoint - Troubleshoot printing, connectivity, and peripheral device issues - Support and configure iOS and Android mobile devices - Assist users with email, VPN, wireless networking, and application-related issues - Maintain accurate documentation and ticket updates within IT service management tools - Perform asset management activities including tagging, inventory tracking, recovery, and disposal - Provide walk-up technical support and maintain high levels of customer satisfaction - Follow established IT support processes and best practices Required Qualifications list: - 2+ years of desktop or deskside support experience in a corporate environment - Experience supporting Windows 10 and/or Windows 11 - Strong hardware troubleshooting and break/fix experience - Experience imaging and deploying desktop and laptop systems - Experience supporting Microsoft Office 365 applications - Ability to troubleshoot basic networking issues, including VPN, wireless connectivity, and network adapters - Experience supporting mobile devices including iPhone and Android - Experience working with IT ticketing systems - Strong communication, customer service, and problem-solving skills - Ability to work independently while also collaborating within a team environment Preferred Qualifications list: - Enterprise-level desktop support experience - Experience with asset management and inventory control - Tech Bar or walk-up support experience - Familiarity with IT service management practices What We're Looking For prose: "We're looking for a technician who combines strong technical troubleshooting abilities with outstanding customer service skills. Successful candidates will be patient, professional, and comfortable supporting users with varying levels of technical knowledge while providing a high-quality support experience." Skills list: given as "Windows 10/11Desktop SupportDesksideSupportOffice 365OutlookHardware Break/FixPC Imaging & DeploymentMobile Device Support (iOS/Android)VPN & Wireless TroubleshootingAsset ManagementPrinter SupportIT TicketingSystemsCustomer Service". It seems missing spaces. We need to parse: Probably they intend each skill separated by no space? Let's split logically: Windows 10/11, Desktop Support, Deskside Support, Office 365, Outlook, Hardware Break/Fix, PC Imaging & Deployment, Mobile Device Support (iOS/Android), VPN & Wireless Troubleshooting, Asset Management, Printer Support, IT Ticket