{"schemaVersion":"jobsearcher.job.v1","id":"ee4691cc49b100f2ca0fad4e","url":"https://jobsearcher.com/jobs/ee4691cc49b100f2ca0fad4e","canonicalUrl":"https://jobsearcher.com/jobs/ee4691cc49b100f2ca0fad4e","title":"Remote Laboratory Data Ontologist (Remote)","description":"Laboratory Data OntologistRemote | Canada or USOverviewWe are seeking a Laboratory Data Ontologist to strengthen the semantic foundation of our platform and the client-specific ontologies deployed on top of it. Labbit is built on a typed entity graph — samples, containers, locations, instruments, pools, and their provenance — and every implementation is, at its core, a modelling exercise: mapping a client's scientific and operational vocabulary onto that graph without losing fidelity.This role sits within our Advisory group. You will spend ~50% of your time billable on client implementation projects as the modelling lead, and the remaining ~50% on internal stewardship — evolving the core ontology, codifying modelling practice, and supporting Sales pursuits. This is not a data engineer role and not a solutions architect role. You are a modeller — steeped in information theory, taxonomy design, and ontology engineering — whose primary deliverables are client and platform ontologies, reference models, and the standards that govern them.Why This Role MattersOur platform's differentiator is a configurable, versioned entity graph with immutable lineage. That model is only as valuable as the discipline behind it:Advisory engagements deepen when modelling is treated as a first-class deliverable rather than a byproduct of configuration.Sales wins when we can quickly show a prospect their world represented cleanly in our model.Implementation delivers faster when client vocabulary maps to reusable patterns instead of bespoke types.Platform evolves coherently when extensions across clients are legible as variants of shared abstractions rather than divergent one-offs.Housing this role in Advisory keeps the practitioner close to real client problems — the billable work is where modelling craft is sharpened — while the non-billable half compounds those learnings into shared assets the whole company draws on.What You Will Do1. Lead Modelling on Client Engagements (~50% billable)Serve as the modelling lead on Advisory and Implementation engagements where ontology depth is the critical riskRun discovery sessions to elicit and structure client domain modelsProduce target ontologies — entity types, controlled vocabularies, field taxonomies, workflow decompositions — as billable deliverablesReview changeset designs for modelling quality alongside implementation engineersCoach client counterparts on stewardship of their own model post go-live2. Steward the Core OntologyOwn the conceptual model behind Labbit's base entity types (@Sample, @Container, @Location, @Instrument, @Reagent, @Pool) and their inheritance semanticsMaintain design principles for when to extend a base type vs. introduce a new oneReview proposed changes to the base ontology for coherence, minimalism, and long-term extensibilityCurate the shared reference/IRI namespace so aliases remain meaningful across changesets and clients3. Codify Modelling Practice Across AdvisoryAuthor internal standards for taxonomy design, controlled vocabulary governance, and ontology versioningIdentify reusable extension patterns across client engagements and promote them into shared librariesEstablish review rituals so modelling decisions are traceable and reversibleTrain Advisory and Implementation staff in applied ontology techniquesBuild a shared library of domain reference models for our priority verticals (QC manufacturing, clinical genomics, CGT, stability)4. Support SalesJoin late-stage sales cycles to lead ontology discovery sessions with prospectsProduce lightweight target models that demonstrate fit without over-committing to configurationTranslate prospect terminology (assays, panels, batches, lots) into our model in real time during demos5. Inform Platform DirectionSurface modelling gaps discovered across client work as candidate platform investmentsAdvise Platform Engineering on schema evolution semantics (changeset migrations, deprecations, aliasing)Contribute to decisions about first-class vs. reference-data entities, computed fields, and graph traversal featuresWhat You Will Not DoOwn application development or feature deliveryServe as project manager or delivery lead on client engagementsReplace implementation configuration engineers or platform engineersBuild a parallel modelling framework outside our changeset systemQualificationsStrong grounding in information theory, formal ontology, or knowledge representation (academic or applied)5+ years working with structured domain models — taxonomies, controlled vocabularies, ontologies, or graph schemas — in production settingsFluency with at least one modelling formalism (OWL/RDF, property graphs, UML class models, ISA-Tab, or comparable)Demonstrated ability to elicit domain knowledge from subject-matter experts and translate it into a coherent modelComfort in a client-facing, billable advisory context — including scoping deliverables, running workshops, and defending modelling decisions to technical and non-technical stakeholdersComfort reading and reasoning about configuration-as-code artifacts (JSON schemas, BPMN, expression languages)Excellent written communication — you will produce reference models, standards, and documentation that others rely onStrongly PreferredExperience in laboratory informatics, life sciences, or another regulated scientific domain (QC manufacturing, genomics, clinical diagnostics, CGT)Familiarity with LIMS, ELN, or scientific workflow platforms and their data modelsExperience with versioned schema evolution and immutable/provenance data modelsExposure to regulated environments (21 CFR Part 11, GAMP5) and their implications for schema governancePrior consulting or professional services experience with utilization targetsTo further support our team, we offer the following benefits:Competitive vacation Flexible health spending account / Health InsuranceRRSP / 401 K matching Annual professional development budgetThe expected salary range for this role is: $150,000 - $190,000 CAD or USDActual compensation may vary based on experience, domain expertise, and geographic location.","company":"Semaphore Solutions","rawCompany":"semaphore solutions","city":"Greeley","state":"CO","isRemote":true,"isActive":false,"createdAt":"2026-09-16T05:38:29.289Z","occupations":[{"code":"15-2051.00","title":"Data Scientists","slug":"data-scientists"},{"code":"15-1243.01","title":"Data Warehousing Specialists","slug":"data-warehousing-specialists"},{"code":"15-1211.00","title":"Computer Systems Analysts","slug":"computer-systems-analysts"}],"industries":[{"code":"541690","title":"Other Scientific and Technical Consulting Services","slug":"other-scientific-and-technical-consulting-services"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Remote Laboratory Data Ontologist (Remote)","description":"Laboratory Data OntologistRemote | Canada or USOverviewWe are seeking a Laboratory Data Ontologist to strengthen the semantic foundation of our platform and the client-specific ontologies deployed on top of it. Labbit is built on a typed entity graph — samples, containers, locations, instruments, pools, and their provenance — and every implementation is, at its core, a modelling exercise: mapping a client's scientific and operational vocabulary onto that graph without losing fidelity.This role sits within our Advisory group. You will spend ~50% of your time billable on client implementation projects as the modelling lead, and the remaining ~50% on internal stewardship — evolving the core ontology, codifying modelling practice, and supporting Sales pursuits. This is not a data engineer role and not a solutions architect role. You are a modeller — steeped in information theory, taxonomy design, and ontology engineering — whose primary deliverables are client and platform ontologies, reference models, and the standards that govern them.Why This Role MattersOur platform's differentiator is a configurable, versioned entity graph with immutable lineage. That model is only as valuable as the discipline behind it:Advisory engagements deepen when modelling is treated as a first-class deliverable rather than a byproduct of configuration.Sales wins when we can quickly show a prospect their world represented cleanly in our model.Implementation delivers faster when client vocabulary maps to reusable patterns instead of bespoke types.Platform evolves coherently when extensions across clients are legible as variants of shared abstractions rather than divergent one-offs.Housing this role in Advisory keeps the practitioner close to real client problems — the billable work is where modelling craft is sharpened — while the non-billable half compounds those learnings into shared assets the whole company draws on.What You Will Do1. Lead Modelling on Client Engagements (~50% billable)Serve as the modelling lead on Advisory and Implementation engagements where ontology depth is the critical riskRun discovery sessions to elicit and structure client domain modelsProduce target ontologies — entity types, controlled vocabularies, field taxonomies, workflow decompositions — as billable deliverablesReview changeset designs for modelling quality alongside implementation engineersCoach client counterparts on stewardship of their own model post go-live2. Steward the Core OntologyOwn the conceptual model behind Labbit's base entity types (@Sample, @Container, @Location, @Instrument, @Reagent, @Pool) and their inheritance semanticsMaintain design principles for when to extend a base type vs. introduce a new oneReview proposed changes to the base ontology for coherence, minimalism, and long-term extensibilityCurate the shared reference/IRI namespace so aliases remain meaningful across changesets and clients3. Codify Modelling Practice Across AdvisoryAuthor internal standards for taxonomy design, controlled vocabulary governance, and ontology versioningIdentify reusable extension patterns across client engagements and promote them into shared librariesEstablish review rituals so modelling decisions are traceable and reversibleTrain Advisory and Implementation staff in applied ontology techniquesBuild a shared library of domain reference models for our priority verticals (QC manufacturing, clinical genomics, CGT, stability)4. Support SalesJoin late-stage sales cycles to lead ontology discovery sessions with prospectsProduce lightweight target models that demonstrate fit without over-committing to configurationTranslate prospect terminology (assays, panels, batches, lots) into our model in real time during demos5. Inform Platform DirectionSurface modelling gaps discovered across client work as candidate platform investmentsAdvise Platform Engineering on schema evolution semantics (changeset migrations, deprecations, aliasing)Contribute to decisions about first-class vs. reference-data entities, computed fields, and graph traversal featuresWhat You Will Not DoOwn application development or feature deliveryServe as project manager or delivery lead on client engagementsReplace implementation configuration engineers or platform engineersBuild a parallel modelling framework outside our changeset systemQualificationsStrong grounding in information theory, formal ontology, or knowledge representation (academic or applied)5+ years working with structured domain models — taxonomies, controlled vocabularies, ontologies, or graph schemas — in production settingsFluency with at least one modelling formalism (OWL/RDF, property graphs, UML class models, ISA-Tab, or comparable)Demonstrated ability to elicit domain knowledge from subject-matter experts and translate it into a coherent modelComfort in a client-facing, billable advisory context — including scoping deliverables, running workshops, and defending modelling decisions to technical and non-technical stakeholdersComfort reading and reasoning about configuration-as-code artifacts (JSON schemas, BPMN, expression languages)Excellent written communication — you will produce reference models, standards, and documentation that others rely onStrongly PreferredExperience in laboratory informatics, life sciences, or another regulated scientific domain (QC manufacturing, genomics, clinical diagnostics, CGT)Familiarity with LIMS, ELN, or scientific workflow platforms and their data modelsExperience with versioned schema evolution and immutable/provenance data modelsExposure to regulated environments (21 CFR Part 11, GAMP5) and their implications for schema governancePrior consulting or professional services experience with utilization targetsTo further support our team, we offer the following benefits:Competitive vacation Flexible health spending account / Health InsuranceRRSP / 401 K matching Annual professional development budgetThe expected salary range for this role is: $150,000 - $190,000 CAD or USDActual compensation may vary based on experience, domain expertise, and geographic location.","datePosted":"2026-09-16T05:38:29.289Z","dateModified":"2026-09-16T05:38:29.289Z","hiringOrganization":{"@type":"Organization","name":"Semaphore Solutions","sameAs":"https://jobsearcher.com"},"jobLocationType":"TELECOMMUTE","applicantLocationRequirements":{"@type":"Country","name":"US"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Greeley","addressRegion":"CO","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"ee4691cc49b100f2ca0fad4e"},"url":"https://jobsearcher.com/jobs/ee4691cc49b100f2ca0fad4e"}}