Build knowledge construction pipelines for Exa's knowledge engine, synthesizing vast amounts of data into a precise knowledge graph.
Posted by employer 2 days ago
First seen on Joblaze 2 days ago
Last verified on the company career page 9 hours ago
Skills & Technologies
What you'll build
Must have
Nice to have
Not disclosed in this posting: compensation, years of experience, work arrangement, visa sponsorship.
Joblaze summary
In this role, the Software Engineer for the Knowledge Engine will focus on building and maintaining data pipelines that transform vast amounts of web and vendor data into a structured knowledge graph. Proficiency in distributed data processing, particularly with Spark and Python, is essential, along with a strong understanding of incremental data processing techniques. This position is suited for experienced engineers who have a background in large-scale data systems and a keen attention to data quality and correctness. The work is foundational, contributing to a significant project aimed at creating a comprehensive and reliable knowledge base.
Joblaze insights
Quick facts
From the original posting
The Knowledge Platform team builds Exa's knowledge engine. We continuously synthesize information from across the web and beyond into one of the world's largest open-domain knowledge graphs, with hundreds of billions of evidence-backed claims. The work has two halves: construction pipelines that decide what to trust, and retrieval engines that decide how best to search it. Our goal is to give agents answers to any factual question about the world with unprecedented precision and completeness.
In this role, you'll build the knowledge construction pipelines: turning everything from a 100k docs/s web crawl to vendor datasets into a graph of what is true about the world, and keeping it correct as data changes.
This is greenfield work with a massive scope. There is no off-the-shelf system for building a model of the world from the open web, so you'll make foundational decisions, from how claims are represented and resolved to how trust is assigned and how the graph evolves over time, that everything built on top of it depends on.
Continuously synthesize the live web crawl, vendor deliveries and APIs, and other off-the-web sources into one typed graph: extraction that turns pages and records into ontology-shaped claims, each carrying its provenance, timestamp and confidence.
Bring every new source in cleanly: versioned, append-only history with schema evolution, late-arriving and corrected records, and replayable cursors, so every claim traces back to the exact delivery that produced it.
Decide what to trust: entity resolution across billions of records (blocking, pairwise scoring, clustering) into canonical people, companies, places and publications, then truth discovery that weighs source reliability, recency and corroboration to reconcile conflicting claims.
Keep that picture current and convergent: streams arrive continuously, out of order and at very different rates, so the graph is eventually consistent by design. You'll build incremental computation over change data feeds, where each update is a diff of what changed and every job is idempotent and resumable, so the graph converges to the same state however runs interleave, fail or replay, and readers only ever see committed, consistent versions.
Measure precision and completeness: labeled evals for extraction and resolution, per-source coverage and correctness metrics, and lineage that pinpoints which source or stage broke and why.
You've built and operated large-scale distributed data pipelines in production over petabytes of structured and unstructured data, with Spark over a lakehouse format (Delta Lake, Iceberg, Hudi).
You understand incremental processing deeply: change data capture, idempotent writes, backfills and reprocessing.
Strong in Python and at least one systems language; you can read and tune Spark query plans.
You obsess over correctness, reliability and data quality as much as scale.
Entity resolution, record linkage, knowledge graphs or ontologies
Information extraction or truth discovery at scale
Lance or other columnar/vector-native formats
Take a new billion-row dataset from first delivery to queryable entities in days, not months.
Keep a graph of hundreds of billions of claims current with incremental updates, so a fact that changes on the web reaches it in minutes.
Build a system that knows every company and person in the world, with one evidence-backed record each, resolved across the web and every source we ingest.
Standard company text repeated across Exa's postings is omitted here.