← home

Information Security Engineer - Infrastructure Security

Palantir United States Washington, D.C. hybrid
$198k–$300kEstimateEstimate from 12 posted bands in Washington · mid — not the company's offer. Based on 12 similar postings, high confidence.

Estimate from 12 posted bands in Washington · mid — not the company's offer. Based on 12 similar postings, high confidence.

Level: Mid, typically 2–6 years. Titles vary by employer; see the levels guide.

At a glance

Workplacehybrid · Washington, D.C.
Level / familyMid · Product & platform security
Days listed140d
Last checkSep 3, 2026
Other open roles6 at Palantir

Skills this posting names

Cloud securityEndpoint securityComplianceActive Directory / Entra

Add your skills on the profile page (kept in this browser only) to see which ones also appear there.

A World-Changing Company
 
Palantir builds the world’s leading software for data-driven decisions and operations. By bringing the right data to the people who need it, our platforms empower our partners to develop lifesaving drugs, forecast supply chain disruptions, locate missing children, and more.

The Role

We're looking for an Information Security Engineer who can think broadly about how infrastructure is built, attacked, defended, and improved. You may have deep experience in one area—such as endpoint security, Active Directory, Data Loss Prevention, cloud security, identity, or detection and response—but you’re motivated by solving security problems across the environment.

As an Information Security Engineer focused on infrastructure security, you'll help protect Palantir's global endpoints, servers, identity systems, applications, networks, and data flows. You'll work across teams to reduce attack surface, improve defensive controls, investigate security events, and turn security findings into durable architectural and operational improvements.

This is not just a corporate security role; the adversaries we face are sophisticated. We need someone who understands both the details and the broader system: how a weakness in one part of the environment can create risk somewhere else, how controls interact, and how to build security improvements that hold up in practice.