Okta IAM / Identity Integration Engineer at Peraton
UNAVAILABLE
$66,000–$106,000from the description
Jul 19, 2026
UNAVAILABLE
Jul 21, 2026
What this job asks for AI summary
This fully remote role centers on building and maintaining a large-scale identity and access management platform for the Department of Defense, replacing an existing authentication system used by millions of military members, veterans, and their families. Day-to-day work involves configuring Okta Identity Engine, implementing embedded SDK authentication flows, developing mobile identity integrations for iOS and Android, and ensuring compliance with federal cybersecurity frameworks. It suits engineers with deep hands-on IAM experience across modern identity protocols, federation, and DoD security requirements.
Senior level · 5+ years · 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 320 people nationally plausibly meet what this posting asks for (software quality assurance analysts and testers). range 65–470
Applicant volume Light — Few people clear these requirements, so an application that does clear them gets looked at. Worth applying to even if you miss a nice-to-have.
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $106,594 (middle half $82,076–$136,109). This posting is about at that midpoint.
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 (11)
SOC classification is Medium confidence: the role is primarily an IAM/identity integration engineer — designing and implementing authentication and federation services — which sits at the intersection of Information Security Analysts (15-1212) and the broader 'Computer Occupations, All Other' (15-1299) category. The security compliance and DoD cybersecurity mandate emphasis tips it toward 15-1212.
Clearance: the JD requires the ability to obtain and maintain a Public Trust, which is a suitability determination, not a formal US security clearance (Confidential/Secret/TS). Clearance is therefore set to None.
Degree requirement: the JD states '5 years with BS/BA; 3 years with MS/MA; 0 years with PhD', meaning a PhD substitutes for all experience and a degree is not strictly required — equivalent experience is accepted. Degree requirement is set to None.
Total years minimum is set to 5, reflecting the BS/BA pathway as the baseline (the most common credential path).
DevSecOps and CI/CD appear in the required qualifications section but are framed as 'familiarity with', which is softer gating language — listed as preferred accordingly.
NIST SP 800-63 appears explicitly under Preferred Qualifications.
CAC/PIV and Purebred appear under Preferred Qualifications.
JWT is extracted as a standalone skill representing the token lifecycle management requirement (ID, Access, and Refresh tokens are all JWT-based in this context).
Okta Certified Administrator / Okta Certified Professional certifications are listed under Preferred Qualifications but are certifications rather than named technologies, so they are omitted from the skills list per extraction rules.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): NIST SP 800-63.
Caller marked this a fully-remote role — scored against the national candidate pool.
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.