Ontology Engineer

Designs and builds the OntoSphere KG — the canonical model that fuses SOPIA, ISO 20022, FIBO, PROV-O, and Client PayOps ontologies. Front-loaded role: most intensive in P0-P1 during ontology consensus, then transitions to consult/maintenance through hyper-care. Ontology design choices made here are very expensive to change later.MUST-HAVE SKILLS (GO/NO-GO)#SkillYears RequiredSpecific Context / ToolsKnowledge Graph databasesNeo4j, Stardog, Graph DB, AWS Neptune, or Apache JenaSPARQLComplex queries, federated queries, optimizationRDF / OWLOntology modeling, OWL reasoning, named graphsSHACLConstraint validation, shape design, error reportingPython OR JavaKG integration code; rdflib, owlready2, or Apache JenaBanking ontologies (or willingness)FIBO, ISO 20022, FRO, or rapid learning track-recordSchema / domain modelingProperty graphs vs RDF tradeoffs; domain-driven designOntology engineering processTop-down vs bottom-up; competency questions; iterationNICE-TO-HAVE SKILLS (differentiators)• Wikidata / DBpedia experience• Ontology alignment / mapping (LIMES, Silk)• PROV-O provenance modeling for audit trails• Reasoning engines (Pellet, HermiT, ELK)• Property graph (Cypher / Gremlin) experience• Apache Jena Fuseki or Graph DB Workbench• RDF* / RDF-star for statement-level metadata• KG embeddings (TransE, ComplEx, RGCN)CERTIFICATIONS• OMG Certified Expert in BPM (CEBPM) — for FIBO depth• Stardog certificationsSOFT SKILLS (interview-validated)• Patient with stakeholder ontology debates (consensus is slow)• Strong communicator with non-technical SMEs• Iterative ontology evolution mindset (not big-design-up-front)• Documentation discipline — ontologies live or die by docs