[mocatta]

Hadean | Systems Programmer | London | ONSITE, VISA

We're looking for a brilliant systems-level implementor to join us in London, or potentially remote, who matches ≥6 of the following:

  • loves C
  • loves Rust
  • has a wide array of ambitious self-directed projects
  • has got their hands dirty writing technically complex systems, such as:
    ◦ a high-performance database/KV store
    ◦ an OS
    ◦ a programming language implementation
  • enjoys writing roughly–performance-optimal code
  • enjoys writing roughly–reliability-optimal code (static/bounded memory allocation)
  • has used EPOLLET
  • has used io_submit + O_DIRECT
  • has bypassed the Linux kernel (for fun and/or profit)
  • has written on top of paravirtualisation APIs
  • enjoys reverse engineering
  • [insert your own comparable points here]

Our team runs the gamut — systems, distributed systems, compilers, professors, famous computer scientists — and is well-funded to change the landscape of compute. If intrigued, drop us an email at [e-mail]

[AndyKelley]

Warning: I had a close friend apply for this position about a year back and it was a bit sketchy. They said remote in the posting and then on the phone said the position was on-site. Additionally they said a salary number on the posting, and then on the phone said a lower number, with a promise to raise salary to the previous number after some amount of time. Then they lowered the number again in a second phone call.

[mocatta]

Sincere apologies to your friend. At that point we were bootstrapping, and had been for a year. We had a fundraise coming together but the amount and timing were at that point unknown, hence lack of specificity regarding salary early on. We have since closed funding so things have been firmed up.

As for on-site vs remote we've always been happy to do remote for the right candidate but prefer on-site. We have in the past and continue to have a few remote employees.

[hayd]

"bootstrapping" is a shitty excuse for changing the salary expectations mid-way through the process.

[mocatta]

From the perspective of a couple of engineer founders who went back and forth between two drastically different termsheets over the course of a few months of negotiations, it was either stick with a figure that relied on a deal we were leaning against, or share the most accurate picture at that point in time. It seems hard to justify acting differently, given the situation.

[Manikandan]

Sounds interesting to me!