1

Contract Knowledge Graph Jobs in Washington (NOW HIRING)

Neo4J Developer

Rockville, MD ยท On-site

$53.50 - $69/hr

MD - 100% Remote Duration: Long Term Contract Client is seeking a talented, energetic, ambitious ... Query Languages for Property-Graph or Knowledge-Graph, NoSQL, and Relational databases e.g. Gremlin ...

We define competency questions as the contract for what a system must be able to answer, design ... Experience with knowledge graph platforms or graph databases * Experience in client-facing roles ...

Senior Level Systems Integrator

Chantilly, VA ยท On-site

$135K - $216K/yr

Knowledge of graph data science (GDS) and knowledge graph applications supporting AI/ML or MBSE ... and contract considerations. Depending on the position, employees may be eligible for overtime ...

Senior Level Systems Integrator

Springfield, VA ยท On-site

$135K - $216K/yr

Knowledge of graph data science (GDS) and knowledge graph applications supporting AI/ML or MBSE ... and contract considerations. Depending on the position, employees may be eligible for overtime ...

Senior Level Systems Integrator

Chantilly, VA ยท On-site

$135K - $216K/yr

Knowledge of graph data science (GDS) and knowledge graph applications supporting AI/ML or MBSE ... and contract considerations. Depending on the position, employees may be eligible for overtime ...

Senior Level Systems Integrator

Springfield, VA ยท On-site

$135K - $216K/yr

Knowledge of graph data science (GDS) and knowledge graph applications supporting AI/ML or MBSE ... and contract considerations. Depending on the position, employees may be eligible for overtime ...

Senior Level Systems Integrator

Chantilly, VA ยท On-site

$135K - $216K/yr

Knowledge of graph data science (GDS) and knowledge graph applications supporting AI/ML or MBSE ... and contract considerations. Depending on the position, employees may be eligible for overtime ...

next page

Showing results 1-20

Contract Knowledge Graph information

How does a Contract Knowledge Graph specialist typically collaborate with legal and IT teams during implementation projects?

A Contract Knowledge Graph specialist often works closely with legal teams to understand contract structures, key clauses, and compliance requirements, ensuring that the graph accurately represents legal relationships and obligations. Simultaneously, they partner with IT and data teams to integrate data sources, design the graph schema, and implement technical solutions. Effective collaboration requires clear communication, regular meetings, and the ability to translate legal concepts into technical requirements, which helps ensure the knowledge graph delivers actionable insights for both legal and business stakeholders.

What are the key skills and qualifications needed to thrive as a Contract Knowledge Graph Specialist, and why are they important?

To excel as a Contract Knowledge Graph Specialist, you need expertise in semantic data modeling, contract analysis, and a background in computer science or information management. Familiarity with tools like Neo4j, RDF, SPARQL, and experience with natural language processing (NLP) solutions are typically required. Strong analytical thinking, attention to detail, and effective communication skills help translate complex contract terms into structured, actionable data. These competencies ensure accurate, scalable contract data representation, enabling better compliance, searchability, and automation for organizations.

What is the difference between Contract Knowledge Graph vs Contract Analyst?

AspectContract Knowledge GraphContract Analyst
Required CredentialsTypically a background in data science, knowledge graphs, or related fieldsUsually a degree in law, business, or finance
Work EnvironmentData-driven, often in tech or AI-focused teamsLegal, finance, or corporate departments
Employer & Industry UsageTech companies, AI firms, legal techCorporations, law firms, government agencies
Common Search & Comparison IntentUnderstanding data modeling and AI applications in contractsAnalyzing contract terms and compliance

The Contract Knowledge Graph focuses on creating structured, interconnected data models for contracts using AI and data science skills. In contrast, a Contract Analyst primarily reviews, interprets, and manages contract data within legal or business contexts. While both roles deal with contracts, the Knowledge Graph role emphasizes data structuring and AI, whereas the Analyst role centers on contract review and analysis.

What is a Contract Knowledge Graph?

A Contract Knowledge Graph is a structured representation of the information and relationships found within contracts. It uses graph technology to map entities such as parties, clauses, obligations, and deadlines, and the connections between them. This makes it easier to search, analyze, and visualize contractual data, enabling more efficient compliance checks, risk assessments, and contract lifecycle management. Organizations use contract knowledge graphs to gain better insights, automate contract analysis, and improve decision-making processes.
What are the most commonly searched types of Knowledge Graph jobs in Washington? The most popular types of Knowledge Graph jobs in Washington are:
What are popular job titles related to Contract Knowledge Graph jobs in Washington? For Contract Knowledge Graph jobs in Washington, the most frequently searched job titles are:
What job categories do people searching Contract Knowledge Graph jobs in Washington look for? The top searched job categories for Contract Knowledge Graph jobs in Washington are:
What cities in Washington are hiring for Contract Knowledge Graph jobs? Cities in Washington with the most Contract Knowledge Graph job openings:
Principal Knowledge & Data Architect

Principal Knowledge & Data Architect

Howard Hughes Medical Institute

Chevy Chase, MD โ€ข On-site

Other

Posted 2 days ago


Job description

The EverydayAI Accelerator exists to turn generative AI into daily reality across HHMIโ€™s administrative and operational functions. This role owns HHMIโ€™s knowledge management layer for AI: the discipline of turning institutional information (documents, records, policies, scientific content, operational data) into structured, retrievable, trustworthy knowledge that AI systems can actually use.

