Desktop Support Technician - (NOC) Arlington Heights, IL
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to parse the job description.
Let's extract sections:
Brief Description About the Job: description paragraph.
Then "What will you do?" list of duties.
Then "This is a 40-hour week, which may vary to accommodate 5 days x 8-hour coverage from the onsite team." That's schedule info.
Then "Requirements" heading.
Then bullet list of requirements.
Then "Physical Requirements" bullet list.
Then "If you are…" maybe a paragraph about motivation.
Then "What We Will Offer" includes subheadings: Personal & Professional Development, Diversity, Inclusion & Belonging, Salary, Benefits.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can combine some.
- About the role: could be the brief description paragraph.
- Responsibilities: the "What will you do?" list.
- Requirements: the bullet list under Requirements.
- Qualifications: maybe certifications (Comp IT (A+, Network+, Security+), or equivalent certification) and experience? Could be part of Requirements but we can separate.
- Skills: maybe the list of technical skills (Windows, Mac, Android, iOS, networking, printing, etc.) but that's also in requirements.
- Benefits: the benefits list (Medical Insurance, Vision & Dental plans, PTO time, Perkbox discounts, On-site Paid Parking). Also Personal & Professional Development could be considered benefits but we can include under Benefits or separate? The instruction: include a section only when posting has real, specific content for it. We have Benefits content, so we can have Benefits section.
- Pay: The posting says "Salary We offer a competitive range based on suitability or experience." That's vague, not specific numbers. The instruction: 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. For Pay, they say "competitive range based on suitability or experience" which is vague but still states something. Is that considered filler? It's not a specific number, but it's a statement. The instruction says avoid filler like "commensurate with experience". "competitive range based on suitability or experience" is similar to that. Likely we should omit Pay section because it's not specific. So we will not include Pay.
- Schedule: They said "This is a 40-hour week, which may vary to accommodate 5 days x 8-hour coverage from the onsite team." That's specific: 40-hour week, may vary to accommodate 5 days x 8-hour coverage. That's schedule info. So we can include Schedule section.
Now we need to output HTML fragment with headings
and content.
We must not repeat job title. No markdown.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove boilerplate: EEO statement, etc. Also remove duplicated lines.
Let's extract content precisely.
Brief Description About the Job: "As a Desktop Support Technician, you will be responsible for providing IT support to end users for Windows PCs, Macs, printers, mobile devices, desktop applications, and other associated hardware & software. This position will support one or more departments to restore service and/or identify and correct core problems. Ensuring that all hardware issues are effectively and efficiently resolved in line with our customers’ contractual service level agreements (SLAs)."
That's prose.
What will you do? list:
- Provide in-person, phone, remote, and email support to users of supported departments.
- Keep the ticketing system up to date with the status off all support requests. (typo "off" but keep as is)
- Keep inventory system up to date with all deployed computing asset information.
- Research, recommend, and order software and hardware requested by departments.
- Create and provision user accounts, email accounts, and necessary access for user staff.
- Provides support to end users in problem resolution for both Windows and Apple systems.
- Guides end users through troubleshooting procedures.
- Performs upgrades to hardware and software.
- Supports printing and other peripheral computing devices.
- Performs set-up, installation, and configuration of desktop hardware and software in compliance with internal controls, policies, and standards.
- Participates in the identity and access management of various systems.
- Other IT support duties to be assigned
We need to keep each as
- .
Schedule: "This is a 40-hour week, which may vary to accommodate 5 days x 8-hour coverage from the onsite team."
That's prose.
Requirements heading: list:
- 1 - 3 years of experience providing Helpdesk/Desktop Support or Field Services, which includes troubleshooting hardware, software, connectivity, and operating system issues
- 1 - 3 years of experience with current Microsoft Windows Desktop software
- 1 - 3 years of experience support - DSS, Multiple Workstation OS (Windows, Mac), Multiple Mobile OS (Android, iOS), Networking, Printing Services, etc.
- Experience in fulfilling the onboarding and offboarding requests (i.e., set-up of desktop/laptop / IPAD, installing screens & displays, patch port cabling, software configuration, mobile setup)
- Experience in supporting performance and resolving client-related issues
- Understanding of network protocols, server hardware, and configurations
- Self-motivated with a willingness to learn and adapt to any new change or situation
- Able to communicate effectively with peers, line manager, stakeholders & client end users.
- Comp IT (A+, Network+, Security+), or equivalent certification
Physical Requirements:
- Able to lift or push 20-50 pounds of equipment if needed.
- Able to stand or kneel for extended periods of time.
- Able to use mechanical tools. (Screwdrivers, wrenches, pliers, hammers & drills)
If you are…. paragraph: "Motivated to develop your career in IT support, supported by a strong learning and development culture, you are passionate about delivering service excellence and like the variety of end-user environments we should connect and explore."
That's prose.
What We Will Offer:
- Personal & Professional Development: paragraph about unlimited access to training, L&D system, etc.
- Diversity, Inclusion & Belonging: paragraph about inclusivity.
- Salary: "We offer a competitive range based on suitability or experience."
- Benefits: list: Medical Insurance, Vision & Dental plans, PTO time, Perkbox discounts, On-site Paid Parking
Then Who Are We etc: that's boilerplate about company; we should remove as it's not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who Are We" section is not exactly boilerplate but could be considered company description; but it's not a required heading. However we might keep it as part of About the role? But we already have About the role from brief description. The "Who Are We" is extra company info; could be considered boilerplate? It's not legal/EEO but it's generic marketing. The instruction says remove boilerplate, but not explicitly to remove company description. However we should preserve ALL substantive information; the "Who Are We" is substantive about the company. But the allowed headings do not include a company overview section. We could incorporate into About the role? But About the role is about the job, not company. The instruction says "Prefer a few substantive sections over many thin ones." We could add a section like "About the Company" but not in allowed headings. The allowed headings list is not exhaustive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not strict list. But we should follow the pattern: use those headings when appropriate. If we have company info, we could put under About the role? Might be okay to add a separate About the Company? But not in list. Safer to incorporate into About the role? However the brief description already covers job responsibilities; adding company info may be okay as part of About the role? The instruction: "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." It doesn't forbid other headings. But to be safe, we could include a section "About the Company" as
About the Company. But the examples didn't list it; but they said e.g., meaning examples. I think it's okay to add a section for company overview if there is substantive content. However the instruction also says "Prefer a few substantive sections over many thin ones." So we could merge company info into About the role? But About the role is about the job; mixing company info might be less appropriate. However we could treat the brief description as About the role, and then add a separate section "About the Company" with the Who Are We paragraph. That seems reasonable.
But we need to check if any of that content is boilerplate: It's a description of the company, its history, values, etc. It's not legal boilerplate. So we keep.
Now we need to decide which sections to output:
- About the role (brief description)
- Responsibilities (What will you do?)
- Requirements (the list)
- Qualifications (maybe certifications and experience? Could be part of Requirements but we can separate: Qualifications could include the certification line and maybe the experience years? But we already have experience in Requirements. To avoid duplication, we could put Qualifications as the certification line only. But we need to preserve all info; we can keep Requirements as the experience bullets, and Qualifications as the certification bullet. However the certification bullet is already in Requirements list. If we split, we would duplicate. Better to keep Requirements as all bullets (including certification). Then we may not need Qualifications section. But we have a heading Qualifications allowed; we could omit if no specific content beyond what's already in Requirements. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we omit Qualifications, that's fine.
- Skills: maybe we could list technical skills (Windows, Mac, Android, iOS, networking, printing, etc.) but those are already in Requirements. Could create Skills section but would duplicate. Better to omit.
- Benefits: we have specific benefits list.
- Schedule: we have schedule info.
- Pay: we have vague statement; we should omit.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly also About the Company.
But we need to check if any content left out: The "If you are…. Motivated to develop your career..." paragraph is motivational; could be part of About the role or a separate section like "About You". Not in allowed headings. Could be folded into About the role as prose? It's about candidate motivation. Could be included as a short
under About the role? Might be okay. But we already have About the role paragraph; we could add another
after it. That would preserve the info.
Similarly, Personal & Professional Development and Diversity, Inclusion & Belonging are under What We Will Offer. Could
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to parse the job description. Let's extract sections: Brief Description About the Job: description paragraph. Then "What will you do?" list of duties. Then "This is a 40-hour week, which may vary to accommodate 5 days x 8-hour coverage from the onsite team." That's schedule info. Then "Requirements" heading. Then bullet list of requirements. Then "Physical Requirements" bullet list. Then "If you are…" maybe a paragraph about motivation. Then "What We Will Offer" includes subheadings: Personal & Professional Development, Diversity, Inclusion & Belonging, Salary, Benefits. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some. - About the role: could be the brief description paragraph. - Responsibilities: the "What will you do?" list. - Requirements: the bullet list under Requirements. - Qualifications: maybe certifications (Comp IT (A+, Network+, Security+), or equivalent certification) and experience? Could be part of Requirements but we can separate. - Skills: maybe the list of technical skills (Windows, Mac, Android, iOS, networking, printing, etc.) but that's also in requirements. - Benefits: the benefits list (Medical Insurance, Vision & Dental plans, PTO time, Perkbox discounts, On-site Paid Parking). Also Personal & Professional Development could be considered benefits but we can include under Benefits or separate? The instruction: include a section only when posting has real, specific content for it. We have Benefits content, so we can have Benefits section. - Pay: The posting says "Salary We offer a competitive range based on suitability or experience." That's vague, not specific numbers. The instruction: 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. For Pay, they say "competitive range based on suitability or experience" which is vague but still states something. Is that considered filler? It's not a specific number, but it's a statement. The instruction says avoid filler like "commensurate with experience". "competitive range based on suitability or experience" is similar to that. Likely we should omit Pay section because it's not specific. So we will not include Pay. - Schedule: They said "This is a 40-hour week, which may vary to accommodate 5 days x 8-hour coverage from the onsite team." That's specific: 40-hour week, may vary to accommodate 5 days x 8-hour coverage. That's schedule info. So we can include Schedule section. Now we need to output HTML fragment with headings
and content.
We must not repeat job title. No markdown.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove boilerplate: EEO statement, etc. Also remove duplicated lines.
Let's extract content precisely.
Brief Description About the Job: "As a Desktop Support Technician, you will be responsible for providing IT support to end users for Windows PCs, Macs, printers, mobile devices, desktop applications, and other associated hardware & software. This position will support one or more departments to restore service and/or identify and correct core problems. Ensuring that all hardware issues are effectively and efficiently resolved in line with our customers’ contractual service level agreements (SLAs)."
That's prose.
What will you do? list:
- Provide in-person, phone, remote, and email support to users of supported departments.
- Keep the ticketing system up to date with the status off all support requests. (typo "off" but keep as is)
- Keep inventory system up to date with all deployed computing asset information.
- Research, recommend, and order software and hardware requested by departments.
- Create and provision user accounts, email accounts, and necessary access for user staff.
- Provides support to end users in problem resolution for both Windows and Apple systems.
- Guides end users through troubleshooting procedures.
- Performs upgrades to hardware and software.
- Supports printing and other peripheral computing devices.
- Performs set-up, installation, and configuration of desktop hardware and software in compliance with internal controls, policies, and standards.
- Participates in the identity and access management of various systems.
- Other IT support duties to be assigned
We need to keep each as
- .
Schedule: "This is a 40-hour week, which may vary to accommodate 5 days x 8-hour coverage from the onsite team."
That's prose.
Requirements heading: list:
- 1 - 3 years of experience providing Helpdesk/Desktop Support or Field Services, which includes troubleshooting hardware, software, connectivity, and operating system issues
- 1 - 3 years of experience with current Microsoft Windows Desktop software
- 1 - 3 years of experience support - DSS, Multiple Workstation OS (Windows, Mac), Multiple Mobile OS (Android, iOS), Networking, Printing Services, etc.
- Experience in fulfilling the onboarding and offboarding requests (i.e., set-up of desktop/laptop / IPAD, installing screens & displays, patch port cabling, software configuration, mobile setup)
- Experience in supporting performance and resolving client-related issues
- Understanding of network protocols, server hardware, and configurations
- Self-motivated with a willingness to learn and adapt to any new change or situation
- Able to communicate effectively with peers, line manager, stakeholders & client end users.
- Comp IT (A+, Network+, Security+), or equivalent certification
Physical Requirements:
- Able to lift or push 20-50 pounds of equipment if needed.
- Able to stand or kneel for extended periods of time.
- Able to use mechanical tools. (Screwdrivers, wrenches, pliers, hammers & drills)
If you are…. paragraph: "Motivated to develop your career in IT support, supported by a strong learning and development culture, you are passionate about delivering service excellence and like the variety of end-user environments we should connect and explore."
That's prose.
What We Will Offer:
- Personal & Professional Development: paragraph about unlimited access to training, L&D system, etc.
- Diversity, Inclusion & Belonging: paragraph about inclusivity.
- Salary: "We offer a competitive range based on suitability or experience."
- Benefits: list: Medical Insurance, Vision & Dental plans, PTO time, Perkbox discounts, On-site Paid Parking
Then Who Are We etc: that's boilerplate about company; we should remove as it's not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Who Are We" section is not exactly boilerplate but could be considered company description; but it's not a required heading. However we might keep it as part of About the role? But we already have About the role from brief description. The "Who Are We" is extra company info; could be considered boilerplate? It's not legal/EEO but it's generic marketing. The instruction says remove boilerplate, but not explicitly to remove company description. However we should preserve ALL substantive information; the "Who Are We" is substantive about the company. But the allowed headings do not include a company overview section. We could incorporate into About the role? But About the role is about the job, not company. The instruction says "Prefer a few substantive sections over many thin ones." We could add a section like "About the Company" but not in allowed headings. The allowed headings list is not exhaustive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not strict list. But we should follow the pattern: use those headings when appropriate. If we have company info, we could put under About the role? Might be okay to add a separate About the Company? But not in list. Safer to incorporate into About the role? However the brief description already covers job responsibilities; adding company info may be okay as part of About the role? The instruction: "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." It doesn't forbid other headings. But to be safe, we could include a section "About the Company" as
About the Company. But the examples didn't list it; but they said e.g., meaning examples. I think it's okay to add a section for company overview if there is substantive content. However the instruction also says "Prefer a few substantive sections over many thin ones." So we could merge company info into About the role? But About the role is about the job; mixing company info might be less appropriate. However we could treat the brief description as About the role, and then add a separate section "About the Company" with the Who Are We paragraph. That seems reasonable.
But we need to check if any of that content is boilerplate: It's a description of the company, its history, values, etc. It's not legal boilerplate. So we keep.
Now we need to decide which sections to output:
- About the role (brief description)
- Responsibilities (What will you do?)
- Requirements (the list)
- Qualifications (maybe certifications and experience? Could be part of Requirements but we can separate: Qualifications could include the certification line and maybe the experience years? But we already have experience in Requirements. To avoid duplication, we could put Qualifications as the certification line only. But we need to preserve all info; we can keep Requirements as the experience bullets, and Qualifications as the certification bullet. However the certification bullet is already in Requirements list. If we split, we would duplicate. Better to keep Requirements as all bullets (including certification). Then we may not need Qualifications section. But we have a heading Qualifications allowed; we could omit if no specific content beyond what's already in Requirements. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we omit Qualifications, that's fine.
- Skills: maybe we could list technical skills (Windows, Mac, Android, iOS, networking, printing, etc.) but those are already in Requirements. Could create Skills section but would duplicate. Better to omit.
- Benefits: we have specific benefits list.
- Schedule: we have schedule info.
- Pay: we have vague statement; we should omit.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly also About the Company.
But we need to check if any content left out: The "If you are…. Motivated to develop your career..." paragraph is motivational; could be part of About the role or a separate section like "About You". Not in allowed headings. Could be folded into About the role as prose? It's about candidate motivation. Could be included as a short
under About the role? Might be okay. But we already have About the role paragraph; we could add another
after it. That would preserve the info.
Similarly, Personal & Professional Development and Diversity, Inclusion & Belonging are under What We Will Offer. Could
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO statement, etc. Also remove duplicated lines. Let's extract content precisely. Brief Description About the Job: "As a Desktop Support Technician, you will be responsible for providing IT support to end users for Windows PCs, Macs, printers, mobile devices, desktop applications, and other associated hardware & software. This position will support one or more departments to restore service and/or identify and correct core problems. Ensuring that all hardware issues are effectively and efficiently resolved in line with our customers’ contractual service level agreements (SLAs)." That's prose. What will you do? list: - Provide in-person, phone, remote, and email support to users of supported departments. - Keep the ticketing system up to date with the status off all support requests. (typo "off" but keep as is) - Keep inventory system up to date with all deployed computing asset information. - Research, recommend, and order software and hardware requested by departments. - Create and provision user accounts, email accounts, and necessary access for user staff. - Provides support to end users in problem resolution for both Windows and Apple systems. - Guides end users through troubleshooting procedures. - Performs upgrades to hardware and software. - Supports printing and other peripheral computing devices. - Performs set-up, installation, and configuration of desktop hardware and software in compliance with internal controls, policies, and standards. - Participates in the identity and access management of various systems. - Other IT support duties to be assigned We need to keep each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not strict list. But we should follow the pattern: use those headings when appropriate. If we have company info, we could put under About the role? Might be okay to add a separate About the Company? But not in list. Safer to incorporate into About the role? However the brief description already covers job responsibilities; adding company info may be okay as part of About the role? The instruction: "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." It doesn't forbid other headings. But to be safe, we could include a section "About the Company" as
About the Company. But the examples didn't list it; but they said e.g., meaning examples. I think it's okay to add a section for company overview if there is substantive content. However the instruction also says "Prefer a few substantive sections over many thin ones." So we could merge company info into About the role? But About the role is about the job; mixing company info might be less appropriate. However we could treat the brief description as About the role, and then add a separate section "About the Company" with the Who Are We paragraph. That seems reasonable. But we need to check if any of that content is boilerplate: It's a description of the company, its history, values, etc. It's not legal boilerplate. So we keep. Now we need to decide which sections to output: - About the role (brief description) - Responsibilities (What will you do?) - Requirements (the list) - Qualifications (maybe certifications and experience? Could be part of Requirements but we can separate: Qualifications could include the certification line and maybe the experience years? But we already have experience in Requirements. To avoid duplication, we could put Qualifications as the certification line only. But we need to preserve all info; we can keep Requirements as the experience bullets, and Qualifications as the certification bullet. However the certification bullet is already in Requirements list. If we split, we would duplicate. Better to keep Requirements as all bullets (including certification). Then we may not need Qualifications section. But we have a heading Qualifications allowed; we could omit if no specific content beyond what's already in Requirements. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. If we omit Qualifications, that's fine. - Skills: maybe we could list technical skills (Windows, Mac, Android, iOS, networking, printing, etc.) but those are already in Requirements. Could create Skills section but would duplicate. Better to omit. - Benefits: we have specific benefits list. - Schedule: we have schedule info. - Pay: we have vague statement; we should omit. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly also About the Company. But we need to check if any content left out: The "If you are…. Motivated to develop your career..." paragraph is motivational; could be part of About the role or a separate section like "About You". Not in allowed headings. Could be folded into About the role as prose? It's about candidate motivation. Could be included as a short
under About the role? Might be okay. But we already have About the role paragraph; we could add another
after it. That would preserve the info. Similarly, Personal & Professional Development and Diversity, Inclusion & Belonging are under What We Will Offer. Could