Drimva

Figure AI

Security Engineer, Infrastructure Security

$150K–$250K

San Jose, CA +1 · Full-time · Posted Sep 17, 2026

Location
San Jose, CA
San Jose, California, United States
Experience
6+ years of security / software development experience.
Education
BS/BA in Computer Science, Engineering, Information Systems, or equivalent years of experience in a related technical field.

About the job

Designs and manages infrastructure security controls, identity systems, network protections, and security visibility across cloud, on-premises, and neocloud environments.

What you'll do

  • Partner with infrastructure, networking, and detection teams to secure AI tooling, networks, and incident response.
  • Own authentication and authorization across environments, including workload identity and time-bound elevated access.
  • Build posture measurement and remediation tooling, and establish secure-by-default zero-trust networking patterns.

What they ask for

  • Security knowledge or experience in one or more listed areas, such as Kubernetes, networking, authentication/authorization, or cloud security tools.
  • Experience developing and deploying services in multi-cloud environments; familiarity with at least two of Azure, AWS, or Google Cloud Platform is preferred.
  • 6+ years of security / software development experience.
  • Strong software engineering skills in C/C++, Rust, Golang, Python, or similar; BS/BA in a related field or equivalent years of experience in a related technical field.

Nice to have

  • Familiarity with zero-trust networking, workload identity, secrets management, or security controls delivered as reviewed, versioned code.
  • Experience securing AI/ML tool usage or on-prem/neocloud environments, or building self-service security tooling.

Pay

$150,000 - $250,000 per year (USD, base salary)

Tools

Kubernetes, Azure, AWS, Google Cloud Platform, C/C++, Rust, Golang, Python

AI focus

Securely roll out AI tooling across infrastructure and secure AI/ML tool usage.

Model-written summary · the original posting is authoritative

First seen Oct 10, 2026 · Last verified Nov 4, 2026 (UTC)