Time since we first saw it
Day 0
Early. Similar jobs usually come down between day 6 and day 55.
From 13,214 similar postings that came down. Coming down is not always a hire.
Senior Data Engineer
- Pay
- Pay not listed
- Work setting
Remote — work setting source
Work setup in the employer’s posting: remote
From the employer’s posting- Employment
Full-time — employment source
Employment type Full-Time
Employment type in the employer’s posting: Full-Time
From the employer’s posting
What you’ll work on
Full postingYou will design, build and run the systems behind our data products, covering ingestion, processing, analytical storage and serving.
Design and build scalable, high-throughput data pipelines and platform systems for blockchain data across 30+ chains.
Build backend data services and loaders in Go and Python.
From the employer’s posting
The Role You will design, build and run the systems behind our data products, covering ingestion, processing, analytical storage and serving. You own your work from the design document through to production. The people who design a pipeline also run it and answer for its numbers. Our stack is very wide, and we go deep in every part of it. We don't stop at "it works." We keep measuring, profiling and tuning to make systems faster, cheaper and more reliable. We want engineers who are razor sharp, pay close attention to detail, and care as much about why a query takes 800 ms as whether it returns the right answer.
What You'll Do Design and build scalable, high-throughput data pipelines and platform systems for blockchain data across 30+ chains. Build backend data services and loaders in Go and Python.
Design and build scalable, high-throughput data pipelines and platform systems for blockchain data across 30+ chains. Build backend data services and loaders in Go and Python. Design and evolve data models and analytical workloads in ClickHouse, and tune them for sub-second queries.
What you’ll bring
All qualificationsCore experience
- 5+ years building and operating production data systems, including ETL and ELT pipelines.
- Experience building platforms that serve multiple data sources, datasets or product teams.
- You have hands-on experience with pipelines over billions of rows and tens of terabytes.
Qualification wording
5+ years building and operating production data systems, including ETL and ELT pipelines. At least two of those years should be spent owning systems that other engineers depend on.
Experience building platforms that serve multiple data sources, datasets or product teams.
Large-scale data. You have hands-on experience with pipelines over billions of rows and tens of terabytes. You understand how partitioning, clustering and file sizing affect cost and latency.
Posting record
Report an errorActively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.
- Status in our records
- Live
- First seen by us
- Nov 11, 2026today
- Recorded sightings
- 1
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
How this job compares
Merklescience is hiring
5 open jobs
Open jobs by the week we first saw them, last 12 weeks.
- Data Engineer hiring is picking up
See how this role fits your experience
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.
- Python
- SQL
- AWS
- ClickHouse
- Databricks
- Delta Lake
- Docker
- Grafana
- Kafka
- Kubernetes
- Terraform
- Airflow
- PySpark
- Go
- GCP
Where the posting names them
- Design and build scalable, high-throughput data pipelines and platform systems for blockchain data across 30+ chains. - Build backend data services and loaders in Go and Python. - Design and evolve data models and analytical workloads in ClickHouse, and tune them for sub-second queries.
- 5+ years building and operating production data systems, including ETL and ELT pipelines. At least two of those years should be spent owning systems that other engineers depend on. - Expert Python and strong SQL. You write typed, tested code, are comfortable with asyncio and concurrency, and have built incremental data models over billions of rows. - Go for backend services. You have built and run high-throughput services or data loaders in Go in production.
- Large-scale data. You have hands-on experience with pipelines over billions of rows and tens of terabytes. You understand how partitioning, clustering and file sizing affect cost and latency. - Kafka, Airflow and Kubernetes in production. You understand delivery semantics and idempotent writes, have handled backfills and failures, and have run data workloads with Docker and Helm. Google Cloud is preferred; AWS is fine. - An operations and communication mindset. You instrument what you build, write runbooks and post-incident reviews, and can write a design document that a reviewer in another time zone can approve.
- Build backend data services and loaders in Go and Python. - Design and evolve data models and analytical workloads in ClickHouse, and tune them for sub-second queries. - Build incremental, idempotent pipelines on Databricks over billions of rows and tens of terabytes.
- Go for backend services. You have built and run high-throughput services or data loaders in Go in production. - ClickHouse in production. You know MergeTree schema and sort-key design, materialised views, bulk loads and query tuning. - Databricks in production. You have worked with PySpark, Delta Lake and Unity Catalog, designed incremental and idempotent tables, and kept an eye on compute cost.
- Design and evolve data models and analytical workloads in ClickHouse, and tune them for sub-second queries. - Build incremental, idempotent pipelines on Databricks over billions of rows and tens of terabytes. - Keep improving the scale, reliability, freshness, performance and cost efficiency of the platform.
- ClickHouse in production. You know MergeTree schema and sort-key design, materialised views, bulk loads and query tuning. - Databricks in production. You have worked with PySpark, Delta Lake and Unity Catalog, designed incremental and idempotent tables, and kept an eye on compute cost. - Large-scale data. You have hands-on experience with pipelines over billions of rows and tens of terabytes. You understand how partitioning, clustering and file sizing affect cost and latency.
- Graph or distributed key-value stores: entity resolution or clustering on large graphs. - Infrastructure as code, GitOps and observability: Terraform, Helm, ArgoCD, OpenTelemetry, Prometheus and Grafana, and load-test design. - Experience building platforms that serve multiple data sources, datasets or product teams.
Your next step
Complete your application on jobs.lever.co. The employer’s form will show what is required.
Applying through Lever
- No account needed: one form, and Lever reads your resume into the profile recruiters search.
Already applied? Track this application
Has Merklescience posted this job before?
Yes. We’ve followed 2 other Senior Data Engineer jobs there since November 2026. All 2 are still up.
Demand for Data Engineer roles
New Data Engineer postings at the employers we follow are up 7% 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.
About the role
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.
US government figures for database architects
- Median yearly pay, May 2025
- $139,500
- Expected change, 2025 to 2035
- 9.4% more jobsagainst 3.5% for all jobs
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.
Job description
⚡️ About Merkle Science
Merkle Science provides blockchain transaction monitoring and intelligence solutions for web3 companies, digital asset service providers, financial institutions, law enforcement and government agencies to detect, investigate and prevent illicit use of cryptocurrencies. Our vision is to make cryptocurrencies safe and provide infrastructure for the safe and compliant growth of cryptocurrencies.
Merkle Science is headquartered in New York with offices in Singapore, Bangalore and London. The team has combined experience across Bank of America, Paypal, Luno, Thomson Reuters and Amazon. The company has raised over US$27 MM from SIG, Beco, Republic, DCG, Kenetic, GGV and several others.
The Role
You will design, build and run the systems behind our data products, covering ingestion, processing, analytical storage and serving. You own your work from the design document through to production. The people who design a pipeline also run it and answer for its numbers.
Our stack is very wide, and we go deep in every part of it. We don't stop at "it works." We keep measuring, profiling and tuning to make systems faster, cheaper and more reliable. We want engineers who are razor sharp, pay close attention to detail, and care as much about why a query takes 800 ms as whether it returns the right answer.
You don't need blockchain experience. If you're a strong data engineer who wants to learn it, we'd like to hear from you.
What You'll Do
-
Design and build scalable, high-throughput data pipelines and platform systems for blockchain data across 30+ chains.
-
Build backend data services and loaders in Go and Python.
-
Design and evolve data models and analytical workloads in ClickHouse, and tune them for sub-second queries.
-
Build incremental, idempotent pipelines on Databricks over billions of rows and tens of terabytes.
-
Keep improving the scale, reliability, freshness, performance and cost efficiency of the platform.
-
Investigate hard performance and reliability problems and see them through to resolution.
-
Work closely with the product, analytics and investigations teams that use the data, and turn their needs into platform designs.
-
Help set technical direction through architecture discussions, design reviews and code reviews.
-
Mentor engineers and help set strong engineering and operational practices.
What You Bring
-
5+ years building and operating production data systems, including ETL and ELT pipelines. At least two of those years should be spent owning systems that other engineers depend on.
-
Expert Python and strong SQL. You write typed, tested code, are comfortable with asyncio and concurrency, and have built incremental data models over billions of rows.
-
Go for backend services. You have built and run high-throughput services or data loaders in Go in production.
-
ClickHouse in production. You know MergeTree schema and sort-key design, materialised views, bulk loads and query tuning.
-
Databricks in production. You have worked with PySpark, Delta Lake and Unity Catalog, designed incremental and idempotent tables, and kept an eye on compute cost.
-
Large-scale data. You have hands-on experience with pipelines over billions of rows and tens of terabytes. You understand how partitioning, clustering and file sizing affect cost and latency.
-
Kafka, Airflow and Kubernetes in production. You understand delivery semantics and idempotent writes, have handled backfills and failures, and have run data workloads with Docker and Helm. Google Cloud is preferred; AWS is fine.
-
An operations and communication mindset. You instrument what you build, write runbooks and post-incident reviews, and can write a design document that a reviewer in another time zone can approve.
Nice to Have
-
Blockchain data: EVM, UTXO or non-EVM chain data models, and pulling data from nodes over JSON-RPC or gRPC.
-
Graph or distributed key-value stores: entity resolution or clustering on large graphs.
-
Infrastructure as code, GitOps and observability: Terraform, Helm, ArgoCD, OpenTelemetry, Prometheus and Grafana, and load-test design.
-
Experience building platforms that serve multiple data sources, datasets or product teams.
-
AI-assisted development, and experience in fintech, compliance or AML.
How We Work
-
You'll join a small, senior team where everyone owns their work end to end.
-
We make decisions based on measured evidence, not opinion.
-
We keep design notes and runbooks next to the code.
-
We test at production scale and run blameless post-incident reviews.
-
We use AI coding tools every day, and we use judgement when reviewing what they produce.
❤️ Well Being, Compensation and Benefits
We care about your well-being. Along with excellent health insurance, we offer flexible time off, learning & development initiatives and hours that are designed to provide work/life balance. We regularly host team-building sessions and encourage discussions around mental health.
We reward talent and believe in acknowledging people for their contributions. We offer industry-leading compensation, along with generous equity. As a rapidly growing business, there are endless opportunities to grow your career with Merkle Science.
Employment type
Full-Time
Source details
Source notes
Source excerptsSelected passages from the saved posting. Check the full description for conditions and exceptions.
- Pay
No pay amount identified in the saved description.
- Location & working pattern
London
Working pattern and location restrictions need checking in the full posting.
- Work authorization
No clear work-authorization passage found. Eligibility is unconfirmed.