The work is technical and grounded. You will design and operate the retrieval-augmented generation pipelines that every Accelerator project depends on: the chunking, embedding, indexing, and retrieval patterns that turn HHMIโ€™s content into something AI can find and reason over. For use cases where a graph representation is the right tool (complex entity relationships, lineage, multi-hop reasoning), the knowledge graph gets built and operated alongside it. This work happens in partnership with the Principal AI Architect, who owns the AI platform and engineering foundation, and the Technology and Systems Management (TSM) Data Integrations team, who owns the data pipelines from source systems. Whoever holds this role designs the knowledge architecture and is accountable for operating it.

Why this role matters

HHMIโ€™s scientific, financial, and operational knowledge lives scattered across documents, databases, and systems never built to talk to AI. Without someone accountable for turning that information into something structured and trustworthy, every AI initiative at HHMI either repeats the same expensive groundwork or surfaces answers no one can stand behind. This role solves that problem once so that every Accelerator project and future AI effort can build on a governed, reliable knowledge foundation instead of reinventing it. 

What you will actually do 

  • Own HHMIโ€™s knowledge management architecture. Design how institutional content is captured, structured, classified, retrieved, and maintained over time. Make the calls on representation (chunked text, embeddings, structured records, knowledge graphs, or hybrid) for each kind of content and each kind of use case, and own the consequences. 

  • Build and operate the RAG pipelines. Design and run the retrieval-augmented generation systems that every AI product at HHMI consumes, including document processing, chunking, embedding, indexing, hybrid retrieval, re-ranking, query rewriting. New projects inherit proven patterns; they do not roll their own. 

  • Build knowledge graphs where the use case requires it. For problems where graph representation is the right tool (complex entity resolution, multi-hop reasoning, lineage and provenance, relationship-heavy queries), design the data model, stand up the graph store, and operate it.  

  • Extract structure from unstructured content. Build the pipelines that turn HHMIโ€™s documents (policies, applications, financial records, scientific content) into something AI can consume. Use the right mix of LLM-based extraction, classical NLP, and rule-based methods for each source, and be able to explain why. 

  • Solve entity resolution. The same person, fund, application, or concept appears across many systems with many representations. Build the deduplication, linking, and canonicalization that lets the institution rely on a single, defensible truth. 

  • Govern knowledge classification and lineage. Sit in the AI governance group as the technical voice on knowledge sensitivity, provenance, and retention. 

  • Partner with Data Integrations and the AI platform team. TSM Data Integrations owns the plumbing across HHMIโ€™s source systems, and you define what AI needs from it while co-building the contracts that connect the two layers. The Principal AI Architect owns the AI platform; the knowledge layer it reasons over comes from this seat. 

  • Communicate across the altitude range. Translate knowledge-architecture trade-offs for engineering teams, then turn around and explain the same decisions to a business leader or executive in terms that actually land. Expect to do both regularly. 

What we are looking for 

  • Real production RAG experience. Proven experience shipping retrieval-augmented systems and running in production, with failures debugged back through the pipeline and the broken step rebuilt. Hybrid retrieval, chunking strategy, query understanding, and re-ranking used as working tools, not just concepts. This is the core of the role. 

  • Knowledge management and data modeling. A librarianโ€™s instinct for content (whatโ€™s authoritative, whatโ€™s stale, who can see it), plus the ability to look at an unfamiliar domain and identify the right entities, relationships, and representation, defending why an attribute is a node, an edge, or not modeled at all. 

  • Knowledge graph and entity resolution experience. At least one knowledge graph designed, built, and operated in production, with a clear sense of when a graph beats a vector store or document chunk. Deduplication and linking problems solved where the same thing has seven names across four systems and none of them are wrong. 

  • Information extraction and production rigor. Extraction pipelines built to turn unstructured text into structured knowledge using a mix of LLMs, classical NLP, and rule-based methods, treating embedding versioning, retrieval evaluation, corpus drift, and re-indexing as first-class engineering concerns. โ€œThe model gave the wrong answerโ€ is a debuggable system, not a shrug. 

  • Data engineering, security, and range. Fluency in a data integration teamโ€™s tools (SQL, Databricks, dbt, ETL patterns) pairs with designing around data classification, access controls, and PII handling from the first conversation rather than as a final review. Ability to lead engineers technically without a reporting line, and to explain the same decision to a non-technical stakeholder in terms that help them choose. 

  • Technical range to operate at this level. Strong proficiency in Python and SQL. Production experience with vector databases (Postgres pgvector, Pinecone, Weaviate, Qdrant, or comparable) and embedding pipelines. Production experience with at least one graph database (Neo4j, AWS Neptune, JanusGraph, TigerGraph, Stardog, or comparable) and graph query languages (Cypher, SPARQL, or Gremlin). Working knowledge of modern NLP and information extraction. Fluency in the modern data stack (Databricks, dbt, or comparable). 

  • Education and experience. Bachelorโ€™s degree or equivalent, plus at least eight years of hands-on experience across data engineering, information retrieval, and applied machine learning, with at least three years focused on production knowledge management for AI systems (retrieval-augmented generation, knowledge graphs, or both). 

Nice to have 

  • Background in library or information science, formal ontology, or semantic web technologies (RDFS, OWL, SKOS).