IT Helpdesk, Support Representative
Atlas · Lafayette, LA · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- About Atlas (company description) maybe not needed? The instruction: "use
. The instruction: Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- About Atlas (company description) maybe not needed? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should map content to these headings. "About the role" likely corresponds to Job Description overview. "Responsibilities" corresponds to Core Responsibilities. "Requirements" maybe corresponds to "You'll Thrive Here If You Have" (experience, knowledge). "Qualifications" maybe similar to Requirements? Might combine. "Skills" maybe specific skills list. "Benefits" from "What You Can Expect From Us". "Pay" and "Schedule" only if present. The posting does not mention pay or schedule specifics, only flexibility note: "Flexibility: May vary by project demands and regional workloads, but we are committed to providing reasonable accommodation..." Not specific schedule. So we should NOT include Pay or Schedule sections because no concrete info.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from each section.
We must not include boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
...
maybe.Skills
- ... ...
Benefits
- ... ...
under About the role. Responsibilities: The list under "Core Responsibilities". It's a long paragraph with many sentences separated by periods. We need to convert each duty into
- for any list of duties/requirements/benefits. So we should split each sentence into a list item. Ensure we preserve all info. Let's extract each duty: 1. Serve as the first point of contact for employees seeking technical assistance, delivering timely and professional support across multiple channels including phone, Microsoft Teams, remote support tools, ticketing systems, and in-person interactions. 2. Troubleshoot and resolve a wide range of hardware, software, account access, application, and connectivity issues to minimize business disruption and ensure a positive user experience. 3. Support and maintain Microsoft 365 applications, Outlook, Teams, OneDrive, Windows operating systems, printers, peripheral devices, and other standard business technologies. 4. Manage IT incidents and service requests from intake through resolution, ensuring accurate prioritization, thorough documentation, clear communication, and adherence to service desk processes. 5. Perform first-level diagnostics to identify root causes, resolve issues whenever possible, and escalate complex problems to Tier 2 support with complete troubleshooting details and supporting information. 6. Maintain ownership of assigned tickets, provide status updates to users, verify successful resolution, and ensure users can resume normal operations before closing requests. 7. Assist with workstation deployments, hardware installations, software configuration, user account administration, password resets, and technology rollouts across the organization. 8. Conduct basic troubleshooting related to workstation performance, network connectivity, mobile devices, printing systems, and business applications. 9. Utilize internal knowledge bases, vendor resources, and documented procedures to efficiently diagnose and resolve technical issues while maintaining consistency and quality standards. 10. Create and maintain detailed documentation of troubleshooting steps, resolutions, recurring issues, and support procedures to strengthen organizational knowledge and improve future response times. 11. Identify recurring technical trends, recommend process improvements, and collaborate with IT teams to enhance support effectiveness and the overall employee experience. 12. Partner closely with Tier 2 support staff and other IT teams on escalations, special projects, technology initiatives, training activities, and continuous improvement efforts. That seems comprehensive. Requirements: The "You'll Thrive Here If You Have" bullet list. Let's extract each line: - 1-3 years of experience in a Help Desk, Service Desk, Desktop Support, Technical Support, or similar customer-facing IT support environment. - Strong working knowledge of Windows operating systems, Microsoft 365 applications, computer hardware, and common business technologies. - Experience troubleshooting end-user issues involving software, hardware, printers, network connectivity, account access, and Microsoft Office applications. - Hands-on experience using ticketing systems to manage incidents, document resolutions, and deliver high-quality customer support. - A customer-first mindset with the ability to remain patient, professional, and empathetic when assisting users with technical challenges. - Excellent verbal and written communication skills with the ability to explain technical concepts clearly to non-technical audiences. - Strong organizational skills and the ability to prioritize multiple requests while maintaining attention to detail in a fast-paced environment. - A structured problem-solving approach, sound troubleshooting abilities, and a desire to continuously learn and expand technical knowledge. - Experience with Microsoft 365 administration, Active Directory or Entra ID, remote support tools, and endpoint support is highly valued. - Familiarity with networking fundamentals including wired, wireless, VPN, and internet connectivity concepts. - An Associate Degree in Information Technology, CompTIA A+ certification, or equivalent technical training is preferred. - A collaborative team-oriented attitude with a willingness to share knowledge, contribute to process improvements, and support broader IT initiatives. We'll put each as
- under Requirements.
Qualifications: Might be overlapping with Requirements; but we could treat "Qualifications" as the education/certification preference. However we already included that in Requirements. To avoid duplication, maybe we put Qualifications as the education/certification line. But we must not repeat info. The instruction: "Prefer a few substantive sections over many thin ones." Could combine Requirements and Qualifications? But they ask to use headings for those sections if content exists. We have content for both; we could split: Requirements = experience and knowledge; Qualifications = education/certification. Let's do that.
Thus:
Requirements: experience and knowledge items (first 8 maybe). Qualifications: education/certification and maybe the collaborative attitude? Actually collaborative attitude is more skill. Let's decide:
Requirements (experience & knowledge):
- 1-3 years of experience in a Help Desk, Service Desk, Desktop Support, Technical Support, or similar customer-facing IT support environment.
- Strong working knowledge of Windows operating systems, Microsoft 365 applications, computer hardware, and common business technologies.
- Experience troubleshooting end-user issues involving software, hardware, printers, network connectivity, account access, and Microsoft Office applications.
- Hands-on experience using ticketing systems to manage incidents, document resolutions, and deliver high-quality customer support.
- A customer-first mindset with the ability to remain patient, professional, and empathetic when assisting users with technical challenges.
- Excellent verbal and written communication skills with the ability to explain technical concepts clearly to non-technical audiences.
- Strong organizational skills and the ability to prioritize multiple requests while maintaining attention to detail in a fast-paced environment.
- A structured problem-solving approach, sound troubleshooting abilities, and a desire to continuously learn and expand technical knowledge.
Qualifications (education/certification):
- Experience with Microsoft 365 administration, Active Directory or Entra ID, remote support tools, and endpoint support is highly valued.
- Familiarity with networking fundamentals including wired, wireless, VPN, and internet connectivity concepts.
- An Associate Degree in Information Technology, CompTIA A+ certification, or equivalent technical training is preferred.
- A collaborative team-oriented attitude with a willingness to share knowledge, contribute to process improvements, and support broader IT initiatives.
But some of those are more skills. However we have a separate Skills section. Could move those to Skills.
Skills: maybe list technical skills: Microsoft 365 administration, Active Directory/Entra ID, remote support tools, endpoint support, networking fundamentals, etc. Also collaborative attitude.
Let's define:
Skills:
- Microsoft 365 administration
- Active Directory or Entra ID
- Remote support tools
- Endpoint support
- Networking fundamentals (wired, wireless, VPN, internet connectivity)
- Collaborative team-oriented attitude, willingness to share knowledge, contribute to process improvements, support broader IT initiatives
But we need to preserve all substantive information; we can't lose any. So we need to include all items from the "You'll Thrive Here If You Have" list somewhere. We'll allocate them across Requirements, Qualifications, Skills as appropriate, ensuring no duplication.
Better approach: Keep Requirements as the list of experience/knowledge/skills (all items). Then Qualifications could be empty? But we must not create a heading with filler. So we should only include Qualifications if there is specific content distinct from Requirements. The posting does not have a separate "Qualifications" heading; it's all under "You'll Thrive Here If You Have". So we could treat that as Requirements (or Skills). The instruction says use headings for those sections if content exists. We can decide to put all that content under Requirements, and omit Qualifications and Skills if they'd be thin. However we have also Benefits section.
But we also have a list of skills like "Experience with Microsoft 365 administration, Active Directory or Entra ID, remote support tools, and endpoint support is highly valued." That's still a skill/experience. Could be part of Requirements.
Thus we could have:
- About the role
- Responsibilities
- Requirements (includes all experience, knowledge, skills, education, certifications, attitudes)
- Benefits
No Qualifications or Skills separate to avoid thin sections. That seems acceptable: "Prefer a few substantive sections over many thin ones." So we combine.
Thus we will output:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...