Palantir
Product Reliability Engineer - Defense
About this role
Palantir seeks a Product Reliability Engineer to ensure the stability and performance of critical defense software systems. You'll own end-to-end service reliability, respond to outages, improve system observability, and drive strategic infrastructure improvements while supporting defense-focused customers.
What you'll do
- Monitor service health and respond to production outages during on-call shifts
- Investigate and troubleshoot critical issues for key defense customers
- Build observability and monitoring solutions for complex distributed systems
- Address technical debt and improve resilience in core codebases
- Lead infrastructure migrations and stability enhancements
- Collaborate with product teams to inform strategic investments and improvements
What they're looking for
- Distributed systems troubleshooting and debugging
- Infrastructure and DevOps practices
- System observability and monitoring
- Software engineering and code analysis
- On-call incident response and escalation management
- Root cause analysis
- Communication across technical teams
- Problem-solving and critical thinking
Benefits
- Mentorship from experienced engineers
- Clear onboarding framework
- Opportunity to impact mission-critical defense systems
- Deep technical work on complex infrastructure
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
- Walk us through a time when you diagnosed and resolved a critical production outage. What was your approach to determining root cause versus applying a quick fix?
- How do you approach adding observability and monitoring to a complex system you're unfamiliar with? What metrics or signals would you prioritize?