Palantir
Offensive Security Engineer
About this role
Palantir seeks an Offensive Security Engineer to conduct authorized penetration testing of internal systems and infrastructure, develop LLM-powered security tools, and coordinate third-party assessments. You'll identify attack paths, work with engineering teams on remediation, and help build the next generation of automated offensive security capabilities.
What you'll do
- Perform penetration testing on internal applications, infrastructure, and cloud environments using adversarial techniques
- Chain security findings into realistic attack scenarios and document exploitable pathways
- Collaborate with product and infrastructure engineers to remediate identified vulnerabilities
- Design and develop agentic offensive security tools that leverage LLMs to automate tradecraft
- Manage and coordinate third-party penetration testing engagements, including scoping and risk prioritization
- Transform external assessment results into actionable remediation plans
What they're looking for
- Penetration testing and attack chain development
- Cloud security assessment (AWS, Azure, or GCP)
- Network and infrastructure security testing
- Application security and vulnerability analysis
- LLM and AI systems familiarity
- Security tooling development
- Communication and stakeholder coordination
- Threat modeling and risk prioritization
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Palantir
Palantir builds data platforms and software solutions that help government and enterprise customers tackle complex operational challenges, with a focus on responsible AI governance and privacy. The company is hiring software engineers and interns for forward-deployed customer roles, infrastructure and platform teams, and specialized privacy and civil liberties engineering positions.
- Website
- palantir.com
Likely interview questions
- Describe a complex attack chain you've discovered during a penetration test and how you communicated findings to the affected engineering team.
- How would you approach designing an LLM-driven offensive security tool, and what guardrails would you implement?