DirectJobHub
Jobs · Information Technology · Washington

Security Incident Response Engineer

Twitch · Seattle, WA · 1 mo ago
Information Technology$159k–$202k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, "About Us" is boilerplate? It's about Twitch, but it's not about the role. The instruction: "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." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." We need to keep substantive info: About The Role, You Will (responsibilities), You Have (requirements/qualifications/skills), Bonus Points (maybe skills/qualifications), Perks (benefits), Salary range (pay), location maybe schedule? No schedule given. So we may not include Schedule section. We need to decide headings: About the role (we have "About The Role" heading). Responsibilities: from "You Will:" list. Requirements/Qualifications/Skills: from "You Have:" list and Bonus Points. Benefits: from "Perks" list. Pay: from salary ranges. Possibly also location info could be in a short paragraph. We must not include sections with filler like "commensurate with experience". We have actual salary ranges. We need to preserve all substantive info; do not invent or summarize away detail. So we need to list each bullet exactly as in posting? Probably we can keep the phrasing but as list items. We need to output only HTML fragment, no /, no markdown fences. Let's extract. About The Role paragraph: "Twitch is looking for a Security Incident Response Engineer to join our SIRT. Reporting to the SIRT Manager, you'll be at the heart of our mission to find, handle, and learn from security incidents across our global platform. We're looking for engineers who thrive coordinating response to emerging issues in information security who are ready to level up our defense. If you're passionate about protecting the Twitch community and solving complex security puzzles, we want to hear from you! You can work from San Francisco, CA; Irvine, CA; or Seattle, WA." We'll put that in

under

About the role

