Skip to main content

FluidStack

Security Engineer, Incident Response

  • Confirmed live in the last 24 hours
  • $275k–$344k
  • Mid level
  • Full-time
  • On-site · Austin, TX
  • Added 2 months ago

About this role

Fluidstack is seeking a Security Engineer to build and lead its incident response program from the ground up, protecting critical AI infrastructure. This role involves owning the entire security lifecycle, from detection and containment to eradication and post-incident review, with a focus on securing highly valuable model weights against sophisticated threats. If you thrive in a fast-paced, autonomous environment and are passionate about tackling challenging security problems at scale, this is a unique opportunity.

What you'll do

  • Lead incident response across corporate, cloud, and data center environments.
  • Develop detection logic, response playbooks, and forensic tooling.
  • Investigate security incidents, correlating signals from various systems.
  • Define severity models, on-call rotations, and escalation paths.
  • Partner with teams to implement improvements based on incident findings.

What they're looking for

  • Incident Response
  • Digital Forensics
  • Cloud Security (AWS, GCP)
  • Detection Engineering
  • SIEM/SOAR
  • Security Tooling
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

FluidStack

FluidStack builds AI infrastructure at scale, developing data centers and warehouse operations designed to handle gigawatt-capacity compute deployment. The company is hiring for warehouse engineers, data center operations specialists, product engineers, and people leaders to support rapid infrastructure expansion across multiple sites.

Industry
Technology & Software
View all jobs at FluidStack

Likely interview questions

  • Describe a major security incident you led from detection to resolution, and the difficult decisions you had to make.
  • Explain your experience building detection logic and response playbooks. Can you provide an example of a successful implementation?