Back to jobs

Database Engineer

Cambridge, Massachusetts, United States; Palo Alto, California, United States; Singapore; Tokyo, Japan

Actively hiring, first seen by us 7 days ago
Pay
Pay not listed
Work setting
Not stated
Employment
Not stated

Before you apply

Work authorization
Must already have the right to workyou’ll need the right to work in the office you choose

What you’ll work on

Full posting
  • Build storage and query features in ClickHouse, such as replication over a shared file system

  • Make MooseFS and SeaweedFS highly available and durable with Raft-based metadata and automatic re-replication

  • Find performance problems in production profiles and fix them in the code

  • Trace data corruption to its root cause and repair the damaged data

  • Roll out releases and storage migrations across about 1,200 servers in three regions without downtime

From the employer’s posting
Build storage and query features in ClickHouse, such as replication over a shared file system
Make MooseFS and SeaweedFS highly available and durable: Raft-based metadata servers, follower reads, an intent log, automatic re-replication.
Find performance problems in production profiles and fix them in the code, from query plans to FUSE clients.
Trace data corruption to its root cause, even when it’s in compression, the memory allocator or the compiler, and repair the damaged data.
Roll out releases and storage migrations across about 1,200 servers in three regions, without downtime.
Apply at Ahrefs

Posting record

Report an error

Actively hiringFirst seen by us 7 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Oct 28, 20267 days ago
Recorded sightings
7
Last seen by us
Nov 4, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 7

Similar jobs usually come down between day 6 and day 54.

From 10,824 similar postings that came down. Coming down is not always a hire.

Ahrefs is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

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.

  • C++
  • ClickHouse
  • Elasticsearch
Where the posting names them
You’re probably right for this if - You write strong C++, C and Rust, can work in Go, and feel at home in codebases of millions of lines. - You know database storage engines deeply: merges or compaction, replication logs, query execution.
The team The Database team owns our databases and storage end to end, from the source code to production. We run ClickHouse, MooseFS, SeaweedFS, TiDB and Elasticsearch on about 1,200 servers holding hundreds of petabytes, in data centres in Singapore, the US and the UK. We don’t file tickets with vendors and wait. When a system doesn’t do what we need, we change its source, prove the change on production data and roll it out ourselves.
The job You’ll build and run our data layer: ClickHouse, the MooseFS and SeaweedFS storage under it, and the TiDB and Elasticsearch clusters beside it. You write the code, you ship it, and you’re there when it meets production. You’ll work with AI coding agents as a normal part of the job. Examples of what you’ll work on
Examples of what you’ll work on - Build storage and query features in ClickHouse, such as replication over a shared file system, and storage policies that place data by its merge history. - Keep up with upstream ClickHouse LTS releases, keep CI green and ship our own releases regularly.
- Build storage and query features in ClickHouse, such as replication over a shared file system, and storage policies that place data by its merge history. - Keep up with upstream ClickHouse LTS releases, keep CI green and ship our own releases regularly. - Make MooseFS and SeaweedFS highly available and durable: Raft-based metadata servers, follower reads, an intent log, automatic re-replication.
- Roll out releases and storage migrations across about 1,200 servers in three regions, without downtime. - Run and tune TiDB, TiKV, TiCDC and Elasticsearch: scheduling, replication lag, backups, disk balance. - Check risky designs with TLA+ and fault injection, and automate whatever repeats with watchdogs, balancers and dashboards.

Your next step

Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.

Applying through Greenhouse

  • No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
  • Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.

Already applied? Track this application

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

View original posting ↗

Own the data layer behind one of the biggest crawlers on the web.

Ahrefs helps marketers get their brands found in search, in AI answers and on social. Under the product sits one of the largest datasets on the web, and someone has to keep it fast, correct and alive. 

The team

The Database team owns our databases and storage end to end, from the source code to production. We run ClickHouse, MooseFS, SeaweedFS, TiDB and Elasticsearch on about 1,200 servers holding hundreds of petabytes, in data centres in Singapore, the US and the UK.

We don’t file tickets with vendors and wait. When a system doesn’t do what we need, we change its source, prove the change on production data and roll it out ourselves.

The job

You’ll build and run our data layer: ClickHouse, the MooseFS and SeaweedFS storage under it, and the TiDB and Elasticsearch clusters beside it. You write the code, you ship it, and you’re there when it meets production. You’ll work with AI coding agents as a normal part of the job.

Examples of what you’ll work on

  • Build storage and query features in ClickHouse, such as replication over a shared file system, and storage policies that place data by its merge history.
  • Keep up with upstream ClickHouse LTS releases, keep CI green and ship our own releases regularly.
  • Make MooseFS and SeaweedFS highly available and durable: Raft-based metadata servers, follower reads, an intent log, automatic re-replication.
  • Find performance problems in production profiles and fix them in the code, from query plans to FUSE clients.
  • Trace data corruption to its root cause, even when it’s in compression, the memory allocator or the compiler, and repair the damaged data.
  • Roll out releases and storage migrations across about 1,200 servers in three regions, without downtime.
  • Run and tune TiDB, TiKV, TiCDC and Elasticsearch: scheduling, replication lag, backups, disk balance.
  • Check risky designs with TLA+ and fault injection, and automate whatever repeats with watchdogs, balancers and dashboards.
  • Build an SRE agent that watches our database clusters, diagnoses incidents and proposes fixes.

You’re probably right for this if

  • You write strong C++, C and Rust, can work in Go, and feel at home in codebases of millions of lines.
  • You know database storage engines deeply: merges or compaction, replication logs, query execution.
  • You understand distributed consensus (Raft or Paxos) and what happens when things fail.
  • You know Linux storage internals: page cache, fsync, FUSE, file systems, and how NVMe and HDDs really behave.
  • You’ve run databases or storage on hundreds of nodes, and led the recovery when an incident hit.
  • You debug with gdb, perf and sanitizers.
  • You measure a change on production data before you call it a win.

Good to have

  • Contributions to an open-source database or file system.
  • OCaml. Much of our backend is written in it.
  • Puppet or a similar configuration management tool.

Why Ahrefs?

We give smart people real ownership and don’t micromanage them. Here that means a few hundred petabytes and the source code of the systems that hold them. Small team, no layers of process, and the hardware to do the job properly. We value honesty, results and simple solutions over complicated ones.

Ahrefs does not engage with agencies or third-party recruitment providers for the roles we hire for. If we need help, we’ll let you know.

Location: Singapore, Tokyo, Palo Alto (CA) or Cambridge (MA). On-site; you’ll need the right to work in the office you choose.

Ahrefs does not engage with agencies or third party recruitment solutions for the roles we hire for. If at any point we need help, we'll let you know! 

Source details

View original posting ↗

Source notes

Source excerpts

Selected 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

Cambridge, Massachusetts, United States; Palo Alto, California, United States; Singapore; Tokyo, Japan

Ahrefs does not engage with agencies or third-party recruitment providers for the roles we hire for. If we need help, we’ll let you know. Location: Singapore, Tokyo, Palo Alto (CA) or Cambridge (MA). On-site; you’ll need the right to work in the office you choose. Ahrefs does not engage with agencies or third party recruitment solutions for the roles we hire for. If at any point we need help, we'll let you know!
Work authorization
Ahrefs does not engage with agencies or third-party recruitment providers for the roles we hire for. If we need help, we’ll let you know. Location: Singapore, Tokyo, Palo Alto (CA) or Cambridge (MA). On-site; you’ll need the right to work in the office you choose. Ahrefs does not engage with agencies or third party recruitment solutions for the roles we hire for. If at any point we need help, we'll let you know!

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.