Protocol Engineer

  • Applications may have closed

The role:

We are building a communications tool with extreme security, coercion resistance and privacy in mind
You will help us research and develop new and existing technologies in secure messaging

Responsibilities:

  • Research and develop open protocols for secure messaging
  • Use a layered protocol approach that is mindful and explicit about what it requires, what it provides, under what threat models, and with what trade-offs
  • Combine cryptoeconomics and traditional technologies to create a sustainable distributed and fault-tolerant system
  • Write and maintain Nim code
  • Research and design core functionality
  • Provide feedback on overall design decisions, and participate in code reviews
  • Use libp2p to build application-level protocols
  • Build incentivized, distributed systems
  • Interpret and implement solutions based on academic research

Ideally you will have:

[Don’t worry if you don’t meet all of these criteria, we’d still love to hear from you anyway if you think you’d be a great fit for this role!]

  • A passion for blockchain technology, privacy-preserving technology and decentralization
  • Strong academic or engineering background
  • Deep understanding of encryption and key exchange mechanisms
  • Experience with low level/strongly typed languages (C/C++/Go/Rust or Java/C#)
  • Experience building networking-heavy applications and p2p networking specifically
  • Familiarity with message propagation in loosely connected networks
  • A solid grasp of p2p building blocks such as gossiping, routing and discovery (DHTs), and Nat traversal

Bonus points if you have:

  • Contributed to a blockchain-related, open source project
  • Experience with cryptography such as OTR, X3DH, Noise protocol
  • Experience with Nim
  • Experience with off-the-shelf networking stacks such as libp2p / devp2p

Hiring process:

The hiring process for this role will be:

  1. Introductory chat with Ceri from our People Ops team
  2. Interview with Oskar, Protocol lead
  3. Technical challenge / peer interview with Dean from the Protocol team
  4. Final interview with Jacek (Head of Research)

The steps may change along the way if we see it makes sense to adapt the interview stages, so please consider the above as a guideline
We’re looking for the new Protocol Engineer to join the team as soon as possible, and we’re hoping to close the hiring process ideally by the end of May 2020

Get to know us:

Find out about the team here: