Back to jobs

Data Modeler - Ontology

Pay
Pay not listed
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting

What you’ll work on

Full posting

We are looking for a hands-on Ontology / Knowledge Graph Engineer who understands not just graph databases, but the true semantic foundations behind enterprise knowledge graphs.

This is not a Cypher-only graph querying role.

  • Design and maintain insurance domain ontologies using OWL/RDF

  • Map source system fields from policy admin, claims, CRM and billing to ontology entities

  • Design and extend production knowledge graphs derived from ontologies

  • Document semantic models, maintain change logs, and drive ontology versioning

From the employer’s posting
We are looking for a hands-on Ontology / Knowledge Graph Engineer who understands not just graph databases, but the true semantic foundations behind enterprise knowledge graphs. This role requires experience in building domain ontologies, modeling conceptual semantics, and connecting those models to enterprise data sources.
This is not a Cypher-only graph querying role. This is a role for someone who has worked with OWL/RDF, domain modeling, and semantic standards—and can translate complex insurance concepts into a formal ontology that powers AI, LLMs, data governance, and enterprise knowledge systems.
Design, model, and maintain insurance domain ontologies using OWL/RDF.
Parse schemas from policy admin, claims, CRM, billing, and underwriting systems.
Design and extend production-grade knowledge graphs derived from ontologies.
Document semantic models, maintain change logs, and drive ontology versioning.
Apply at Fractal

Posting record

Report an error

Actively hiringFirst seen by us 1 day ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 3, 20261 day ago
Recorded sightings
2
Last seen by us
Nov 4, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 1

Early. Similar jobs usually come down between day 6 and day 47.

At Fractal, jobs usually come down by about day 38.

From 1,417 similar postings that came down, and 20 of Fractal’s. Coming down is not always a hire.

Fractal is hiring

30 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring is picking up
  • Takes jobs down at a usual pace
  • 3% of open jobs were reposted
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Azure
  • Kubernetes
  • Neo4j
Where the posting names them
- Ensure semantic alignment and consistency across diverse insurance systems. 4. Azure Cloud Integration - Deploy and operationalize ontology and KG components using:- Azure Data Lake / Storage
4. Azure Cloud Integration - Deploy and operationalize ontology and KG components using:- Azure Data Lake / Storage - Azure Purview / Microsoft Fabric Catalog
- Deploy and operationalize ontology and KG components using:- Azure Data Lake / Storage - Azure Purview / Microsoft Fabric Catalog - Azure Cognitive Search (for semantic indexing)
- Azure Purview / Microsoft Fabric Catalog - Azure Cognitive Search (for semantic indexing) - Azure Kubernetes Services / Azure Functions (for KG pipelines)
- Azure Cognitive Search (for semantic indexing) - Azure Kubernetes Services / Azure Functions (for KG pipelines) - Azure OpenAI (for semantic enrichment, RAG, and reasoning)
- Azure Kubernetes Services / Azure Functions (for KG pipelines) - Azure OpenAI (for semantic enrichment, RAG, and reasoning) - Integrate KG metadata into Azure metadata and lineage systems.
- Azure OpenAI (for semantic enrichment, RAG, and reasoning) - Integrate KG metadata into Azure metadata and lineage systems. 5. Collaboration & Governance
- Metadata grounding - Familiarity with Azure OpenAI or similar LLM orchestration frameworks. - Understanding of industry data standards such as ACORD.
- Ability to map enterprise source schemas to semantic models. - Experience with at least one semantic technology stack:- Stardog, GraphDB, Neo4j (with RDF frameworks), TopQuadrant, AllegroGraph, etc. Nice-to-Have Skills

Your next step

Complete your application on fractal.wd1.myworkdayjobs.com. The employer’s form will show what is required.

Applying through Workday

  • You create an account with each employer before you can upload anything. Every Workday employer has its own account, so one sign-up doesn’t carry over.
  • “Autofill with Resume” comes right after sign-in, before the My Information and My Experience steps. Check every field it fills in those steps, since that’s what recruiters see.
  • Your application status lives in that employer’s Candidate Home, under the same sign-in.

Already applied? Track this application

About the role

We file this job under Analytics Engineer, by the work the posting describes.

Analytics engineers turn raw warehouse data into clean, tested and documented tables that analysts and dashboards can rely on, often with dbt.

Expect strong SQL, data modeling, Git, and a warehouse such as Snowflake, BigQuery or Redshift.

