Job Opportunities API

AURIS AI | PLATFORM ENGINEERING Platform Engineer - Palantir Hands-On Builder, Cost Steward & Component Curator Note: This is a full-time role and we do not offer C2C or C2H employment and are not able to sponsor visas for this position.       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 $38 million in revenue to nearly $5 billion and now employs more than 19,000 colleagues across 20+ countries. Built on entrepreneurial spirit, we prioritize leadership, accountability, and collaboration — equipping our teams to work at the highest levels and solve meaningful challenges. 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 consume