Platform Security Engineer at Future Secure AI
Austin, TX
—
Jul 1, 2026
Austin, TX
Jul 21, 2026
What this job asks for AI summary
A hands-on engineering role focused on securing the full software delivery lifecycle — from cloud infrastructure (AWS/EKS) and CI/CD pipelines to supply-chain controls and AI/agentic systems. The engineer will build security tooling, run threat models and design reviews, harden the path from code commit to production, and participate in incident response. Suited to someone with a strong software engineering background who can translate security requirements into developer-integrated workflows.
Senior level · 5+ years · National · 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
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $132,021 (middle half $99,961–$167,095).
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 (10)
This role sits at the intersection of security engineering and software development — it builds security tooling and automation (15-1252 signal) but is framed around product/application security ownership (15-1212 signal). 15-1212 was chosen as primary because the JD's core framing is security design, threat modeling, and securing the supply chain/cloud, not general software delivery.
Location is not stated anywhere in the posting. Remote status is unclear; 'flexible work environment' is mentioned but does not confirm fully remote. Remote is marked false as a conservative default.
Compensation is described only as 'competitive salary' with no figures provided.
Python, Go, and TypeScript are listed as interchangeable options for the general-purpose language requirement; Python is used as the primary name with Go and TypeScript as alternatives.
Terraform, CDK, and CloudFormation appear under Preferred Qualifications as IaC security tools and are marked preferred accordingly.
Socket and Snyk are listed together as example dependency/SCA tools under Responsibilities (narrative context, not a hard-gate section); they are marked preferred. Snyk is used as primary with Socket as an alternative since they serve the same function.
GitHub Enterprise and GitHub Actions appear in the Responsibilities narrative as examples, not in the Minimum Qualifications gate; marked preferred.
HashiCorp Vault, JFrog Artifactory, Cosign, and Kyverno appear as parenthetical examples in the Responsibilities section, not in Minimum Qualifications; marked preferred.
SLSA and sigstore/Cosign appear under Preferred Qualifications; SLSA is emitted separately as a supply-chain framework skill, Cosign covers sigstore/Cosign.
LLM/AI system security experience is explicitly listed under Preferred Qualifications.
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.