1

Palantir Deployment Strategist Jobs in Decatur, GA

The Platform Engineer sets the strategy for ingress and egress, marking and permissions ... unit deployments. Key Responsibilities Hands-On Platform Operations * Actively configure and ...

Develop robust AI evaluation strategies to ensure the quality, reliability, and performance of ... Experience with data engineering using PySpark, SQL, and Palantir Foundry, including Foundry AIP

AL/ML Engineer

Atlanta, GA · On-site

$79K - $105K/yr

Develop robust AI evaluation strategies to ensure the quality, reliability, and performance of ... Experience with data engineering using PySpark, SQL, and Palantir Foundry, including Foundry AIP

Develop robust AI evaluation strategies to ensure the quality, reliability, and performance of ... Experience with data engineering usingPySpark, SQL, and Palantir Foundry, including Foundry AIP

Develop robust AI evaluation strategies to ensure the quality, reliability, and performance of ... Experience with data engineering using PySpark, SQL, and Palantir Foundry, including Foundry AIP

... deployment. In this role, you will also lead the development of AI evaluation strategies, prompt ... Lead the design and development of scalable AI / ML systems using PySpark and Palantir Foundry for ...

... deployment. In this role, you will also lead the development of AI evaluation strategies, prompt ... Lead the design and development of scalable AI/ML systems usingPySparkand Palantir Foundry for ...

RaceTrac is seeking an Analytics Consultant to join their Enterprise Strategic Analytics + Data ... deployment of analytical solutions. • Collaborate with business stakeholders and Analytics ...

Palantir Deployment Strategist information

See Decatur, GA salary details

$28.8K

$89.9K

$132.8K

How much do palantir deployment strategist jobs pay per year?

As of Jul 28, 2026, the average yearly pay for palantir deployment strategist in Decatur, GA is $89,945.00, according to ZipRecruiter salary data. Most workers in this role earn between $80,100.00 and $92,300.00 per year, depending on experience, location, and employer.

What are some common challenges Palantir Deployment Strategists face when implementing solutions for clients?

Palantir Deployment Strategists often encounter challenges such as navigating complex organizational structures, aligning diverse stakeholder interests, and adapting technical solutions to unique client environments. They must balance understanding the client's business needs with the technical capabilities of Palantir's platforms, often requiring strong communication and problem-solving skills. Additionally, Deployment Strategists frequently work in fast-paced settings where priorities can shift quickly, making adaptability and proactive project management crucial for success.

What is a Palantir Deployment Strategist?

A Palantir Deployment Strategist is a professional who works at Palantir Technologies to bridge the gap between technology and business problems. They partner with clients to understand their unique challenges and design data-driven solutions using Palantir's software platforms. Deployment Strategists are responsible for gathering requirements, integrating data, configuring software, and ensuring the successful implementation of Palantir products to deliver value to clients. They often work onsite with clients and collaborate closely with engineers, data scientists, and business stakeholders.

What are the key skills and qualifications needed to thrive as a Palantir Deployment Strategist, and why are they important?

To thrive as a Palantir Deployment Strategist, you need a strong analytical background, problem-solving skills, and experience with data-driven decision-making, often supported by a degree in a technical or quantitative field. Familiarity with data integration tools, enterprise software platforms, and sometimes programming languages like Python or SQL is advantageous. Exceptional communication, stakeholder management, and adaptability distinguish top performers in this client-facing, fast-paced environment. These skills are crucial for bridging technical solutions with business needs, ensuring successful software deployment and client satisfaction.

What is the difference between Palantir Deployment Strategist vs Data Analyst?

AspectPalantir Deployment StrategistData Analyst
Required CredentialsRelevant technical background, often with experience in data integration and software deploymentDegree in statistics, mathematics, or related field; proficiency in data analysis tools
Work EnvironmentCollaborates with technical teams and clients to deploy Palantir solutionsAnalyzes data sets to generate insights, often within corporate or research settings
Employer & Industry UsagePrimarily in tech, government, and consulting firms using Palantir platformsAcross various industries including finance, healthcare, and marketing

The Palantir Deployment Strategist focuses on deploying Palantir software solutions and working closely with clients to implement data systems. In contrast, a Data Analyst primarily interprets data to inform business decisions. While both roles require analytical skills, the Deployment Strategist emphasizes technical deployment and client interaction, whereas the Data Analyst centers on data interpretation and reporting.

What job categories do people searching Palantir Deployment Strategist jobs in Decatur, GA look for? The top searched job categories for Palantir Deployment Strategist jobs in Decatur, GA are:
What cities near Decatur, GA are hiring for Palantir Deployment Strategist jobs? Cities near Decatur, GA with the most Palantir Deployment Strategist job openings:
Infographic showing various Palantir Deployment Strategist job openings in Decatur, GA as of July 2026, with employment types broken down into 92% Full Time, 5% Part Time, and 3% Contract. Highlights an 86% Physical, 4% Hybrid, and 10% Remote job distribution, with an average salary of $89,945 per year, or $43.2 per hour.

Full-time

Posted 10 days ago


Job description

AURIS AI | PLATFORM ENGINEERING 

Platform Engineer - Palantir 

Hands-On Builder, Cost Steward & Component Curator 

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

Cost & Resource Optimization 

  • Own end-to-end FinOps 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. 

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. 

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

  • Maintain platform standards documentation 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. 

  • Working proficiency across 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 and maintaining shared component libraries, internal developer platforms, or reusable pattern catalogs. 

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

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

Platform Operations & FinOps 

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

  • Strong FinOps fundamentals — usage forecasting, compute and 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 audiences require. 

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, and risk tradeoffs 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, component specifications, and platform standards. 

Experience 

  • 5–10+ years of experience operating, 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. 

  • Prior experience in insurance, financial services, or similarly regulated industries is a strong plus. 

  • Bachelor's or Master's degree in Computer Science, Engineering, or related technical field. 

  • Optional: Bachelor's or Master's degree in Business, Finance, or related business field. 

Success Metrics / KPIs 

Metric & Indicator of Success 

Admin Request SLA Adherence 

% of access, provisioning, ingress/egress, and configuration requests fulfilled within committed turnaround targets 

Cost Efficiency 

Compute, storage, and licensing cost per active use case trending favorably quarter-over-quarter 

Permissions Hygiene 

% of projects, groups, and markings in compliance with least-privilege standards; reduction in audit findings 

Ingress / Egress Posture 

Zero unauthorized data movement events; 100% of inbound and outbound data flows mapped, classified, and approved 

Component Catalog Adoption 

# of reusable components in the catalog and % of new use cases consuming ≥1 cataloged component 

Platform Team Throughput 

Platform Engineering velocity against capacity plan; reduction in cross-pod escalations and repeat requests