Database Engineer

Ahrefs

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

Posted 23 days ago· Checked live at Ahrefs 29 minutes ago

Stale: open 23 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Ahrefs asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Ahrefs's own hiring page 29 minutes ago.
What is the job?
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.
What does it pay?
The posting doesn't say.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

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 Database team owns our databases and storage end to end, from the source code to production.

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.

Similar open jobs

Jobs in San Jose (7796)Jobs in Singapore (275)Jobs in Tokyo (153)