Senior Palantir Foundry Engineer / FDE (US-Based, Ongoing Contract Work)

We are a Palantir Foundry and AIP delivery studio building a standing roster of senior, US-based Foundry engineers for ongoing client engagements. This is not a one-off gig. We are looking for a small number of genuinely experienced people we can engage repeatedly as work comes in, on monthly or hourly terms, embedded into client programs under our delivery. We place engineers onto live Foundry engagements where they are expected to ship from day one, not ramp for a quarter. You would work as part of our delivery team, on our programs, for our clients. What we need you to own across the Foundry stack: - Ontology design and modeling - Pipeline Builder and data integration (batch and streaming) - Code Repositories (PySpark, TypeScript transforms) - OSDK and off-platform / custom application integration - Workshop application development - AIP: agent configuration, logic, and evaluation - Foundry administration, permissions, and data governance where required Who you are: - You have shipped production Foundry work for real organizations, not just trained on it - You can drop into an active engagement and be useful in week one - You communicate clearly and work to a professional delivery standard - You are US-based and can work US business hours - You are available for ongoing engagement, full-time embedded. How engagement works: - We bring the client relationship and the program. You bring the engineering. - Work is delivered under our brand and program structure. - Terms are flexible to the contract: monthly embedded, fractional, or hourly blocks. - Strong performers become first-call for our incoming pipeline, which is growing. If you have real Foundry depth and want steady, senior-level delivery work without chasing individual gigs, apply with specifics. Vague "I know Palantir" applications will not be considered. Tell us what you have actually built. Questions to answer in your application: - Are you US-based, and what is your timezone and weekly availability (hours/week)? - Describe one production Foundry system you personally built. - What was the business problem, what parts of the stack did you use (Ontology, Pipeline Builder, OSDK, Workshop, AIP), and what shipped? Be specific. - How did you learn Foundry, and how long have you worked on it? (e.g. at Palantir, at a Palantir customer, at a partner/SI, self-taught on a project) - Walk through how you would model an Ontology for a [supply chain / logistics / operations] use case. What are objects, links, and actions in your approach? (Short answer is fine, we want to see how you think.) - Are you comfortable working under another firm's brand and delivery structure (white-label)?