Senior Incident Response Analyst

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for any list of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Position Details: Senior Incident Response Analyst - Overview: Rutgers description (boilerplate about university) - Posting Summary: Key duties listed - FLSA Exempt Grade 07 - Salary Details: Minimum, Mid Range, Maximum - Offer Information: salary determination factors - Benefits: comprehensive benefits package listed - Position Status: Full Time - Working Hours: Standard Hours 37.50 - Work Arrangement: hybrid eligible per policy - Union Description: Admin Assembly (MPSC) - Payroll Designation: PeopleSoft Seniority Unit - Terms of Appointment: Staff - 12 month - Pension Eligibility: ABP - Qualifications: Minimum Education and Experience, Required Certifications/Licenses, Required Knowledge, Skills, and Abilities, Preferred Qualifications - Equipment Utilized: list - Physical Demands and Work Environment: lift up to 50 pounds - Special Conditions: Posting Details (Posting Number, Posting Open Date), Special Instructions to Applicants, Regional Campus, Home Location Campus, City, State, Location Details, Pre-employment Screenings, Immunization Requirements, Equal Employment Opportunity Statement, Supplemental Questions, Applicant Documents I need to structure this into meaningful sections. The rules say to use specific heading names like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". I should map the content accordingly. Let me plan sections: 1. About the role (or Overview) - could include the posting summary description 2. Responsibilities - the key duties listed in Posting Summary 3. Requirements / Qualifications - minimum education/experience, required knowledge/skills/abilities 4. Preferred Qualifications - preferred qualifications 5. Skills - maybe combine with required knowledge/skills/abilities? But the rules mention Skills as a heading. Could have a Skills section for the required knowledge/skills/abilities. 6. Benefits - the benefits listed 7. Pay - salary details 8. Schedule - working hours, work arrangement 9. Additional Information - maybe for equipment, physical demands, union, etc. But the rules say: "include a section ONLY when the posting has real, specific content for it". So I should only include sections that have substantive content. Also, "Do NOT repeat the job title as a heading". So no

  Senior Incident Response Analyst

  . "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So Posting Number, Posting Open Date, etc. can be in a paragraph or dropped. Remove boilerplate: Equal Employment Opportunity Statement, Immunization Requirements, Pre-employment Screenings, Supplemental Questions, Applicant Documents, Special Instructions to Applicants, etc. are boilerplate. Also remove duplicated lines. Now, let's extract substantive content: - Overview: Rutgers description (maybe keep as a paragraph under About the role) - Posting Summary: key duties (list) - Salary Details: min, mid, max (pay section) - Offer Information: salary factors (pay section) - Benefits: list of benefits (benefits section) - Position Status: Full Time (schedule) - Working Hours: 37.50 hours (schedule) - Work Arrangement: hybrid eligible (schedule) - Union Description, Payroll Designation, Terms of Appointment, Pension Eligibility: maybe fold into a paragraph under Additional Information or drop? They are specific to the position. Could include in a "Position Details" section. - Qualifications: Minimum Education and Experience, Required Certifications/Licenses (none listed? It says "Required Certifications/Licenses" but then lists "Required Knowledge, Skills, and Abilities". Actually the posting has "Required Certifications/Licenses" heading but no list? It says "Required Certifications/Licenses" then "Required Knowledge, Skills, and Abilities". Might be a heading with no content. I'll include the required knowledge/skills/abilities as requirements. - Preferred Qualifications: list - Equipment Utilized: list - Physical Demands: lift 50 pounds I'll create sections: - About the role: overview paragraph + posting summary intro - Responsibilities: bullet list of key duties - Requirements: minimum education/experience, required knowledge/skills/abilities - Preferred Qualifications: bullet list - Skills: maybe the required knowledge/skills/abilities are skills? But the rules have separate "Skills" heading. Could combine with Requirements. However, the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So they expect possibly separate Skills section. But the posting doesn't have a distinct "Skills" section; it has "Required Knowledge, Skills, and Abilities". I'll treat that as Requirements or Skills. I'll make a "Requirements" section for minimum education/experience and required knowledge/skills/abilities. And a "Preferred Qualifications" section for preferred. - Benefits: bullet list - Pay: salary details and offer information - Schedule: working hours, work arrangement, position status - Additional Details: equipment, physical demands, union, pension, etc. But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine some. Let's decide on sections: 1. About the role (overview) 2. Responsibilities 3. Requirements (minimum education/experience, required knowledge/skills/abilities) 4. Preferred Qualifications 5. Benefits 6. Pay 7. Schedule 8. Additional Information (equipment, physical demands, union, pension, etc.) But "Additional Information" might be too generic. Could include equipment and physical demands under "Requirements" or separate. The rules don't have an "Equipment" heading. I'll include equipment and physical demands in a "Work Environment" or "Additional Details" section. However, the rules say only use headings like those listed. But they say "e.g." so not exhaustive. But they say "include a section ONLY when the posting has real, specific content for it". So I can create a heading like "Equipment & Environment" if needed. But to stay close to the example headings, maybe "Qualifications" covers requirements, "Skills" covers knowledge/skills/abilities. But the example includes "Qualifications" and "Skills" as separate. I'll do: - About the role - Responsibilities - Qualifications (minimum education/experience) - Skills (required knowledge, skills, abilities) - Preferred Qualifications - Benefits - Pay - Schedule - Additional Details (equipment, physical demands, union, pension, etc.) But "Qualifications" and "Skills" might be overlapping. The posting has "Minimum Education and Experience" and "Required Knowledge, Skills, and Abilities". I'll combine into "Qualifications" with two sub-lists? But the rules say use

  • for lists. I can have a paragraph for minimum education, then a list for required knowledge/skills/abilities. Better to follow the example headings: "Requirements" and "Skills". The example includes both. I'll use "Requirements" for minimum education/experience, and "Skills" for required knowledge/skills/abilities. Then "Preferred Qualifications" for preferred. Let's structure:

    About the role

    Rutgers, The State University of New Jersey, is a leading national research university...

    This position reports to the Associate Director and performs daily operations of the incident detection and response program...

    But the posting summary already lists key duties. I'll put the overview paragraph, then maybe a sentence about the role.

    Responsibilities

    • Performs daily operations of the incident detection and response program, which includes finding evidence of threats or suspicious behavior and leveraging data to improve controls and processes.
    • Monitors information security incidents throughout Rutgers’ computing environment.
    • Serves as an escalation point for Incident Response Analysts.
    • Provides expert-level analytic, investigative and forensic support of complex security incidents to detect and remediate security threats on networks, workstations, servers, and other connected devices.
    • Provides expert level advice and services to business units throughout the University while participating in all phases of Rutgers’ Integrated Incident Response Program (Prepare, Detect & Analyze, Contain, Eradicate, Recovery, Report, Remediate).

    Requirements

    Bachelor’s degree or equivalent education and experience plus five years relevant experience in specialty area.

    5+ years of information security experience; vulnerability scanning, penetration testing and/or security operations.

    5+ years of experience working in an enterprise technical environment, preferably in a customer-service based organization.

    Skills

    • Knowledge in a wide array of cybersecurity tools and their capabilities as they pertain to the detection and mitigation of Cyber Threats (SIEM, EDR, NGFW, DLP, IPS/IDS, etc.)
    • Knowledge of industry standard cybersecurity frameworks (Mitre ATT&CK, NIST Incident Response, etc.)
    • Understanding of complex enterprise networks to include routing, switching, firewalls and common networking protocols (HTTP, DNS, SMB, etc.)
    • Experience with Regex and at least one common scripting language (PERL, Python, PowerShell)
    • Experience with an enterprise SIEM platform
    • Excellent verbal and written communication skills
    • Ability to communicate technical problems succinctly and accurately
    • Ability to handle multiple, shifting priorities and a large volume of technical problem resolution
    • Ability to apply and document new technical knowledge and procedures
    • Ability to work well with peers and junior staff in a team oriented, cooperative spirit

    Preferred Qualifications

    • Degree in a related field such as Information Security.
    • 3+ years of experience in incident response, threat hunting, SOC operations, digital forensics, or detection engineering.
    • Relevant certifications such as GCFA, GCIH (or other SANS certifications), CISSP, CySA+
    • Experience as a key member of a cybersecurity team (SOC, Incident Response, Threat Intel, Malware Analysis, Live Forensics, IDS/IPS Analysis)
    • Experience investigating identity-centric attacks, cloud compromise, phishing, business email compromise, and SaaS-based incidents.
    • Knowledge of TTPs related to cyber-crime, malware, botnets, social engineering, APTs and other threats.