Platform DevSecOps Engineer at Future Secure AI
Austin, TX
—
Jul 6, 2026
Austin, TX
Jul 21, 2026
What this job asks for AI summary
A hands-on security engineering role focused on owning the full secure software development lifecycle for an AI agent platform and its agents. Day-to-day work spans CI/CD pipeline security, Kubernetes cluster hardening across multiple clouds, supply-chain integrity (SBOMs, artifact signing, dependency provenance), secrets management, and CVE remediation campaigns. Suits an experienced DevSecOps practitioner comfortable working across GitOps infrastructure and influencing both technical and non-technical stakeholders.
Senior level · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 26,400 people nationally plausibly meet what this posting asks for (software developers). range 15,900–39,700
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
Location is not stated anywhere in the posting; CBSA and state are left blank. The 'flexible work environment' framing suggests remote-friendly but no explicit remote-only or office-location claim is made — remote is set to true as the most consistent reading.
The role sits at the intersection of platform/infrastructure engineering and security. It is classified as Software Developers (15-1252) because the JD explicitly emphasises hands-on work in pipelines, infrastructure-as-code, and Kubernetes clusters — shipping and enforcing security through code — rather than governance or policy analysis. Information Security Analysts (15-1212) is the close runner-up given the SSDLC ownership mandate.
No overall years-of-experience figure is stated; seniority is inferred as Senior from the scope (single point of accountability for SSDLC, multi-cloud fleet, cross-functional influence) and the 'deep, practical' language in minimum qualifications.
AWS and Azure are listed together as 'AWS and/or Azure' in minimum qualifications; AWS is the primary name with Azure as an alternative. EKS/AKS, Terraform/Terragrunt, and Helm/Helmfile all appear under Preferred Qualifications.
SBOM/VEX appears in both minimum qualifications (supply-chain security context) and preferred qualifications (tooling experience). It is marked preferred because the minimum qualifications section uses descriptive/ownership language rather than explicit tool-gating language for this item.
No compensation figures are provided in the posting.
This posting reads as a fully-remote role, so it was scored against the national candidate pool rather than a single metro.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.