Platform Engineer - Palantir

About Acrisure

Acrisure is a global fintech leader empowering ambitious businesses and individuals with customized solutions that drive growth and impact. We combine cutting‑edge technology with expert human support to deliver tailored insurance, reinsurance, payroll, benefits, cybersecurity, mortgage services, and more.

In the last twelve years, Acrisure has grown from $38million in revenue to nearly $5billion and now employs more than 19,000 colleagues across 20+ countries.

The Platform Engineer - Palantir is the technical owner of Acrisure’s Palantir environment, responsible for the substrate that every Palantir use case is built on. The role is an internal‑facing position and combines senior strategy with hands‑on implementation. The engineer sets the strategy for ingress & egress, permissions architecture, environment topology, compute & storage cost optimization, release governance, and reusable component catalog, and then executes that strategy on the platform.

• 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.

• Drive the platform‑wide reusable component catalog – pipeline templates, Ontology patterns, Workshop building blocks, OSDK modules, Marketplace products, reusable agents, and shared utilities.
• 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, and consolidate duplication across the portfolio.
• Maintain a library of platform‑management components – provisioning workflows, permissions templates, audit reports, cost dashboards – that the Platform Engineering team uses to operate the environment efficiently.

• Own end‑to‑end Fin Ops for the Palantir environment – usage forecasting, compute optimization, build schedule efficiency, storage tiering, and licensing utilization across all platform tools.
• Establish resource quotas, project allocation models, and guardrails across the Platform portfolio to prevent runaway cost while enabling delivery velocity.
• Identify and 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.

• 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.
• Drive the Palantir platform security posture in partnership with Info Sec and Data team – marking taxonomy, audit logging, sensitive data handling, and compliance support (SOC2, NYDFS, GDPR, and other applicable regimes).
• Maintain platform standards documentation…