Principal Ontology Architect (Healthcare)

Virtasant is hiring a Principal Ontology Architect (Healthcare) for a remote role open to applicants in United States. Level rates it ; you can apply on Virtasant.

Level's read on this job

Little AI ●○○○ is how Level rates this role: aI is not part of the work.
The posting lists this role as remote.
Level classifies it as a lead role.
Level lists 16 other open roles at Virtasant.
The role was posted in the last few days.

AI in this role

About Virtasant

Virtasant is a global technology services company with a network of over 4,000 technology professionals across 130+ countries. We specialize in cloud architecture, infrastructure, migration, and optimization, helping enterprises scale efficiently while maintaining cost control.

Our clients range from Fortune 500 companies to fast-growing startups, relying on us to build high-performance infrastructure, optimize cloud environments, and enable continuous delivery at scale.

About the role

We are building a senior team for a large enterprise program in healthcare operations. The program uses ontology and knowledge-graph design to help executives make operational decisions, act on them, and measure the results.

We need a senior ontology lead who has done this before and can show it. You will work directly with senior client stakeholders, share real experience of ontologies you have designed and delivered, and then lead the ontology and semantic design.

Engagement

*Immediate start, part-time for the first few weeks.

*Expected to move to full time on a multi-year engagement.

*Contractor. US-based with US work authorization. Occasional US travel

What We’re Looking For

Must-Have Experience

*You have designed and shipped production ontologies that drove real decisions, not just taxonomies or metadata catalogs.

*You can talk through two or three of them: the business problem, the model, what went wrong and what you would do differently.

*Business-first modeling. You start from the questions executives ask and the metrics they run on, run workshops with domain experts, and only then turn that into a technical model.

*Hands-on graph modeling with a property-graph or RDF database. You know when a graph earns its place and when it doesn't, and you can make that case to a skeptical architect.

*Healthcare operations experience, for example, workforce, scheduling, or clinical operations.

*Senior presence. You have presented to C-level stakeholders and are comfortable being challenged live.

*Available immediately.

Strong Plus

*Palantir Foundry Ontology (objects, links, actions).

*Ontology governance: versioning, change control, stable identifiers, a shared core with per-client extensions.

*Decision-intelligence modeling: KPI trees, root-cause analysis, recommendations, and closed-loop measurement of predicted against actual outcomes.

*Grounding AI assistants or agents in an ontology or knowledge graph.

*Rules engines alongside an ontology.

*Modern cloud data platforms.

Not a Fit

*Mainly academic semantic-web work with no production delivery.

*Data engineers or BI developers who have worked near an ontology but never owned one

How we rate this

Principal Ontology Architect (Healthcare) at Virtasant rates 19 out of 100 for how much of the daily work is AI. That makes it Little AI (AI Level 1 of 4). The level is about AI in the job, not seniority.

Classification

Little AI. AI is not part of the work.

●●●● Builds AI80 to 100
●●●○ Works on AI60 to 79
●●○○ Uses AI40 to 59
●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.