Arlington

Salary
Posted
Jul 26, 2026
Location
Arlington
Last confirmed open
Jul 28, 2026

What this job asks for AI summary

A data security engineering role supporting a federal government client, focused on protecting sensitive data across enterprise platforms through encryption, access controls, DLP, and activity monitoring. The engineer will conduct risk assessments, support audits and compliance activities (NIST, FISMA, FedRAMP), and collaborate with governance and engineering teams to secure data pipelines, APIs, and analytics environments. Suited to a mid-career security professional with hands-on data platform security experience in regulated environments.

Mid level · 3+ years · Secret clearance

Must have (8)
encryptionKMS or HsmRBAC or Abacidentity federationDLPNISTFISMAFedRAMP
Nice to have (3)
AWS, Azure or GCPMicrosoft Purview, Aws Macie or BigidSecurity+, CISSP or Ccsp

“or” means any one of them counts — you don't need all of them.

Posted 3 times — it's one opening, so apply once.

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

What won't set you apart
NIST40%

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 29, 2026. It is a model, not a headcount.

Why we read it this way (8)

The title includes 'Journeyman,' a federal/government contracting seniority label roughly equivalent to mid-level; the 3–6 year experience range and scope of responsibilities support a Mid classification.

Location is not specified in the posting; it references a U.S.-only federal IT environment and requires U.S. citizenship, but no city, state, or remote status is stated.

The degree requirement lists a Bachelor's degree 'or equivalent relevant experience,' so no hard degree gate is set.

Secret clearance is listed as a requirement to obtain and maintain — not a current active clearance gate, but treated as a hard requirement per the posting's language.

HIPAA is mentioned as a contextual framework ('where appropriate') rather than a firm requirement, so it is omitted from the skills list.

Cloud platforms (AWS, Azure, GCP) and DLP tools (Microsoft Purview, AWS Macie, BigID) appear under Preferred Qualifications and are marked accordingly.

Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): privileged access management.

Requires a Secret clearance — the cleared population is a small fraction of this occupation, so the real candidate pool is materially smaller than the estimate below, which does not model clearance.

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.

Apply

Apply on employer site ↗