AI/ML Data Knowledge Graph Engineer at Sapience AI Corporation
United States
$204k - $216k
<p><span style="font-size: 12pt;">Sapience AI is the collective intelligence platform for professional communities. We sit above the CRMs, AMS platforms, and knowledge bases that organizations already run, and we turn the expertise scattered across them into something every member can search, act on, and share.</span></p> <p><span style="font-size: 12pt;">The intelligence a community needs is already inside it. Most organizations just cannot reach it. Knowledge lives in silos, in legacy systems, in the heads of a few experts, and in fragmented records no one can connect. We change that.</span></p> <p><span style="font-size: 12pt;">Our work is grounded in four commitments: technology elevates people and never replaces them, the best expertise is already inside the community, everything is built on trust, and every deployment is purpose-driven for the organization it serves.</span></p> <p><span style="font-size: 12pt;"><strong>Let’s achieve more, together.</strong></span></p> <h1><span style="font-size: 14pt;"><strong>Where this role sits</strong></span></h1> <p><span style="font-size: 12pt;">This role builds the structured knowledge that collective intelligence reasons over. You own the KO (knowledge object) graph: the layer that turns a community’s scattered expertise into connected, queryable knowledge the COGENT architecture can use.</span></p> <p><span style="font-size: 12pt;">You work where messy real-world data becomes trustworthy structure: ingesting, resolving, connecting, and modeling knowledge so reasoning has something solid to stand on.</span></p> <p><span style="font-size: 12pt;">You partner closely with neuro-symbolic AI and applied AI, and you are the reason the platform can answer questions that span a community’s knowledge instead of isolated documents.</span></p> <h1><span style="font-size: 14pt;"><strong>Why this role exists</strong></span></h1> <p><span style="font-size: 12pt;">Language models are fluent, but fluency is not knowledge. To reason over a community’s expertise with rigor, the platform needs that expertise structured, connected, and trustworthy, not just retrieved as text.</span></p> <p><span style="font-size: 12pt;">Building a knowledge graph from real, fragmented sources is hard: entities to resolve, relationships to infer, quality to enforce, and provenance to preserve. The graph is only as good as the engineering behind it.</span></p> <p><span style="font-size: 12pt;">The AI/ML Data and KO Graph Engineer builds that foundation. You turn scattered knowledge into a graph the COGENT architecture can reason over, so members get answers grounded in their community’s real expertise.</span></p> <h1><span style="font-size: 14pt;"><strong>What you will own (Areas of Responsibility)</strong></span></h1> <p><span style="font-size: 12pt;">You hold seven areas of responsibility across the knowledge layer. Each one is yours to set direction on, build, and measure.</span></p> <h2><span style="font-size: 12pt;"><strong>1. Knowledge graph engineering</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Build and maintain the KO graph that structures a community’s knowledge for reasoning.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Design schemas, ontologies, and relationships that reflect how expertise actually connects.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Make the graph queryable, performant, and reliable at scale.</span></li> </ul> <h2><span style="font-size: 12pt;"><strong>2. Ingestion and knowledge extraction</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Build pipelines that extract knowledge from documents, systems, and community sources into the graph.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Turn unstructured and semi-structured content into structured knowledge objects.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Keep the graph current as a community’s knowledge changes.</span></li> </ul> <h2><span style="font-size: 12pt;"><strong>3. Entity resolution and quality</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Resolve entities, deduplicate, and connect knowledge across fragmented sources.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Enforce quality so members can trust what the graph tells them.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Detect and handle conflicts and gaps in the knowledge.</span></li> </ul> <h2><span style="font-size: 12pt;"><strong>4. Provenance and trust</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Preserve provenance so every piece of knowledge can be traced to its source.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Build the structure that lets the platform show its work and earn member trust.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Protect sensitive community knowledge with correct access and governance.</span></li> </ul> <h2><span style="font-size: 12pt;"><strong>5. Serving knowledge to COGENT</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Partner with neuro-symbolic and applied AI to serve the graph into reasoning and retrieval.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Shape the graph so it supports both symbolic reasoning and neural retrieval.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Make knowledge access fast enough for production answers.</span></li> </ul> <h2><span style="font-size: 12pt;"><strong>6. Data pipelines and platform</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Build the data pipelines and platform the knowledge layer depends on.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Instrument the pipelines so quality and freshness can be measured.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Turn recurring ingestion needs into reusable connectors.</span></li> </ul> <h2><span style="font-size: 12pt;"><strong>7. Evaluation of knowledge quality</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Measure the quality, coverage, and freshness of the graph against what communities need.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Build the evaluation that tells whether the knowledge layer is improving.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Use evidence to steer where to invest next.</span></li> </ul> <h1><span style="font-size: 14pt;"><strong>AI-augmented ways of working</strong></span></h1> <p><span style="font-size: 12pt;">You use AI to build the knowledge layer, from extraction and entity resolution to schema suggestions, while you own the correctness, structure, and trustworthiness of the graph.</span></p> <p><span style="font-size: 12pt;">The standard is human in partnership: AI accelerates the work, you own the judgment, the interpretation, and the call. The people who create the most value here are not the ones producing the most output. They are the ones turning evidence into clear, durable decisions.</span></p> <h1><span style="font-size: 14pt;"><strong>What this role is not</strong></span></h1> <p><span style="font-size: 12pt;">To keep the boundary clear:</span></p> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>This is not a reasoning-architecture role. </strong>You build the graph the COGENT architecture reasons over; neuro-symbolic AI owns the reasoning.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>This is not a general analytics role. </strong>You engineer a production knowledge graph, not dashboards and reports.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>This is not an ingestion-only role. </strong>You own structure, quality, provenance, and how knowledge serves reasoning.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>This is not a best-effort role. </strong>The graph is a production foundation members’ trust depends on.</span></li> </ul> <h1><span style="font-size: 14pt;"><strong>What success looks like</strong></span></h1> <p><span style="font-size: 12pt;">We measure this role on outcomes the team can see:</span></p> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>Connected knowledge. </strong>A community’s scattered expertise becomes a connected, queryable graph.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>Trustworthy answers. </strong>Quality and provenance let members trust and trace what the platform tells them.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>Fresh and current. </strong>The graph keeps pace with a community’s changing knowledge.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>Reasoning-ready. </strong>The graph serves both symbolic reasoning and neural retrieval well.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>Reusable ingestion. </strong>New sources come online faster because ingestion is reusable.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;"><strong>Measured quality. </strong>Coverage, quality, and freshness are measured and improving.</span></li> </ul> <h1><span style="font-size: 14pt;"><strong>Who you are</strong></span></h1> <h2><span style="font-size: 12pt;"><strong>Required qualifications</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Five or more years in data engineering, knowledge graph engineering, or a related field.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Hands-on experience building and operating knowledge graphs or graph databases.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Strong data pipeline engineering, including ingestion and transformation.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Experience with entity resolution, deduplication, and data quality.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Solid grounding in knowledge representation, ontologies, or schema design.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Strong Python and SQL, plus graph query languages.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Care for provenance, trust, and protection of sensitive data.</span></li> </ul> <h2><em><span style="font-size: 12pt;"><strong>Preferred qualifications</strong></span></em></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Experience serving graphs into retrieval or reasoning systems.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Familiarity with neuro-symbolic AI and how structure supports reasoning.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Experience with embeddings, vector search, and hybrid retrieval.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Experience integrating CRM, AMS, or knowledge-base sources.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Domain understanding of knowledge-intensive or professional communities.</span></li> </ul> <h2><span style="font-size: 12pt;"><strong>How you work</strong></span></h2> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">You name the real problem in the data before reaching for a structure.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">You care about quality, provenance, and trust as much as coverage.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">You build pipelines others can run and extend.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">You measure the knowledge layer honestly.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">You share reusable connectors and patterns.</span></li> </ul> <h1><span style="font-size: 14pt;"><strong>Skills & Competencies</strong></span></h1> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Knowledge graph and ontology engineering.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Ingestion, extraction, and transformation pipelines.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Entity resolution, deduplication, and data quality.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Provenance, governance, and protection of sensitive knowledge.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Serving graphs into retrieval and reasoning.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Evaluation of knowledge quality and coverage.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Turning recurring ingestion into reusable capability.</span></li> </ul> <h1><span style="font-size: 14pt;"><strong>Services & Tools Experience</strong></span></h1> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Graph databases (for example Neo4j-class systems) and graph query languages (Cypher, SPARQL, or GQL).</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Data pipeline and orchestration tools.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Entity resolution and data-quality tooling.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Vector databases and embedding models for hybrid retrieval.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Python and SQL as primary languages.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Cloud data platforms and storage.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Building and serving the KO graph into the COGENT architecture and MINERVA.</span></li> </ul> <h1><span style="font-size: 14pt;"><strong>Prior Experience & Background</strong></span></h1> <ul> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Prior data or knowledge graph engineering at a software or AI company.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Experience building knowledge structures from messy, real-world sources.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">A track record of production data systems with quality and provenance.</span></li> <li style="font-size: 12pt;"><span style="font-size: 12pt;">Experience supporting reasoning or retrieval systems is a plus.</span></li> </ul> <h1><span style="font-size: 14pt;"><strong>Cross-functional partners</strong></span></h1> <p><span style="font-size: 12pt;">You work most closely with Neuro-Symbolic AI, Applied AI, Data Engineering, and Platform Engineering. You build the KO graph that the COGENT architecture reasons over inside MINERVA.</span></p> <h1><span style="font-size: 14pt;"><strong>How we hire</strong></span></h1> <p><span style="font-size: 12pt;">We review every application, and we encourage you to apply even if you do not match every line above. Research shows that talented people, especially those from underrepresented communities, often hold back when they do not meet every qualification. If that is the only thing holding you back, apply anyway.</span></p> <p><span style="font-size: 12pt;">Sapience AI is an equal opportunity employer. We are committed to a workplace where everyone, regardless of background, has a voice in building what comes next.</span></p> <h1><span style="font-size: 14pt;"><strong>Compensation</strong></span></h1> <p><span style="font-size: 12pt;">Base Salary: $204,000 - $216,000 + early stage equity</span></p> <p><span style="font-size: 12pt;">Generous health and wellness benefits</span></p> <p> </p> <p><span style="font-size: 12pt;"><em>Sapience AI is an equal opportunity employer. We do not discriminate on the basis of gender, race or color, ethnicity or national origin, age, disability, religion, sexual orientation, gender identity or expression, veteran status, or any other protected characteristic. If you need an accommodation to complete our application process, let your recruiter know.</em></span></p>
Apply Now