. Responsibilities: list after "You Will:" includes multiple items each starting with a verb. We'll capture each as
  • . Let's list them exactly: - Participate in an on-call rotation that includes your peers on the Security Incident Response Team - Qualify reports or alerts of activity as security incidents using clear guidelines that establish what a security incident is - Evaluate the potential and realized impact of security incidents to Twitch - Analyze threat actor tactics, techniques, and procedures - Participate or create information sharing groups; communicate securely and responsibly - Write and follow clear procedures so that our work can be accountable, repeated, measured, and improved - Communicate with peers and leadership about timeline of a security related event with what potential and realized impact, how we discovered it, and how we're handling it - Coordinate security incident response activities with affected teams to do the right thing for our customers and our organization - Investigate, document, and implement agentic detection, enrichment, triage, response, and communication automations in every day processes - Lead lessons learned discussions and help teams effect change across the business that reduces incident recurrence We'll keep as is. Now "You Have:" list: - 3+ years relevant experience doing information security work or equivalent BS degree in Information Security, Information Systems, Computer Science, Computer Engineering, or other related fields - Automation experience using scripting or programming languages (Go, Python, Ruby, Shell, or Perl) - Ability to securely design and implement AI/ML-driven playbooks to automate common security operations - Experience coordinating responses to security incidents - Knowledge of security issues and threat landscape - Background in cloud, host, network, and application security - Familiarity with common Incident Response frameworks or lifecycle models like NIST-800-61, ISO/IEC 27035, etc. Now "Bonus Points": - B.S. or M.S. in Computer Science, Computer Engineering, Software Security, or a related technical discipline - Experience and familiarity with streaming and content creation - Experience handling security incidents in hybrid cloud environment (AWS, GCP) and conducting log dives on cloud telemetry like CloudTrail - Passion and excitement for Twitch Now "Perks": - Medical, Dental, Vision & Disability Insurance - 401(k) - Maternity & Parental Leave - Flexible PTO - Amazon Employee Discount Also later there is a paragraph about Amazon benefits etc. That seems duplicated; we should not duplicate. The perks list is enough. The later paragraph about Amazon benefits is more detailed but may be considered boilerplate? It's about benefits but repeats. We should keep substantive info; maybe we can include the detailed benefits as part of Benefits section? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The later paragraph includes many benefits: health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, parental leave. That's more detailed than the earlier perks list. We should include that detail. However we must avoid duplication; we can combine. We need to decide: The "Perks" list is short; the later paragraph gives more detail. We should include the detailed benefits as part of Benefits section. The earlier list is also benefits but less detail. We'll combine into a Benefits section with the detailed list. Thus Benefits section: include items: - Medical, Dental, Vision & Disability Insurance - 401(k) - Maternity & Parental Leave - Flexible PTO - Amazon Employee Discount - Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage) - 401(k) matching - Paid time off - Parental leave But note duplication: 401(k) appears twice; we can keep one maybe with matching. We'll keep both? Might be considered duplicate. Better to merge: "401(k) with matching". Also parental leave appears twice. We'll combine. Let's craft a Benefits list: - Medical, Dental, Vision & Disability Insurance - 401(k) with matching - Maternity & Parental Leave - Flexible PTO - Amazon Employee Discount - Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage) - Paid time off But we already have Maternity & Parental Leave; Paid time off maybe separate. We'll keep both. Now Pay: we have salary ranges per location: - US, WA, Seattle - Annually $159,300—$202,400 USD - US, CA, San Francisco - Annually $166,600—$212,800 USD - US, CA, Irvine - Annually $159,300—$202,400 USD We need to include Pay section. Should we also include location? Possibly as a short paragraph before Pay. But location is not a heading; we can include in a

    under About the role or separate? The instruction: "fold minor metadata into a short

    or drop it." Location is minor metadata; we can include in a short paragraph maybe under About the role or separate. We'll add a

    after About the role: "Locations: San Francisco, CA; Irvine, CA; Seattle, WA." Now Schedule: no info, so omit. Now we need to output HTML with headings

    for each section we include. Sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We have qualifications and skills maybe combined? The posting has "You Have:" which includes experience, education, technical skills. Bonus Points also qualifications. We could split into Requirements (maybe experience/education) and Skills (technical). But we can also just have one section "Requirements" that includes all. However the instruction: "Prefer a few substantive sections over many thin ones." So we can combine into one section maybe "Requirements". But they ask to use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have content for Requirements (experience, education), Qualifications (maybe degree), Skills (automation, scripting, AI/ML, incident response, knowledge, background, frameworks). Bonus Points could be additional qualifications/skills. We could make three sections: Requirements, Qualifications, Skills. But that may be thin. Better to have Requirements (experience/education) and Skills (technical). Qualifications maybe not needed. Let's decide: - Requirements: "3+ years relevant experience doing information security work or equivalent BS degree in Information Security, Information Systems, Computer Science, Computer Engineering, or other related fields" plus maybe "B.S. or M.S. in Computer Science, Computer Engineering, Software Security, or a related technical discipline" (Bonus Points). That's education/experience. - Skills: automation experience using scripting/languages, ability to design AI/ML playbooks, experience coordinating responses, knowledge of security issues/threat landscape, background in cloud/host/network/app security, familiarity with IR frameworks, experience/familiarity with streaming/content creation, handling security incidents in hybrid cloud (AWS,GCP) and log dives, passion for Twitch. That seems substantive. We'll also include maybe "Bonus Points" as part of Skills or Requirements? We'll incorporate into Skills. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We'll not include Qualifications separate. Now produce HTML. Structure:

    About the role

    Twitch is looking for a Security Incident Response Engineer to join our SIRT. Reporting to the SIRT Manager, you'll be at the heart of our mission to find, handle, and learn from security incidents across our global platform. We're looking for engineers who thrive coordinating response to emerging issues in information security who are ready to level up our defense. If you're passionate about protecting the Twitch community and solving complex security puzzles, we want to hear from you! You can work from San Francisco, CA; Irvine, CA; or Seattle, WA.

    Locations: San Francisco, CA; Irvine, CA; Seattle, WA.

    (maybe redundant; we already mentioned locations in paragraph; we could keep just one. To avoid duplication, we can just keep the paragraph and not add separate location line. The paragraph already includes location. So we can skip separate.) Thus only one paragraph. Now Responsibilities:

    Responsibilities

    • ...
      • ...
    Now Requirements:

    Requirements

    • 3+ years relevant experience doing information security work or equivalent BS degree in Information Security, Information Systems, Computer Science, Computer Engineering, or other related fields
    • B.S. or M.S. in Computer Science, Computer Engineering, Software Security, or a related technical discipline
    Now Skills:

    Skills

    • Automation experience using scripting or programming languages (Go, Python, Ruby, Shell, or Perl)
    • Ability to securely design and implement AI/ML-driven playbooks to automate common security operations

    • Similar jobs