IT Support Specialist
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings only if present. The posting does not have explicit sections named those, but we can infer: "WHAT YOU GET TO DO:" corresponds to Responsibilities. "WHAT YOU BRING TO THE TEAM:" corresponds to Requirements/Qualifications/Skills. "About Slate" maybe About the role? Actually "About Slate" is company description, not role. Could be "About the role" maybe not. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create headings only when we have real specific content for that section. We have content for Responsibilities (WHAT YOU GET TO DO). We have content for Requirements/Qualifications/Skills (WHAT YOU BRING TO THE TEAM). We have maybe About the role? Could combine "About Slate" and "WHO WE ARE LOOKING FOR:" as About the role? But "About Slate" is company overview; maybe we can put under About the role? The instruction says 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. So we can have About the role heading with description of role and company? Probably we can put "About Slate" under About the role? But "About Slate" is about company, not role. However we could still use About the role heading to include both company description and role summary. The posting includes "WHO WE ARE LOOKING FOR:" which describes the role. So we can combine that under About the role. We also have "WORK AUTHORIZATION REQUIREMENT:" which is a minor metadata; we can fold into a short
maybe under About the role or separate? Probably we can include as a
under About the role. We have "WHY JOIN TEAM SLATE:" which includes values; could be Benefits? Not exactly benefits but culture. Could be Benefits section? The instruction says include Benefits section only if posting actually states them. It does list values like Safety First, Delight Customers etc. Those are not benefits like health insurance. Might be considered culture/benefits? Safer to not create Benefits unless explicit benefits like health, 401k etc. So we may omit Benefits. Pay and Schedule not present, omit. Thus sections: About the role, Responsibilities, Requirements (or Qualifications/Skills). We could split Requirements into Requirements and Skills? But we have both experience/education and technical proficiency. Could make Requirements for experience/education, Skills for technical proficiency. However instruction: prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section covering both. Thus we will output:
About the role
About Slate: ...
WHO WE ARE LOOKING FOR: ...
WORK AUTHORIZATION REQUIREMENT: ...
ThenResponsibilities
- ... each duty
Requirements
- ... each requirement/skill
- each.
We should not include headings like "Experience & Education Requirements:" as separate headings; just list items.
Now we must not include the "WHY JOIN TEAM SLATE:" content (values) as it's not benefits/pay/schedule; we can drop.
Also remove EEO etc.
Now produce HTML fragment.
Make sure to use
for each section heading. Thus:
About the role
About Slate At Slate, we’re building safe, reliable vehicles that people can afford, personalize and love—and doing it here in the USA as part of our commitment to reindustrialization. The spirit of DIY and customization runs throughout every element of a Slate, because people should have control over how their trucks look, feel, and represent them.
Slate seeks an energetic, organized, customer friendly, and experienced IT professional focused on user support, hardware and software maintenance position in Warsaw, IN. The ideal candidate will provide comprehensive desktop, mobile, and user support across our Warsaw, IN facility, and remote users. You should ensure system reliability, security, and compliance while delivering exceptional customer service. Proficiency in O365 administration, Azure AD, and user ID management, along with a commitment to ITIL best practices, is essential. IT Support Specialist reports to the IT Services Manager.
Applicants must be authorized to work in the United States on a permanent basis. We are unable to offer visa sponsorship at this time.
Responsibilities
- User Support: Provide technical support in Jira Service Desk for hardware and software issues, troubleshooting desktops, laptops, printers, and peripherals.
- Hardware Maintenance: Install, configure, and maintain computer hardware components such as CPUs, RAM, hard drives, and network interface cards (NICs).
- Asset Management: Maintain an accurate inventory of IT assets, including hardware and software.
- Software Installation and Configuration: Install, upgrade, and configure operating systems, software applications, and device drivers.
- Network Troubleshooting: Identify and resolve basic network connectivity issues, including LAN cables, switches, and routers.
- Remote Assistance: Provide remote support via remote desktop tools, phone, or email.
- Documentation: Create and update documentation, user manuals, and knowledge base articles.
- Troubleshooting and Diagnosis: Diagnose hardware and software problems using diagnostic tools and problem-solving techniques.
- Routine Maintenance: Perform system updates, patches, and backups to ensure reliability and security.
- Process Improvement: Focuses on optimizing processes, implementing new technologies, and ensuring that the team follows best practices.
- Compliance: Ensure compliance with IT policies and standards.
- Collaboration: Work with second level support teams or network administrators for complex technical issues.
Requirements
- Bachelor’s degree preferred; equivalent combination of education and relevant work experience will be considered.
- 2+ years as a Helpdesk, Desktop Support, or Systems Admin role in a corporate service desk environment.
- 1+ years as a Microsoft Administrator in an O365 cloud environment.
- Expert familiarity with ticketing systems and remote support tools