Skip to main content

SpyCloud

Security Research Engineer III

Austin, Texas | Remote (Remote)$108k–$140kfull-timemidAdded 2 days ago

About this role

SpyCloud seeks a Security Research Engineer III to design and maintain internal tooling for acquiring and analyzing recaptured breach and malware data. You'll build cloud infrastructure, automation pipelines, and collaborate with the security research team to support data collection and analysis workflows.

What you'll do

  • Design and maintain internal tools for acquiring and parsing underground breach and malware data
  • Build and deploy cloud infrastructure using Infrastructure as Code (Terraform, Ansible)
  • Implement automated CI/CD pipelines for testing and deployment
  • Collaborate with research team on data source targeting and collection
  • Identify and implement improvements to data workflows and ETL pipelines
  • Participate in security research on threat actors and malware investigations

What they're looking for

  • Python (highly skilled)
  • Golang (preferred)
  • Infrastructure as Code (Terraform, Ansible)
  • CI/CD pipeline development
  • Cloud infrastructure deployment
  • Data pipeline and ETL design
  • Problem-solving and critical thinking
  • Self-directed execution and communication

Benefits

  • 401(k) with employer contribution
  • Health, vision, and dental insurance with HSA option
  • Employer-paid life, short-term, and long-term disability insurance
  • Generous PTO and 16 paid holidays annually
  • Flexible and remote-friendly work options
  • Engaging workspace in South Austin
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.

SpyCloud

View all jobs at SpyCloud

Likely interview questions

  • Walk us through a time you designed and deployed infrastructure using Terraform or Ansible—what challenges did you face?
  • How have you optimized data pipelines or ETL workflows in previous roles, and what metrics did you use to measure improvement?