IT Digital Workplace Analyst III
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/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Do not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary range and benefits description, so we can include Pay and Benefits sections. Schedule: mentions hybrid role, on-site 2-3 days, weekend on-call rotation. So we can include Schedule section.
We need sections: About the role (maybe a brief description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should avoid thin sections; combine if needed. But we can include all if they have content.
We need to extract content.
Let's parse posting:
- Intro: "Trusted Connectivity for AI-Powered Dominance..." etc. That's company description, maybe part of About the role? Could be "About the role" or "About Everfox". But we need to preserve substantive info. The job description: "Everfox is looking for a Service Desk technician to join our Global Digital Workplace Experience Team. The role will be focused on modernizing customer experience for our global employee base at Everfox, focused on enabling self-service, zero-touch request fulfillment, and accelerating the productivity needs of our employee base. The Service Desk technician will be exposed to multiple technology disciplines such as AV, Endpoint Management tools, Active Directory, O365, Exchange, and scripting languages. This is a Hybrid position working from the office in Herndon, VA. This position may participate in a weekend on-call rotation. Location: This is a hybrid role in Herndon, VA"
That's about the role.
Key Responsibilities: bullet list (we need to extract each line). Let's list them:
- Serve as the first point of contact for customers seeking technical assistance/support over the phone, email, or via the company ticketing system (Jira).
- Take complete ownership of an end user problem, starting from request submission thru resolution
- Resolve issues independently whenever possible or escalate complex issues to appropriate technical personnel
- Maintain clear communication with users throughout the support process, providing timely updates on case status
- Develop and document standard operating procedures (SOPs) and customer service guidelines for IT support
- Build and maintain positive relationships with users by providing excellent customer service
- Learn and apply company policies, procedures, and technical skills to effectively complete assigned tasks
- Identify deviations from standard practices for non-routine situations
- Share information proactively to identify user needs and provide relevant data
- Work independently on most daily tasks with general oversight on routine work and detailed instructions for new assignments
- Strong understanding of personal computer hardware, software, and networking concepts
- Experience using video conferencing tools such as Teams and Zoom
- Excellent communication, interpersonal, and problem-solving skills
- Ability to learn new technologies and procedures quickly
- Maintain clear communication with users throughout the support process, providing timely updates on case status (duplicate)
- Identify opportunities for enabling self-service and zero-touch automation of repeatable service request
- Identify opportunities to improve First Contact Resolution of Incidents by Service Desk, by partnering with wider IT functions
- Act as a liaison between end users and IT, understanding the needs of the business and providing feedback to wider IT teams on service delivery improvement
- Investigate, diagnose, and solve varied Endpoint software and functionality problems
- Configure and deploy Everfox imaged Endpoints & additional software on computing devices
- Identify and streamline legacy processes, leverage scripts to automate repeatable tasks
- Liaison with multiple technology Vendors/Partners to identify, troubleshoot and eliminate end-user concerns
- Oversee local Employee On-boarding and Termination processes
- Document procedures, corrective actions, and update knowledge base system
- Partner with cross-functional IT teams to assist with troubleshooting Major Incidents impacting IT services as needed
- May participate in Weekend on-call support
Note duplicates: "Maintain clear communication..." appears twice; we should deduplicate.
Key Experience And Education Requirements:
- Bachelor’s degree or 1-3 years of experience with Service Desk, End User Experience, or regional IT support role
- Exposure to certain technology platforms, such as Active Directory, Microsoft O365, and Exchange Online
- Exposure to Windows OS and MacOS-based end-user computing devices
- Basic understanding of concepts such as DNS, DHCP, IP, LAN, Wireless, Virtual Private Network
- Comfortable working within complex IT infrastructure environments.
- Exceptionally strong written and verbal communication skills
- Have a customer-first approach, identify opportunities to mature service offerings to be self-served
- Passion for problem-solving, with an ability to identify technological solutions to business problems
- Understanding of performance metrics, benchmarks, and KPI’s
- Willingness to challenge and improve the status-quo and eliminate toil by streamlining processes and introducing automation as much as possible
- IT related certifications a plus (e.g. A+, ITIL, Jamf & Intune)
Pay: "A reasonable estimate of the base salary range for this role is: $56,200.00-73,700.00 USD The actual salary offered may vary within the range based on a candidates' unique experience, locale, and business needs."
Benefits: "In addition to a base salary and bonus plans, Everfox offers a generous benefits package including flexible PTO, a 401k match, and contribution to healthcare coverages. Our Talent Acquisition team will provide specific information regarding bonus eligibility and benefits offerings."
Schedule: "We’re hiring for a hybrid role. You’ll work on-site with your team several days each week (typically 2–3), with the specific days set by your manager. Because regular in-person collaboration is central to this job, we look for candidates who live within about 50 miles of the office. Everfox will consider reasonable accommodation as required by law." Also "This position may participate in a weekend on-call rotation." Also earlier: "This is a Hybrid position working from the office in Herndon, VA."
Thus schedule: hybrid, 2-3 days on-site, weekend on-call possible.
We need to output HTML with sections. Use
for each section heading. Use - for lists. Use
for prose.
We should avoid repeating same content. Also remove duplicated lines like "Maintain clear communication..." duplicate.
We need to decide which sections to include.
We have content for:
- About the role (intro description)
- Responsibilities (list)
- Requirements (maybe combine Experience/Education)
- Qualifications (maybe same as Requirements? Could separate but we have both Requirements and Qualifications? The posting has "Key Experience And Education Requirements". Could treat as Requirements. Qualifications maybe same? Could combine. But we can have Requirements section covering education/experience, and Skills section covering technical and soft skills.
We have Skills: from responsibilities list includes technical skills (hardware, networking, Teams/Zoom, etc.) and soft skills (communication, problem-solving). Also from requirements list includes communication skills, customer-first, problem-solving, metrics, etc. Could separate.
But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? However instructions: use headings for those specific headings if content exists. We have content for Requirements (education/experience). We also have content for Qualifications (maybe certifications, etc.) but we could put certifications under Skills or Requirements. Might be okay to have Qualifications separate with certifications.
But we need to avoid filler. Let's see if we have distinct content for Qualifications beyond Requirements: The posting includes "IT related certifications a plus (e.g. A+, ITIL, Jamf & Intune)". That's a qualification. Also "Understanding of performance metrics, benchmarks, and KPI’s" could be qualification. Also "Willingness to challenge and improve the status-quo". That's more of a skill/attribute.
We could make Qualifications include certifications and maybe metrics understanding. But we also have Skills for technical and soft skills.
Let's decide:
- About the role: paragraph(s) describing role and location/hybrid.
- Responsibilities: ul list of duties.
- Requirements: ul list of education/experience requirements (Bachelor's degree or 1-3 years experience, exposure to platforms, OS, networking concepts, comfortable in complex IT infrastructure, strong written/verbal communication, customer-first approach, passion for problem-solving, understanding of metrics/KPIs, willingness to challenge status-quo, IT certifications a plus). Actually many of those are more like qualifications/skills. But we can keep them.
- Skills: ul list of technical and soft skills: strong understanding of PC hardware/software/networking, experience with Teams/Zoom, excellent communication/interpersonal/problem-solving, ability to learn new tech quickly, identify opportunities for self-service/zero-touch, improve FCR, liaison, endpoint troubleshooting, configure/deploy imaged endpoints, streamline legacy processes/scripts, vendor liaison, oversee onboarding/termination, document procedures, partner with cross-functional teams for major incidents, weekend on-call (maybe schedule). But some of these are responsibilities. Might be overlapping.
Better to follow the posting's sections: Key Responsibilities (list), Key Experience And Education Requirements (list). Then we can add Benefits, Pay, Schedule.
Thus we can have:
About the role
... description ...
Responsibilities
...
Requirements
...
Benefits
...
(or but benefits are list)
Pay
...
Schedule
...
We should not include Qualifications if we already have Requirements covering similar. But we could still include Qualifications if we have distinct content like certifications. However we already included certifications in Requirements list. Might be okay to not have Qualifications.
We must not create sections with filler. Ensure each section has real content.
Now we need to strip boilerplate: EEO statements, accommodation request, legal, etc. Also remove duplicated lines like "Maintain clear communication..." duplicate.
Also remove "Everfox will consider reasonable accommodation as required by law." That's legal/EEO; remove.
Remove "Our Talent Acquisition team will provide specific information regarding bonus eligibility and benefits offerings." That's maybe part of benefits but it's generic; we can keep benefits specifics: flexible PTO, 401k match, contribution to healthcare coverages. The rest is generic; we can keep but it's not boilerplate? It's still about benefits but it's generic. Might keep.
Remove "Don’t meet every single qualification? Studies show..." that's application encouragement; remove.
Remove EEO paragraph about equal employment opportunity, disability, etc. Remove.
Remove "Everfox is a Federal Contractor..." etc. Remove.
Now craft HTML.
Let's write About the role paragraph: combine intro and location/hybrid.
"Everfox delivers trusted connectivity to protect the world’s most critical environments and safeguard the sensitive data powering decision advantage. Built for mission‑critical operations, Everfox protects what matters most by securing how data moves, how users access it, and how threats are neutralized across every domain. We enable mission speed and secure collaboration across networks, domains, and allies, while ensuring the data powering AI and advanced analytics remains trusted and protected. We don’t just defend systems; we deliver decision dominance.
Everfox is looking for a Service Desk technician to join our Global Digital Workplace Experience Team. The role will be
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Do not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary range and benefits description, so we can include Pay and Benefits sections. Schedule: mentions hybrid role, on-site 2-3 days, weekend on-call rotation. So we can include Schedule section. We need sections: About the role (maybe a brief description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should avoid thin sections; combine if needed. But we can include all if they have content. We need to extract content. Let's parse posting: - Intro: "Trusted Connectivity for AI-Powered Dominance..." etc. That's company description, maybe part of About the role? Could be "About the role" or "About Everfox". But we need to preserve substantive info. The job description: "Everfox is looking for a Service Desk technician to join our Global Digital Workplace Experience Team. The role will be focused on modernizing customer experience for our global employee base at Everfox, focused on enabling self-service, zero-touch request fulfillment, and accelerating the productivity needs of our employee base. The Service Desk technician will be exposed to multiple technology disciplines such as AV, Endpoint Management tools, Active Directory, O365, Exchange, and scripting languages. This is a Hybrid position working from the office in Herndon, VA. This position may participate in a weekend on-call rotation. Location: This is a hybrid role in Herndon, VA" That's about the role. Key Responsibilities: bullet list (we need to extract each line). Let's list them: - Serve as the first point of contact for customers seeking technical assistance/support over the phone, email, or via the company ticketing system (Jira). - Take complete ownership of an end user problem, starting from request submission thru resolution - Resolve issues independently whenever possible or escalate complex issues to appropriate technical personnel - Maintain clear communication with users throughout the support process, providing timely updates on case status - Develop and document standard operating procedures (SOPs) and customer service guidelines for IT support - Build and maintain positive relationships with users by providing excellent customer service - Learn and apply company policies, procedures, and technical skills to effectively complete assigned tasks - Identify deviations from standard practices for non-routine situations - Share information proactively to identify user needs and provide relevant data - Work independently on most daily tasks with general oversight on routine work and detailed instructions for new assignments - Strong understanding of personal computer hardware, software, and networking concepts - Experience using video conferencing tools such as Teams and Zoom - Excellent communication, interpersonal, and problem-solving skills - Ability to learn new technologies and procedures quickly - Maintain clear communication with users throughout the support process, providing timely updates on case status (duplicate) - Identify opportunities for enabling self-service and zero-touch automation of repeatable service request - Identify opportunities to improve First Contact Resolution of Incidents by Service Desk, by partnering with wider IT functions - Act as a liaison between end users and IT, understanding the needs of the business and providing feedback to wider IT teams on service delivery improvement - Investigate, diagnose, and solve varied Endpoint software and functionality problems - Configure and deploy Everfox imaged Endpoints & additional software on computing devices - Identify and streamline legacy processes, leverage scripts to automate repeatable tasks - Liaison with multiple technology Vendors/Partners to identify, troubleshoot and eliminate end-user concerns - Oversee local Employee On-boarding and Termination processes - Document procedures, corrective actions, and update knowledge base system - Partner with cross-functional IT teams to assist with troubleshooting Major Incidents impacting IT services as needed - May participate in Weekend on-call support Note duplicates: "Maintain clear communication..." appears twice; we should deduplicate. Key Experience And Education Requirements: - Bachelor’s degree or 1-3 years of experience with Service Desk, End User Experience, or regional IT support role - Exposure to certain technology platforms, such as Active Directory, Microsoft O365, and Exchange Online - Exposure to Windows OS and MacOS-based end-user computing devices - Basic understanding of concepts such as DNS, DHCP, IP, LAN, Wireless, Virtual Private Network - Comfortable working within complex IT infrastructure environments. - Exceptionally strong written and verbal communication skills - Have a customer-first approach, identify opportunities to mature service offerings to be self-served - Passion for problem-solving, with an ability to identify technological solutions to business problems - Understanding of performance metrics, benchmarks, and KPI’s - Willingness to challenge and improve the status-quo and eliminate toil by streamlining processes and introducing automation as much as possible - IT related certifications a plus (e.g. A+, ITIL, Jamf & Intune) Pay: "A reasonable estimate of the base salary range for this role is: $56,200.00-73,700.00 USD The actual salary offered may vary within the range based on a candidates' unique experience, locale, and business needs." Benefits: "In addition to a base salary and bonus plans, Everfox offers a generous benefits package including flexible PTO, a 401k match, and contribution to healthcare coverages. Our Talent Acquisition team will provide specific information regarding bonus eligibility and benefits offerings." Schedule: "We’re hiring for a hybrid role. You’ll work on-site with your team several days each week (typically 2–3), with the specific days set by your manager. Because regular in-person collaboration is central to this job, we look for candidates who live within about 50 miles of the office. Everfox will consider reasonable accommodation as required by law." Also "This position may participate in a weekend on-call rotation." Also earlier: "This is a Hybrid position working from the office in Herndon, VA." Thus schedule: hybrid, 2-3 days on-site, weekend on-call possible. We need to output HTML with sections. Use
for each section heading. Use - for lists. Use
for prose.
We should avoid repeating same content. Also remove duplicated lines like "Maintain clear communication..." duplicate.
We need to decide which sections to include.
We have content for:
- About the role (intro description)
- Responsibilities (list)
- Requirements (maybe combine Experience/Education)
- Qualifications (maybe same as Requirements? Could separate but we have both Requirements and Qualifications? The posting has "Key Experience And Education Requirements". Could treat as Requirements. Qualifications maybe same? Could combine. But we can have Requirements section covering education/experience, and Skills section covering technical and soft skills.
We have Skills: from responsibilities list includes technical skills (hardware, networking, Teams/Zoom, etc.) and soft skills (communication, problem-solving). Also from requirements list includes communication skills, customer-first, problem-solving, metrics, etc. Could separate.
But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? However instructions: use headings for those specific headings if content exists. We have content for Requirements (education/experience). We also have content for Qualifications (maybe certifications, etc.) but we could put certifications under Skills or Requirements. Might be okay to have Qualifications separate with certifications.
But we need to avoid filler. Let's see if we have distinct content for Qualifications beyond Requirements: The posting includes "IT related certifications a plus (e.g. A+, ITIL, Jamf & Intune)". That's a qualification. Also "Understanding of performance metrics, benchmarks, and KPI’s" could be qualification. Also "Willingness to challenge and improve the status-quo". That's more of a skill/attribute.
We could make Qualifications include certifications and maybe metrics understanding. But we also have Skills for technical and soft skills.
Let's decide:
- About the role: paragraph(s) describing role and location/hybrid.
- Responsibilities: ul list of duties.
- Requirements: ul list of education/experience requirements (Bachelor's degree or 1-3 years experience, exposure to platforms, OS, networking concepts, comfortable in complex IT infrastructure, strong written/verbal communication, customer-first approach, passion for problem-solving, understanding of metrics/KPIs, willingness to challenge status-quo, IT certifications a plus). Actually many of those are more like qualifications/skills. But we can keep them.
- Skills: ul list of technical and soft skills: strong understanding of PC hardware/software/networking, experience with Teams/Zoom, excellent communication/interpersonal/problem-solving, ability to learn new tech quickly, identify opportunities for self-service/zero-touch, improve FCR, liaison, endpoint troubleshooting, configure/deploy imaged endpoints, streamline legacy processes/scripts, vendor liaison, oversee onboarding/termination, document procedures, partner with cross-functional teams for major incidents, weekend on-call (maybe schedule). But some of these are responsibilities. Might be overlapping.
Better to follow the posting's sections: Key Responsibilities (list), Key Experience And Education Requirements (list). Then we can add Benefits, Pay, Schedule.
Thus we can have:
About the role
... description ...
Responsibilities
...
Requirements
...
Benefits
...
(or but benefits are list)
Pay
...
Schedule
...
We should not include Qualifications if we already have Requirements covering similar. But we could still include Qualifications if we have distinct content like certifications. However we already included certifications in Requirements list. Might be okay to not have Qualifications.
We must not create sections with filler. Ensure each section has real content.
Now we need to strip boilerplate: EEO statements, accommodation request, legal, etc. Also remove duplicated lines like "Maintain clear communication..." duplicate.
Also remove "Everfox will consider reasonable accommodation as required by law." That's legal/EEO; remove.
Remove "Our Talent Acquisition team will provide specific information regarding bonus eligibility and benefits offerings." That's maybe part of benefits but it's generic; we can keep benefits specifics: flexible PTO, 401k match, contribution to healthcare coverages. The rest is generic; we can keep but it's not boilerplate? It's still about benefits but it's generic. Might keep.
Remove "Don’t meet every single qualification? Studies show..." that's application encouragement; remove.
Remove EEO paragraph about equal employment opportunity, disability, etc. Remove.
Remove "Everfox is a Federal Contractor..." etc. Remove.
Now craft HTML.
Let's write About the role paragraph: combine intro and location/hybrid.
"Everfox delivers trusted connectivity to protect the world’s most critical environments and safeguard the sensitive data powering decision advantage. Built for mission‑critical operations, Everfox protects what matters most by securing how data moves, how users access it, and how threats are neutralized across every domain. We enable mission speed and secure collaboration across networks, domains, and allies, while ensuring the data powering AI and advanced analytics remains trusted and protected. We don’t just defend systems; we deliver decision dominance.
Everfox is looking for a Service Desk technician to join our Global Digital Workplace Experience Team. The role will be
for prose. We should avoid repeating same content. Also remove duplicated lines like "Maintain clear communication..." duplicate. We need to decide which sections to include. We have content for: - About the role (intro description) - Responsibilities (list) - Requirements (maybe combine Experience/Education) - Qualifications (maybe same as Requirements? Could separate but we have both Requirements and Qualifications? The posting has "Key Experience And Education Requirements". Could treat as Requirements. Qualifications maybe same? Could combine. But we can have Requirements section covering education/experience, and Skills section covering technical and soft skills. We have Skills: from responsibilities list includes technical skills (hardware, networking, Teams/Zoom, etc.) and soft skills (communication, problem-solving). Also from requirements list includes communication skills, customer-first, problem-solving, metrics, etc. Could separate. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? However instructions: use headings for those specific headings if content exists. We have content for Requirements (education/experience). We also have content for Qualifications (maybe certifications, etc.) but we could put certifications under Skills or Requirements. Might be okay to have Qualifications separate with certifications. But we need to avoid filler. Let's see if we have distinct content for Qualifications beyond Requirements: The posting includes "IT related certifications a plus (e.g. A+, ITIL, Jamf & Intune)". That's a qualification. Also "Understanding of performance metrics, benchmarks, and KPI’s" could be qualification. Also "Willingness to challenge and improve the status-quo". That's more of a skill/attribute. We could make Qualifications include certifications and maybe metrics understanding. But we also have Skills for technical and soft skills. Let's decide: - About the role: paragraph(s) describing role and location/hybrid. - Responsibilities: ul list of duties. - Requirements: ul list of education/experience requirements (Bachelor's degree or 1-3 years experience, exposure to platforms, OS, networking concepts, comfortable in complex IT infrastructure, strong written/verbal communication, customer-first approach, passion for problem-solving, understanding of metrics/KPIs, willingness to challenge status-quo, IT certifications a plus). Actually many of those are more like qualifications/skills. But we can keep them. - Skills: ul list of technical and soft skills: strong understanding of PC hardware/software/networking, experience with Teams/Zoom, excellent communication/interpersonal/problem-solving, ability to learn new tech quickly, identify opportunities for self-service/zero-touch, improve FCR, liaison, endpoint troubleshooting, configure/deploy imaged endpoints, streamline legacy processes/scripts, vendor liaison, oversee onboarding/termination, document procedures, partner with cross-functional teams for major incidents, weekend on-call (maybe schedule). But some of these are responsibilities. Might be overlapping. Better to follow the posting's sections: Key Responsibilities (list), Key Experience And Education Requirements (list). Then we can add Benefits, Pay, Schedule. Thus we can have:
About the role
... description ...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
but benefits are list)
Pay
...
Schedule
...
We should not include Qualifications if we already have Requirements covering similar. But we could still include Qualifications if we have distinct content like certifications. However we already included certifications in Requirements list. Might be okay to not have Qualifications. We must not create sections with filler. Ensure each section has real content. Now we need to strip boilerplate: EEO statements, accommodation request, legal, etc. Also remove duplicated lines like "Maintain clear communication..." duplicate. Also remove "Everfox will consider reasonable accommodation as required by law." That's legal/EEO; remove. Remove "Our Talent Acquisition team will provide specific information regarding bonus eligibility and benefits offerings." That's maybe part of benefits but it's generic; we can keep benefits specifics: flexible PTO, 401k match, contribution to healthcare coverages. The rest is generic; we can keep but it's not boilerplate? It's still about benefits but it's generic. Might keep. Remove "Don’t meet every single qualification? Studies show..." that's application encouragement; remove. Remove EEO paragraph about equal employment opportunity, disability, etc. Remove. Remove "Everfox is a Federal Contractor..." etc. Remove. Now craft HTML. Let's write About the role paragraph: combine intro and location/hybrid. "Everfox delivers trusted connectivity to protect the world’s most critical environments and safeguard the sensitive data powering decision advantage. Built for mission‑critical operations, Everfox protects what matters most by securing how data moves, how users access it, and how threats are neutralized across every domain. We enable mission speed and secure collaboration across networks, domains, and allies, while ensuring the data powering AI and advanced analytics remains trusted and protected. We don’t just defend systems; we deliver decision dominance. Everfox is looking for a Service Desk technician to join our Global Digital Workplace Experience Team. The role will be