Time since we first saw it
Day 11
Similar jobs usually come down between day 6 and day 56.
At Exa, jobs usually come down by about day 93.
From 14,771 similar postings that came down, and 5 of Exa’s. Coming down is not always a hire.
Zurich, Switzerland
Actively hiring, first seen by us 11 days agoWork setup in the employer’s posting: On-siteFrom the employer’s posting
Employment type in the employer’s posting: FullTimeFrom the employer’s posting
Extract ontology-shaped claims from web pages and records, each with provenance, timestamp and confidence
Ingest new sources as versioned, append-only history with replayable cursors
Resolve entities across billions of records into canonical people, companies, places and publications
Build truth discovery that weighs source reliability, recency and corroboration to reconcile conflicting claims
Build idempotent, resumable incremental jobs over change data feeds so the graph converges
extraction that turns pages and records into ontology-shaped claims, each carrying its provenance, timestamp and confidence
versioned, append-only history with schema evolution, late-arriving and corrected records, and replayable cursors
entity resolution across billions of records (blocking, pairwise scoring, clustering) into canonical people, companies, places and publications
truth discovery that weighs source reliability, recency and corroboration to reconcile conflicting claims
incremental computation over change data feeds, where each update is a diff of what changed and every job is idempotent and resumable
Actively hiringFirst seen by us 11 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 11
Similar jobs usually come down between day 6 and day 56.
At Exa, jobs usually come down by about day 93.
From 14,771 similar postings that came down, and 5 of Exa’s. Coming down is not always a hire.
7 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- 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.
What we're looking for - 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.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Yes. We’ve followed one other Software Engineer, Knowledge Engine – Data Infrastructure job there since June 2026. It is still up.
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.
Exa is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, creed, color, religion, sex, sexual orientation, gender identity or expression, national origin, disability, age, veteran status, marital status, pregnancy or related conditions, criminal histories consistent with applicable law, or any other basis protected by applicable law.
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Zurich, Switzerland
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.