Twitch · posted · checked
Security Incident Response Engineer
PythonRubyOn-site · San Francisco and SeattleMid-level
Who can apply
On-site · San Francisco and Seattle
Location: Irvine, CA / San Francisco, CA / Seattle, WA
About Us
Twitch is the world’s biggest live streaming service, with global communities built around gaming, entertainment, music, sports, cooking, and more. It is where thousands of communities come together for whatever, every day.
We’re about community, inside and out. You’ll find coworkers who are eager to team up, collaborate, and smash (or elegantly solve) problems together. We’re on a quest to empower live communities, so if this sounds good to you, see what we’re up to on LinkedIn and X, and discover the projects we’re solving on our Blog. Be sure to explore our Interviewing Guide to learn how to ace our interview process.
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.
You Will:
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