Data Architect

Role Summary
We are looking for an Ontology Data Architect to lead the design, evolution, and
operationalisation of our enterprise ontology on the Palantir platform.
This role sits at the intersection of business domain knowledge, data engineering, and
product delivery. You will shape how real-world operational concepts are represented
digitally and ensure the ontology directly enables high-value user journeys, applications,
and automation.
This is not a theoretical modeling role. Success is measured by adoption, reuse, and
business impact.

What You’ll Do
Ontology Design & Evolution

• Design, own, and evolve a business-driven ontology that represents real
operational processes, assets, events, and relationships.

• Ensure ontology development is validated through active use in applications,
analytics, and workflows.

• Balance semantic rigor with pragmatism — evolving iteratively based on real use
cases.
Product & Platform Collaboration

• Work embedded with product teams to co-design ontology elements that support
specific user journeys.

• Partner with the platform team to shape reusable ontology patterns into shared
platform assets.

• Ensure product-driven contributions are hardened, standardized, and made
reusable across the enterprise.
Domain Translation

• Translate domain expert knowledge (often implicit and local) into clear,
maintainable ontology structures.

• Facilitate lightweight workshops with SMEs to capture meaning without
overburdening them.

• Resolve ambiguity and inconsistency across sites, systems, and teams.
Data & Platform Integration

• Collaborate with data engineers to ensure data pipelines align with ontology
semantics.

• Guide how raw data is mapped, enriched, and contextualized within the ontology.

• Influence data quality, lineage, and governance through semantic design rather than
bureaucracy.
Governance & Enablement

• Define principles, patterns, and guardrails for ontology usage and extension.

• Coach product teams on how to use and extend the ontology safely.

• Act as a steward — enabling speed without sacrificing coherence.

What We’re Looking For
Required Experience

• Strong experience in data modeling, semantic modeling, or ontology design in
complex domains.

• Hands-on experience working with Palantir Foundry ontologies or equivalent
semantic platforms.

• Proven ability to work closely with business users and product teams, not just
engineers.

• Experience operating in iterative, product-led environments rather than big
- upfront design.

Domain & Mindset

• Comfortable navigating messy, real-world operational concepts.

• Able to challenge abstract or “perfect” models in favor of what actually delivers
value.

• Product mindset: you think in terms of users, outcomes, and adoption.
Nice to Have

• Experience in industrial, asset-intensive, or operations-heavy environments.

• Background in data engineering, analytics, or platform teams.

• Familiarity with governance, metadata, or data catalog concepts — without being
dogmatic.

How You’ll Be Measured

• Ontology elements are actively used in applications and workflows.

• Product teams can build faster because shared semantic foundations already exist.

• Reduced duplication and inconsistency across data and applications.

• Clear lineage from business questions → ontology → data → action.