IT Support Specialist

We need to output HTML fragment with sections: responsibilities, knowledge/experience/requirements, success criteria, compensation, benefits, about novara? The instruction: Use

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 extract content. Let's parse the posting. First paragraph: description of Novara (company overview). Could be "About Novara" or "About the role"? Actually "About Novara" appears later repeated. The first paragraph is about company. Could be "About Novara". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings; maybe we can also use "About Novara". But they gave examples; not strict list. Probably we can use "About Novara". However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have "About Novara". Also "Responsibilities", "Knowledge, Experience, Requirements" maybe "Requirements". "Success Criteria" maybe "Qualifications"? Could map to "Qualifications". "Compensation" maybe "Pay". "Benefits" maybe "Benefits". "About Novara" maybe "About the role"? Actually "About the role" is generic; but we have company description. Could use "About Novara". Let's decide. We need to preserve all substantive information. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove repeated paragraphs about Novara (they appear multiple times). We need to keep only one copy. Let's extract sections: - Company overview: "Novara provides safety, operational risk management, and sustainability software that empowers organizations to identify and resolve issues before they become incidents. Through the Flex and Risk Management Center platforms, Novara helps organizations manage operational risk proactively with a system they can configure to fit their operations, data that unifies risk and safety intelligence, and tools that increase workforce participation. Novara’s combination of software, training, and AI-powered tools put people and safety first while protecting critical operations." Later there is repeated "About Novara" paragraph similar but slightly different. We'll keep one concise version maybe combine? But we must preserve all substantive information; not invent or summarize away detail. If we combine we might lose some nuance. Better to keep the first occurrence and drop duplicates. The first occurrence includes sustainability software mention; later mentions safety and operational risk management software (no sustainability). The later also mentions "unifying data, increasing workforce engagement, and proactively managing risk." The first includes "data that unifies risk and safety intelligence, and tools that increase workforce participation." Slight differences. To preserve all substantive info, we could include both? But that would be duplicated content. The instruction says remove duplicated lines. So we should deduplicate. We need to decide which version is more comprehensive. The first includes sustainability software, configuration, data unifies risk and safety intelligence, tools increase workforce participation, combination of software, training, AI-powered tools put people and safety first while protecting critical operations. The second (About Novara) mentions: "Novara provides safety and operational risk management software that empowers organizations to identify and resolve issues before they become incidents. Through the Flex and Risk Management Center platforms, Novara helps organizations address operational risk proactively by unifying data, increasing workforce engagement, and proactively managing risk. Novara’s combination of training, software, and tools puts people and safety first while protecting critical operations." It lacks sustainability, configuration, AI-powered tools mention? It mentions training, software, tools. It also mentions launching Jan 1 2026 as spin-off etc. That's additional info. So we need to preserve all substantive info, not just one. We could combine into a paragraph that includes all unique facts: sustainability software, configurability, data unifies risk and safety intelligence, tools increase workforce participation, combination of software, training, AI-powered tools put people and safety first while protecting critical operations, also address operational risk proactively by unifying data, increasing workforce engagement, and proactively managing risk (some overlap), combination of training, software, and tools puts people and safety first while protecting critical operations (overlap), launched Jan 1 2026 as independent company spin-off of Flex and RMC software businesses formerly part of KPA. That seems to capture all unique points without duplication. However we must be careful not to invent or summarize away detail. Summarizing is okay as long as we keep all details? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing could be considered summarizing away detail if we condense multiple sentences into one. But we could keep them as separate sentences, just deduplicate repeated phrases. That is acceptable: we keep each distinct sentence, remove exact duplicates. Let's list unique sentences: From first paragraph: 1. Novara provides safety, operational risk management, and sustainability software that empowers organizations to identify and resolve issues before they become incidents. 2. Through the Flex and Risk Management Center platforms, Novara helps organizations manage operational risk proactively with a system they can configure to fit their operations, 3. data that unifies risk and safety intelligence, 4. and tools that increase workforce participation. 5. Novara’s combination of software, training, and AI-powered tools put people and safety first while protecting critical operations. From later "About Novara" paragraph: - Novara provides safety and operational risk management software that empowers organizations to identify and resolve issues before they become incidents. (duplicate of sentence 1 but missing sustainability) - Through the Flex and Risk Management Center platforms, Novara helps organizations address operational risk proactively by unifying data, increasing workforce engagement, and proactively managing risk. - Novara’s combination of training, software, and tools puts people and safety first while protecting critical operations. (similar to sentence 5 but without AI-powered) - Novara, a Providence Equity portfolio company, provides safety and operational risk management software that empowers organizations to identify and resolve issues before they become incidents. (duplicate again) - Through the Flex and Risk Management Center platforms, Novara helps organizations address operational risk proactively by unifying data, increasing workforce engagement, and proactively managing risk. (duplicate) - Novara’s combination of training, software, and tools puts people and safety first while protecting critical operations. (duplicate) - Novara launched January 1 2026, as an independent company, a spin-off of the Flex and RMC software businesses formerly part of KPA. Thus unique sentences: - Novara provides safety, operational risk management, and sustainability software that empowers organizations to identify and resolve issues before they become incidents. - Through the Flex and Risk Management Center platforms, Novara helps organizations manage operational risk proactively with a system they can configure to fit their operations, - data that unifies risk and safety intelligence, - and tools that increase workforce participation. - Novara’s combination of software, training, and AI-powered tools put people and safety first while protecting critical operations. - Through the Flex and Risk Management Center platforms, Novara helps organizations address operational risk proactively by unifying data, increasing workforce engagement, and proactively managing risk. - Novara’s combination of training, software, and tools puts people and safety first while protecting critical operations. - Novara launched January 1 2026, as an independent company, a spin-off of the Flex and RMC software businesses formerly part of KPA. - Novara, a Providence Equity portfolio company, provides safety and operational risk management software that empowers organizations to identify and resolve issues before they become incidents. (This is similar to first but missing sustainability; but it's a distinct sentence mentioning Providence Equity portfolio company. So we need to keep that as well because it adds Providence Equity portfolio company detail. So include: "Novara, a Providence Equity portfolio company, provides safety and operational risk management software that empowers organizations to identify and resolve issues before they become incidents." Thus we have several sentences; some are similar but not identical. We'll keep them. Now responsibilities: The block after "Responsibilities:" includes a long list of duties separated by semicolons and line breaks. We need to turn into

  • items. Let's parse. Responsibilities: Provide support across phone, email, chat, ticket portal, and deskside, serving as the escalation point for tickets unresolved by first-line support. Resolve incidents and service requests within established SLAs Triage, prioritize, and route tickets; keep affected users informed throughout the resolution process; perform root-cause analysis on recurring issues to drive permanent fixes Provision, image, and deploy Windows and macOS endpoints using Autopilot, Intune, and Kandji; support Android and iOS devices through MDM Manage the full account lifecycle, including onboarding and offboarding, Entra ID accounts, security groups, licenses, device provisioning, password resets, MFA resets, and SSO/SCIM administration Support Microsoft 365 (Exchange Online, SharePoint, OneDrive), including mailboxes, permissions, shared mailboxes, distribution groups, and security groups, as well as collaboration tools such as Slack and Zoom Support conference room AV equipment and Zoom Rooms Support endpoint security, including Microsoft Defender, CrowdStrike, BitLocker, FileVault, and device compliance. Triage phishing and malware alerts and participate in incident response, remediation, and vulnerability management Troubleshoot LAN, Wi-Fi, VPN connectivity, and remote/hybrid access issues Maintain hardware and software asset inventories and license entitlements throughout the device lifecycle, including procurement, deployment, refreshes, warranty repairs, RMAs, and vendor support Create and maintain knowledge base articles, runbooks, standard operating procedures (SOPs), and technical documentation. Develop and deliver end-user training and new-hire IT orientation Build and maintain automation scripts and workflows using PowerShell, Microsoft Graph API, and Power Automate to reduce manual work. Utilize AI-assisted support tools while validating recommended solutions before implementation Serve as a subject matter expert in one or more technology domains (e.g., endpoint management, identity management, macOS) and mentor other IT technicians as needed Contribute to IT initiatives, including technology rollouts, system migrations, and hardware refresh projects We need to split each line into separate
  • items. Some lines contain multiple actions separated by semicolons; but we can keep as one
  • with semicolons inside. That's fine. Now "Knowledge, Experience, Requirements:" block. Knowledge, Experience, Requirements: 4-6 years of IT support, helpdesk, or desktop experience, or a combination of education and experience Windows desktop/laptop and macOS support (advanced); CompTIA A+ and Microsoft certifications preferred Endpoint / MDM management — Intune and Kandji Identity and Microsoft 365 administration — Entra ID, Exchange Online, and Share