Incident Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: "A Day in the Life" (maybe About the role), "What You'll Be Doing" (Responsibilities), "Your Areas of Knowledge and Expertise" (Requirements/Qualifications/Skills), "Why You'll Love Working Here" (Benefits), "Compensation Range" (Pay), maybe "Physical Requirements" (Schedule? Not schedule). There's no explicit schedule info besides "Candidates must be able to work in-office as part of the role’s regular schedule." That's schedule info: onsite, in-office. Could include Schedule section with that detail. Also location: Los Angeles, CA onsite. Could include in About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content. So we need sections: About the role (maybe from "A Day in the Life" and "Lendistry: Who We Are"? Actually "A Day in the Life" describes role. Could be About the role. Also "Lendistry: Who We Are" is company description, maybe not needed but could be part of About the role? The instruction: do NOT repeat the job title as a heading. We can include About the role with description of role and company? Probably include role description from "A Day in the Life". Also maybe include "Lendistry: Who We Are" as part of About the role? Might be okay but not required. We'll include About the role with the paragraph(s) from "A Day in the Life" and maybe also "Lendistry: Who We Are"? But we need to preserve all substantive information. So we need to include company description too. Could be part of About the role or separate? There's no heading for company overview. Could embed within About the role. Responsibilities: from "What You'll Be Doing" bullet points (actually paragraphs with bold headings). We'll need to extract list items. The content includes sections: Incident Command & Crisis Leadership, Physical Security Operations, Cross-Functional Collaboration, Compliance Management, KPIs & Metrics, Documentation. Each has multiple sentences. We can turn each bullet into

. Could group under

. Requirements/Qualifications/Skills: from "Your Areas of Knowledge and Expertise". That's a list of requirements. We'll output as
• ... each line. Benefits: from "Why You'll Love Working Here:" list of benefits. We'll output as
  . Pay: from "Compensation Range". Provide as

  maybe? But instruction: use

  for prose. For Pay section we could have heading

  Pay

  then

  US base salary range ...

  . That's fine. Schedule: we have info: "This position is based onsite at our Los Angeles, CA location. Candidates must be able to work in-office as part of the role’s regular schedule." So schedule: onsite, in-office, Los Angeles. We'll output

  Schedule

  Onsite, in‑office role based in Los Angeles, CA.

  We must remove boilerplate: EEO statements, legal, accommodation, recruiter policy, etc. Also remove "ACKNOWLEDGEMENT B.S.D. Capital..." etc. Also remove "Physical Requirements" maybe? It's substantive but not a heading we have; could be part of Schedule? But it's about physical requirements, not schedule. There's no heading for Physical Requirements in allowed list; we could omit because not in allowed headings? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive. Could we add Physical Requirements? Probably better to stick to allowed headings. But we need to preserve ALL substantive information. If we omit Physical Requirements, we lose info. However we could incorporate physical requirements into Schedule or About the role? Might be okay to add a section for Physical Requirements even if not listed; but instruction says use those as examples, not exclusive. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings if needed. But better to keep within those categories. Physical requirements could be part of Schedule? Not really. Could be part of About the role? Might be okay to add a section "Physical Requirements". I'd include it to preserve info. The instruction: "include a section ONLY when the posting has real, specific content for it". So we can add Physical Requirements heading. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule, Physical Requirements. We need to avoid duplicating lines. Also remove duplicated lines like "Lendistry is an Equal Opportunity/Affirmative Action Employer." etc. Now craft HTML. We'll start with

  About the role

  ... combine A Day in the Life paragraph and Lendistry: Who We Are paragraph maybe two paragraphs. Let's extract: "A Day in the Life The Incident Manager leads the organization’s security and operational incident response function while supporting the GRC program that keeps the company audit-ready. This role owns incident command from detection through resolution, directs cross-functional response across Security, Engineering, IT, Legal, Compliance, Communications, Facilities, HR, and Executive Leadership, and translates each incident into measurable improvement through KPIs, after-action documentation, and updated controls. The role also supports ongoing compliance obligations (SOC 2, GLBA Safeguards Rule, ISO/IEC 27001) so that incident response and compliance posture reinforce each other rather than operating as separate functions." "Lendistry: Who We Are We’re proud to be the nation’s largest minority-led, tech-savvy lender for small businesses and commercial real estate. As a certified Community Development Financial Institution (CDFI) and Community Development Entity (CDE), our mission is all about creating economic opportunities and fueling growth for small business owners and their communities. Join us as we pave the way with innovative financing and financial education!" Combine into one or two paragraphs. We'll do two

  . Responsibilities: list items from each subheading. We'll extract bullet points: Incident Command & Crisis Leadership: - Serve as Incident Manager for security and operational incidents, holding full command and control over response activities. - Build, execute, and maintain Incident Action Plans (IAPs) that give each response a clear structure, owner, and timeline. - Make time-sensitive decisions under pressure, weighing safety, regulatory exposure, and business continuity. - Lead post-incident reviews and drive corrective actions through to closure. - Run tabletop exercises and simulations to pressure-test playbooks and team readiness. Physical Security Operations: - Manage physical security incidents, including unauthorized access, safety threats, and facility disruptions. - Coordinate with Facilities, HR, Legal, and local authorities as needed during physical security events. - Ensure physical security controls align with cybersecurity, business continuity, and compliance programs. Cross-Functional Collaboration: - Act as the central point of coordination between technical responders and non-technical stakeholders during an incident. - Direct and coordinate Security Operations, Engineering, IT, Legal, Compliance, Communications, and Executive Leadership throughout the incident lifecycle. - Engage external parties — law enforcement, emergency services, regulators, and vendors — when an incident requires it. - Partner with Security, Engineering, and Compliance to keep response playbooks and escalation paths current. Compliance Management: - Support the SOC 2 compliance program (Type I and Type II) — assisting with control ownership, evidence collection, auditor coordination, and remediation tracking. - Support alignment with ISO/IEC 27001, including risk assessments, Statement of Applicability support, and control mapping. - Support GLBA Safeguards Rule obligations, including related vendor oversight and risk documentation. - Conduct periodic risk assessments and control-effectiveness reviews across people, process, and technology. - Support regulator, auditor, and customer due-diligence requests. KPIs & Metrics: - Define and track incident response metrics (e.g., time to detect, time to contain, time to resolve, recurrence rate) to measure program maturity. - Develop compliance KPIs (control exceptions, remediation aging, audit findings closure rate) for leadership reporting. - Use trend data from incidents and audits to prioritize control investment and process changes. - Report metrics and program status to Executive Leadership on a recurring cadence. Documentation: - Maintain incident response plans, IAP templates, and after-action reports. - Maintain GRC documentation — policies, standards, procedures, and the risk register — under a continuous-compliance model. - Document control evidence, audit responses, and remediation records to support SOC 2, ISO 27001, and GLBA audits. - Keep playbooks, escalation matrices, and contact trees current and accessible. We'll put each as

  • under a single
    or multiple? Probably one
    with all items. Requirements: from "Your Areas of Knowledge and Expertise": - 3–5 years of experience in incident response, GRC, or risk management, preferably in a regulated environment such as fintech or financial services. - Direct experience serving as Incident Commander or in a comparable incident leadership role, including running IAPs and post-incident reviews. - Familiarity with SOC 2 and GLBA Safeguards Rule compliance programs; working knowledge of ISO/IEC 27001. - Experience building and tracking KPIs/metrics for incident response and compliance programs. - Strong written documentation skills; comfortable producing audit-ready records under time pressure. - Professional certifications such as ICS-100/200 preferred. - Bachelor’s degree in Computer Science, Information Security, or related field, or equivalent experience/certifications. We'll output as
    • ... each. Benefits: from "Why You'll Love Working Here:" list: - Comprehensive Medical, Dental, and Vision Insurance - Generous Paid Time Off - Birthday Day Off - 12 Paid Company Holidays - 401(k) Match - FSA and HSA - Paid Life Insurance - Paid Disability Insurance - Pet Insurance - Employee Assistance Program (EAP) - Professional Development Courses - In Office Provided Snacks and Drinks - Gym Facilities (LA & Tustin/CEC Offices) - In Office Engagement Activities We'll output as
      . Pay: from "Compensation Range": The US base salary range for this full-time position is $118,300-$136,300 annually. Our salary ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum base salary for new hires for the position across all US locations. Within the range, individual pay is determined by multiple factors like job-related skills, experience, and state of residence. Your recruiter can share more about the specific salary range during the interview process. Please note that the compensation details listed in US role postings reflect the base salary only, and do not include any variable compensation elements. We'll put in

      . Schedule: from earlier: "This position is based onsite at our Los Angeles, CA location. Candidates must be able to work in-office as part of the role’s regular schedule." We'll output

      Onsite, in‑office role based in Los Angeles, CA.

      Physical Requirements: from "Physical Requirements This is a stationary position that requires frequent sitting (approximately 95%), repetitive wrist motions, grasping, speaking, listening, close vision, and the ability to adjust focus. It also may require occasional standing, lifting, carrying of 20lbs or less, walking, kneeling, bending/stooping, twisting, pulling/pushing, and reaching above the shoulder. Employees in this position must be physically able to efficiently perform the essential functions of the position." We'll