Security Analyst I (Monday-Thursday, 12AM -11AM CST)

We need to output HTML fragment with sections: About the role? Actually the posting includes intro paragraph about company, then "How You'll Make An Impact", then "Location and Work Expectations", then "What You Will Be Doing", then "You’ll be successful in this role if you have..." (requirements/qualifications), then "Bonus points for Security + Certification", then "Benefits And Perks", then base pay range, etc. Also schedule info. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We need to map content to these headings. We have: - About the role: Could be the intro paragraph describing company and role? The posting starts with "Are you looking for limitless career opportunities..." That's more like company overview. Could be "About the role" or maybe "About the company". We'll use "About the role" heading and put that intro paragraph. - Responsibilities: The "What You Will Be Doing" list of duties. Use

• . - Requirements: The "You’ll be successful in this role if you have ..." includes experience, certifications, etc. Could be Requirements. - Qualifications: Might overlap; but we can separate: maybe "Qualifications" for certifications and specific hands-on exposure. However we need to avoid thin sections. Could combine Requirements and Qualifications? But instructions: use headings for those categories if content exists. We have content for both. - Skills: maybe the "Bonus points for Security + Certification" is more like preferred qualifications/skills. Could be Skills. - Benefits: "Benefits And Perks" list. - Pay: base pay range. - Schedule: schedule description. We must not include headings with filler like "commensurate with experience". We have actual content. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove the EEO statement, "Our Commitment to a Diverse Workforce", "Application Deadline", etc. Also remove "FLSA Status", "Work Authorization Criteria", "Workspace Requirements And Remote Work Policy". Those are likely boilerplate/legal; we should remove them. Also remove "Required Language Skills" maybe? That's substantive? It's about language ability; could be considered a requirement. Might keep as part of Requirements or Qualifications. But we need to preserve ALL substantive information; we can't discard required language skills. So we need to incorporate that info somewhere, maybe under Requirements or Qualifications. We also need to remove duplicated lines. There's some duplication? Not obvious. We need to output only HTML fragment, no /, no markdown fences. Let's extract sections: Intro paragraph (About the role): "Are you looking for limitless career opportunities with a company that values growth, innovation, and teamwork? At Ntiva, we’re more than a Managed Services Provider, we’re a community dedicated to helping each other, our clients, and their businesses thrive both personally and professionally. Ntiva is a culture of people who are passionate about the work…and each other. Our clients view us as an essential part of their teams, relying on us for strategic guidance, fast solutions to complex challenges, and proactive support. With strategic locations across the U.S. and leadership from our founder, Steven Freidkin, we’re on the front lines of a fast-paced industry, facing cybersecurity threats and rapid technology changes together. If you thrive in a dynamic, supportive environment and enjoy going above and beyond, we’d love to meet you. Come explore one of our many opportunities and grow with us!" That's substantive. Next heading: "How You’ll Make An Impact As a Security Analyst I, you'll be our first line of defense against cyber threats. You'll swiftly respond to security alerts, investigate potential malicious activity, secure compromised accounts, and review change activity to prevent or minimize security events. By managing routine security tool adjustments and escalating complex issues, you'll ensure our defenses remain effective and responsive, safeguarding our client's assets and data." That could be part of About the role or Responsibilities? It's more like role impact. Could be included under About the role or maybe a separate section "Role Overview". But we only have allowed headings; we could put this under About the role as well, but we already have intro. Could combine. But we have a separate "Location and Work Expectations" section: "This is a remote position; however, team members should be willing and able to travel if the need arises, though such travel is expected to be infrequent. Candidates with proximity to one of our Centers of Excellence are preferred (Lombard, IL; McLean, VA; Shreveport, LA; Overland Park, KS). Schedule: 4 days on, 3 days off! Monday-Thursday, 12am–11am CST (following a required training period on day shift, M–F 8am–5pm CST — duration varies by individual progress)This role also includes participation in a rotating on-call schedule." We need to separate Schedule and Location maybe. The schedule is within that paragraph. We'll extract schedule details for Schedule section. Location details for maybe "Location" but we don't have a heading for Location; we have only the allowed headings. Could put location info under About the role or Responsibilities? Not ideal. But we could include location info under "About the role" as part of description. However schedule must be its own section if we have specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine location and schedule into one section? But we have separate headings for Schedule and maybe we could put location under About the role. Let's see. We have "What You Will Be Doing" list of duties: that's Responsibilities. We have "You’ll be successful in this role if you have 1-2 years of experience in Cybersecurity 3-5 years in an IT role including log analysis, account/access management, or endpoint troubleshooting This is a full-time role requiring your full alertness and reliable attendance during scheduled hours. Additional outside employment, regardless of hours, is not permitted CySA+, GCIH, or SC-200 (or actively pursuing) Hands-on exposure to at least one EDR/SIEM platform (e.g., SentinelOne, CrowdStrike, Microsoft Defender, Microsoft Sentinel) Direct hands-on experience using ConnectWise Manage for ticket documentation, with a demonstrated track record of clear, timestamped, audit-ready incident notes Must have practical familiarity with at least one of: SIEM log correlation, Windows Event Viewer (Security log IDs like 4624/4625/4648), or a ticketing-based alert queue Sharp attention to detail with a proactive approach to accuracy and thoroughness Passion for delivering outstanding customer service, with a track record of exceeding client expectations Strong enthusiasm for learning new things and ability to adapt to evolving technology trends and industry advancements This role involves extended periods of sitting or standing and regular use of computers and office equipment Required Language Skills Ability to communicate professionally, in English, both written and orally Ability to write business correspondence and process procedures Ability to effectively present information and respond to questions from groups of managers, clients, and the general public" That's a mix of requirements, qualifications, skills, language skills. We'll need to split into Requirements, Qualifications, Skills perhaps. We have "Bonus points for Security + Certification" line: that's a bonus. We have "Benefits And Perks" list. We have base pay range. We have schedule details. We need to avoid boilerplate: remove EEO, FLSA, Work Authorization, Workspace Requirements, etc. Now craft HTML. We'll produce sections:

  About the role

  Intro paragraph + How You’ll Make An Impact maybe.

  Location and Work Expectations

  but we don't have that heading in allowed list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot use Location and Work Expectations. We need to fit location info somewhere else, maybe under About the role or Schedule. Since schedule is separate, we could put location info under About the role as part of description. That seems okay. Thus About the role will include company overview, role impact, location preferences. Then Responsibilities: the bullet list of duties. Then Requirements: maybe the experience, full-time, no outside employment, language skills. Then Qualifications: certifications (CySA+, GCIH, SC-200), hands-on exposure to EDR/SIEM, ConnectWise Manage experience, practical familiarity with SIEM log correlation etc. Then Skills: maybe attention to detail, customer service, learning enthusiasm, etc. Could also include bonus points for Security+ certification. But we need to avoid thin sections. Let's see if we can combine some. We could have: - About the role - Responsibilities - Requirements & Qualifications (combined) - Benefits - Pay - Schedule But the instruction says use those headings if content exists. It doesn't forbid combining, but we must use those headings for sections we emit. If we combine Requirements and Qualifications under one heading, we need to pick one heading; maybe "Requirements". But then we lose Qualifications heading. However we could still include qualifications content under Requirements heading; that's okay as long as we don't emit a Qualifications heading with empty content. So we can emit only the headings we have content for. Thus we could emit: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Skills if we have distinct content not covered elsewhere. But we have language skills, attention to detail, customer service, learning enthusiasm - these could be considered Skills. Could put them under Requirements or Skills. Let's decide to put them under Skills to have a Skills section. Thus sections: - About the role (intro + impact + location) - Responsibilities (duties list) - Requirements (experience, full-time, no outside employment) - Skills (language skills, attention to detail, customer service, learning enthusiasm, bonus Security+) - Benefits (list) - Pay (base pay range) - Schedule (schedule description) We need to ensure we don't emit any heading with filler. Now extract precise content. About the role content: Combine intro paragraph and "How You’ll Make An Impact" and location preferences. Intro paragraph: "Are you looking for limitless career opportunities with a company that values growth, innovation, and teamwork? At Ntiva, we’re more than a Managed Services Provider, we’re a community dedicated to helping each other, our clients, and their businesses thrive both personally and professionally. Ntiva is a culture of people who are passionate about the work…and each other. Our clients view us as an essential part of their teams, relying on us for strategic guidance, fast solutions to complex challenges, and proactive support. With strategic locations across the U.S. and leadership from our founder, Steven Freidkin, we’re on the front lines of a fast-paced industry, facing cybersecurity threats and rapid technology changes together. If you thrive in a dynamic, supportive environment and enjoy going above and beyond, we’d love to meet you. Come explore one of our many opportunities and grow with us!" Impact paragraph: "How You’ll Make An Impact As a Security Analyst I, you'll be our first line of defense against cyber threats. You'll swiftly respond to security alerts, investigate potential malicious activity, secure compromised accounts, and review change activity to prevent or minimize security events. By managing routine security tool adjustments and escalating complex issues, you'll ensure our defenses remain effective and responsive, safeguarding our client's assets and data." Location preferences: "This is a remote position; however, team members should be willing and able to travel if the need arises, though such travel is expected to be infrequent. Candidates with proximity to one of our Centers of Excellence are preferred (Lombard, IL; McLean, VA; Shreveport, LA; Overland Park, KS)." We could