Offensive Security Engineer at Palantir Technologies
Washington
$145,000–$200,000from the description
Aug 13, 2026
Washington
Sep 24, 2026
What this job asks for AI summary
An internal offensive security role at Palantir focused on penetration testing the company's own products, infrastructure, and cloud environments. The engineer conducts web application, network, Active Directory, and cloud security assessments; chains findings into realistic attack paths; and coordinates third-party pentest engagements. A growing portion of the work involves designing and building LLM-driven agentic offensive security tooling. Suits an experienced practitioner who can both break things and write the automation to do it at scale.
Senior level · 4+ years · New York-Newark-Jersey City, NY-NJ-PA · Full-time
Quick apply — this platform usually takes a CV and a few fields.
“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 230 people in the New York-Newark-Jersey City, NY-NJ-PA area plausibly meet what this posting asks for (information security analysts). range 120–300
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $143,559 (middle half $110,181–$179,574). 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 Aug 15, 2026. It is a model, not a headcount.
Why we read it this way (8)
The posting does not specify a city; Palantir's primary US offices are New York and Denver — the CBSA has been set to New York as a best guess. Verify the actual office location before posting.
The role is classified as Information Security Analysts (15-1212) because its primary day-to-day work is offensive security analysis — penetration testing, red teaming, and threat-path assessment. However, a meaningful portion of the work involves building agentic offensive tooling, which pulls toward Software Developers (15-1252); that code is listed as the alt SOC.
A US security clearance is listed as 'preferred', not a hard gate, so the clearance requirement is set to None.
Offensive security certifications (OSCP, OSWE) and CTF/bug bounty experience are explicitly called 'a plus but not required' — listed under What We Value as preferred.
Docker and Kubernetes are listed together as a single containerized-environment requirement in What We Require; both are captured as separate skills since they are distinct technologies used alongside each other.
Python and Go appear as examples of acceptable scripting/programming languages in the requirements block; Python is listed as primary with Go as an alternative since the JD treats them as interchangeable for this gate.
AWS, Azure, and GCP appear as interchangeable cloud platform examples within a single hard-gate requirement; AWS is listed as primary with Azure and GCP as alternatives.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): Web application penetration testing.
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.