Data Architect-1994 at PIP Global Safety
Latham
—
Jul 5, 2026
Latham
Jul 20, 2026
What this job asks for AI summary
This role centers on making enterprise data consumable by AI agents, copilots, and intelligent automation systems, primarily across an Azure data platform and Palantir Foundry environment. The work spans designing data architecture patterns for AI use cases such as retrieval-augmented generation and agentic workflows, owning semantic models and data contracts, and establishing governance guardrails aligned with regulatory standards. It suits an architect with a background spanning data engineering, enterprise architecture, and AI/ML enablement.
Senior level · National
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $142,568 (middle half $111,775–$173,013).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
The posting carries no title-level seniority modifier ('Senior', 'Staff', etc.), so advertised seniority is Unspecified. The scope — owning enterprise semantic models, defining cross-platform standards, partnering with Security/Legal/Compliance, and contributing to a platform roadmap — supports a Senior band.
SOC classification is Medium confidence. The role is primarily a data/enterprise architect designing AI-ready data platforms (pipelines, ontologies, semantic layers, data contracts), which maps best to 15-1243 Database Architects. However, the heavy AI enablement and agentic AI framing could also fit 15-1299 (Computer Occupations, All Other), listed as the runner-up.
No experience floor, degree requirement, compensation, or employment type is stated anywhere in the posting.
Compliance frameworks (GDPR, CCPA, SOX) and RBAC appear in a governance/guardrails section describing partner responsibilities rather than as hard candidate gates; treated as preferred context skills.
LLMs and agentic AI concepts are referenced as the target consumption layer the architect enables, not as a hard technical skill the candidate must personally possess; treated as preferred.
Ignored 3 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): data governance, semantic modeling, role-based access control.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.