Platform Engineer - Palantir

Hands-On Builder, Cost Steward & Component Curator

Role Summary & Mission 

The Platform Engineer - Palantir is the technical owner of Acrisure’s Palantir environment — the person ultimately accountable for the substrate that every Palantir use case is built on. Where FD Partner, FD Delta, and FD Echo are forward-facing roles deploying value to business units, this role is the internal-facing counterpart: the operator, architect, and component curator who defines what the entire Program can build on, how it builds, and how efficiently it builds. 

This role is intentionally designed as both senior and hands-on. The Platform Engineer sets the strategy for ingress and egress, marking and permissions architecture, environment topology, compute and storage cost optimization, release governance, and the reusable component catalog — and then implements that strategy hands-on inside the platform. The person in this seat must be the most technically credible voice in the room on Palantir platform mechanics, while also presenting cost-to-value, capacity, and reusability tradeoffs to the CTO and executive sponsors. Credibility in this role is earned through doing, not delegating. 

This is a primarily internal-facing role. Travel is minimal — typically less than 10% (1-2 nights/month) on average, primarily for Palantir partner engagement, working sessions, and occasional business unit deployments. 

Key Responsibilities 

Hands-On Platform Operations 

• Actively configure and operate Palantir tenant settings across the platform stack — Projects, Groups, Markings, Roles, Resource Queues, Compute, and product-level controls — making changes directly in the platform rather than routing them to engineers. 

• Design and implement the ingress strategy: source system connections, connectors, schema management, and standards for incremental, batch, and streaming data flows. 

• Design and implement the egress strategy: Marketplace exports, OSDK and external API exposure, file/data export controls, and downstream consumption boundaries. 

• Own the permissions architecture across the platform — marking taxonomy, group hierarchy, role assignments, and least-privilege standards — and personally maintain the most sensitive configurations. 

• Personally triage and resolve platform admin issues — permissions, provisioning, ingress/egress configuration, and resource queue contention — rather than routing them to Platform Engineers or Palantir support. 

• Be a go-to resource for external teams leveraging the Palantir Platform and escalating questions and issues for resolution.  

Componentization & Reusability 

• Drive the platform-wide reusable component catalog — pipeline templates, Ontology patterns, Workshop building blocks, OSDK modules, Marketplace products, reusable agents, and shared utilities — covering both platform-management and business-facing use cases. 

• Establish standards for what gets componentized, how components are versioned and documented, and how they are discovered and consumed by FD Delta, FD Echo, and the broader Platform. 

• Partner with FD Delta and FD Echo to extract reusable patterns from delivered use cases, promote them into the catalog, andconsolidateduplication across the portfolio.

• Maintain a library of platform-management components — provisioning workflows, permissions templates, audit reports, cost dashboards — that the Platform Engineering team uses tooperatethe environment efficiently.

Cost & Resource Optimization

• Own end-to-end FinOps for the Palantir environment — usage forecasting, compute optimization, build schedule efficiency, storage tiering, and licensingutilizationacross all platform tools.

• Establish resource quotas, project allocation models, and guardrails across thePlatformportfolio to prevent runaway cost while enabling deliveryvelocity.

• Identifyand remediate cost anomalies in real time; partner with Finance on chargeback, showback, and capacity-based budgeting models.

• Present cost-to-value tradeoffs, capacity decisions, and reusability ROI to the CTO and executive sponsors with supporting data, framed in business terms.

Governance, Standards & Team Leadership

• Establish and enforce platform governance standards: branching strategy, environment promotion (dev/staging/prod), release approvals, and change management — and define the SLAs for platform admin services that the Platform Engineering team commits to.

• Drivethe Palantir platform security posture in partnership with InfoSecand Data team— marking taxonomy, audit logging, sensitive data handling, and compliance support (SOC 2, NYDFS, GDPR, and other applicable regimes).

• Maintain platformstandardsdocumentation and ensure adherence across FD Delta, FD Echo, Platform Engineering, and Palantir FD Team contributions.

• Support the Platform Engineering team: contributing to mentorship, technical direction, and standards setting.

• Support escalation triage for platform constraints raised by FD Partner, FD Delta, and FD Echo — and contribute technical input on platform-vs-delivery tradeoffs.

• Coordinate directly with Palantir on platform upgrades, feature rollouts, and capability roadmap alignment.

Required Skills & Competencies 

Palantir Platform Proficiency (Required — Not Optional) 

• Deep hands-on expertise with Palantir tenant administration across the platform stack: Projects, Groups, Markings, Roles, Resource Management, Compute Modules, and audit/observability tooling. 

• Hands-on experience with ingress patterns — connectors, agent-based ingestion, source system integration, and pipeline scheduling at enterprise scale. 

• Hands-on experience with egress controls — Marketplace, OSDK external endpoints, data export governance, and external-facing API exposure.

• Workingproficiencyacross the Palantir product surface — Foundry (Pipeline Builder, Code Repositories, Ontology, Workshop, OSDK), AIP (Agent Studio, Logic, Evals), and adjacent products (Marketplace, Quiver) — sufficient to administer, govern, and componentize each.

• Strong Python, TypeScript/JavaScript, and SQL skills — the Platform Engineer writes platform tooling, automation, reusable components, and remediation code, not just reviews it.

Componentization & Standards

• Demonstrated experience building andmaintainingshared componentlibraries, internal developer platforms, or reusable pattern catalogs.

• Strong API design and abstraction instincts — knows when something is ready to be a reusablecomponentversus a one-off implementation.

• Documentation and developer-experience sensibility — components only deliver value if they get discovered, understood, and adopted.

Platform Operations & FinOps

• Demonstrated experienceoperatingan enterprise data platform at scale (Foundry, Snowflake, Databricks, or equivalent).

• Strong FinOps fundamentals — usage forecasting,computeand storage cost optimization, chargeback model design, and capacity planning.

• Experience with release management, CI/CD pipelines, and environment promotion strategies.

Governance & Security

• Working knowledge of enterprise security and access control patterns: RBAC, ABAC, attribute-based markings, least privilege, identity federation, and SSO.

• Experience supporting compliance frameworks such as SOC 2, NYDFS, GDPR, HIPAA, or similar regulated environments.

• Demonstrated comfort partnering with InfoSec, Internal Audit, and Enterprise Architecture peers — translating platform mechanics into language those audiencesrequire.

Leadership & Communication

• Demonstrated ability to work effectively within a senior technical team — contributing to direction and standards while executing hands-on.

• Ability to present platform cost, capacity, reusability, andrisktradeoffs to a CTO/CIO-level audience and to translate technical decisions into business outcomes.

• Strong written communication skills — able to author governance documents, RFCs, architecture decision records,componentspecifications, and platform standards.

Experience

• 5–10+ years of experienceoperating, architecting, and administering enterprise platforms.

• Prior Palantir Foundry administration experience strongly preferred; experienced platform leads from Snowflake, Databricks, or AWS/Azure-native enterprise data stacks are encouraged to apply.