Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 4 days ago

Database Engineer

Ahrefs13 open roles

Where
Cambridge, Massachusetts, United States; Palo Alto, California, United States; Singapore; Tokyo, Japan
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowDatabase EngineerAhrefs · Cambridge, Massachusetts, United States; Palo Alto, California, United States; Singapore; Tokyo, Japan

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Ahrefs's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

12.8% of postings close within 7 days. Measured by our own scanner across the market. Ahrefs postings stay open a median of 43 days.

Share of postings closed within
  1. 2.2%1 day
  2. 4.5%3 days
  3. 12.8%7 days
  4. 20.6%14 days
  5. 35.6%30 days
  6. 58.4%60 days
This job: posted 4 days ago

Ahrefs median: 43 days open

The 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!

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Ahrefs's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on Ahrefs's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    Ahrefs's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.