A data engineer gets data into the warehouse; an analytics engineer shapes it once it is there and works closer to the analysts who use it.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for analytics engineers, so these figures are for the closest group, database architects, the same group we use for data engineers.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Job description

View original posting ↗

It's fun to work in a company where people truly BELIEVE in what they are doing!

We're committed to bringing passion and customer focus to the business.

Job Description

About the Role

We are looking for a hands-on Ontology / Knowledge Graph Engineer who understands not just graph databases, but the true semantic foundations behind enterprise knowledge graphs. This role requires experience in building domain ontologies, modeling conceptual semantics, and connecting those models to enterprise data sources.

This is not a Cypher-only graph querying role.
This is a role for someone who has worked with OWL/RDF, domain modeling, and semantic standards—and can translate complex insurance concepts into a formal ontology that powers AI, LLMs, data governance, and enterprise knowledge systems.

Key Responsibilities

1. Ontology Design & Semantic Modeling

  • Design, model, and maintain insurance domain ontologies using OWL/RDF.
  • Build conceptual and logical semantic models for entities such as:
    • Policies, Coverages, Perils, Claims, Loss Events, Parties, Risk Objects, Brokers/Agents.
  • Define canonical data definitions, taxonomies, hierarchical relationships, and semantic constraints.
  • Translate business domain models and regulatory structures into formal semantic structures.

2. Knowledge Graph Architecture

  • Design and extend production-grade knowledge graphs derived from ontologies.
  • Make design decisions on:
    • How the ontology becomes the semantic index for enterprise data.
    • How graph nodes point back to source systems through schema mapping.
    • How the KG will be used in RAG, LLM context grounding, or reasoning pipelines.
  • Implement ontology-driven schemas using RDF stores or labeled-property graph stores.

3. Source System Mapping

  • Parse schemas from policy admin, claims, CRM, billing, and underwriting systems.
  • Map source fields to ontology entities using:
    • Schema parsing
    • Semantic mapping
    • Transformation rules
  • Ensure semantic alignment and consistency across diverse insurance systems.

4. Azure Cloud Integration

  • Deploy and operationalize ontology and KG components using:
    • Azure Data Lake / Storage
    • Azure Purview / Microsoft Fabric Catalog
    • Azure Cognitive Search (for semantic indexing)
    • Azure Kubernetes Services / Azure Functions (for KG pipelines)
    • Azure OpenAI (for semantic enrichment, RAG, and reasoning)
  • Integrate KG metadata into Azure metadata and lineage systems.

5. Collaboration & Governance

  • Work closely with:
    • Underwriting SMEs
    • Claims SMEs
    • Data governance teams
    • Data engineering teams
    • AI/ML product teams
  • Document semantic models, maintain change logs, and drive ontology versioning.

Required Skills (Non-Negotiable)

  • Hands-on experience in ontology development, not just graph querying.
  • Strong knowledge of:
    • OWL, RDF, RDFS, SKOS
    • SPARQL, SHACL (preferred)
  • Experience designing conceptual and logical domain models.
  • Demonstrated ability to build a knowledge graph from scratch, not just use one.
  • Strong insurance domain understanding:
    • Policy structures
    • Exposure / risk modeling fundamentals
    • Claims life cycle
    • Product hierarchies
    • Regulatory constraints
  • Ability to map enterprise source schemas to semantic models.
  • Experience with at least one semantic technology stack:
    • Stardog, GraphDB, Neo4j (with RDF frameworks), TopQuadrant, AllegroGraph, etc.

Nice-to-Have Skills

  • Experience building LLM-integrated semantic pipelines:
    • Context engineering
    • RAG indexing
    • Metadata grounding
  • Familiarity with Azure OpenAI or similar LLM orchestration frameworks.
  • Understanding of industry data standards such as ACORD.

Soft Skills

  • Strong analytical and conceptual modeling skills.
  • Ability to challenge assumptions and define canonical definitions.
  • Ability to communicate with business SMEs and translate domain knowledge into ontology structures.
  • Structured documentation and versioning discipline.

Why This Role Matters

This role is foundational to:

  • Enterprise LLM adoption
  • Semantic search
  • Knowledge-driven underwriting & claims workflows
  • Data governance
  • AI safety & consistency
  • Eliminating redundant and fragmented data definitions across systems

If you like wild growth and working with happy, enthusiastic over-achievers, you'll enjoy your career with us!

Not the right fit?  Let us know you're interested in a future opportunity by clicking Introduce Yourself in the top-right corner of the page or create an account to set up email alerts as new job postings become available that meet your interest!

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Bengaluru

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.