Engineer, Cybersecurity Architecture at Intercontinental Exchange (ICE)
Provo, UT
—
Aug 12, 2026
Provo, UT
Sep 24, 2026
What this job asks for AI summary
A cybersecurity architecture role at ICE (Intercontinental Exchange) focused on security design reviews, threat modeling, and control assessments across network, cloud, data, and system environments. The engineer supports architecture reviews and gap analyses, collaborates with infrastructure and engineering teams to embed security requirements before implementation, and maintains security documentation and reference architectures. Suited to a mid-level information security professional with broad technical security knowledge.
Mid level · 3+ years
Posted 2 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
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 Aug 15, 2026. It is a model, not a headcount.
Why we read it this way (5)
No work location is specified in the posting — CBSA and state are left blank. The role is assumed US-based given the employer (ICE, headquartered in Atlanta, GA) but the posting does not confirm a specific office or remote status.
The 'Specific Technologies' section is not explicitly labeled as 'Required' or 'Preferred'; it reads as a technical knowledge list integral to the role's responsibilities and is treated as required accordingly.
The degree requirement states 'Degree in engineering discipline or equivalent experience,' which accepts equivalent experience in lieu of a degree — degree requirement is therefore not hard-gated.
The alt SOC 15-1299 is noted because the role's primary focus on security architecture and design reviews sits at the boundary between pure security analysis (15-1212) and a broader architecture/engineering function not perfectly captured by any single code.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): key management.
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.