Stop applying — get discovered by hiring agents.
| Job Position and Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|
| $63k - $76k | ||||
| $63k - $76k | ||||
| $90k - $150k | ||||
| $72k - $77k | ||||
 ISO 9001 Certified | 400+ students | Learn more | by Metana | ||
| $90k - $125k | ||||
| $87k - $90k | ||||
| $81k - $95k | ||||
RISC Zero📍 Remote | $253k - $330k | |||
RISC Zero📍 Remote | $288k - $330k | |||
RISC Zero📍 Remote | $231k - $282k | |||
| $87k - $87k | ||||
| $84k - $150k | ||||
| $81k - $110k | ||||
| $85k - $156k | ||||
| $121k - $164k |
About Codex
We’re a diverse team of experienced researchers and engineers scattered around the world working at the intersection of P2P networks and bleeding-edge Zero Knowledge technology. We’re building the next generation storage engine that attempts to “untie the knot” of incentivized storage. Our goal is to deliver a more advanced decentralized storage protocol that pushes the state of the art of decentralized storage solutions forward.
We’re looking for an experienced P2P Networking Protocol Engineer with hands-on experience designing and implementing state of the art networking protocols and distributed systems.
https://codex.storage/
Key responsibilities
- Design, implement and maintain state of the art p2p protocols and decentralized storage solutions
- Coordinate with the ongoing testing efforts to identify and eliminate instabilities in the existing codebase and bring it to production levels quality
- Implement and design new features as part of roadmap milestones
You ideally will have
- Strong academic or engineering background (PhD-level or equivalent in industry); relevant research experience
- Experience with low level libp2p primitives
- Experience with low level/strongly typed languages (C/C++/Go/Rust or Java/C#)
- Experience with Open Source software
- Keen communicator, eager to share your work in a wide variety of contexts, like internal and public presentations, blog posts and academic papers
- Strong networking (P2P systems) background
- Good debugging skills
- Good at explaining a complicated issue at varying levels of complexity for others to understand
- A strong alignment to our principles: https://status.im/about/#our-principles
Bonus points if
- Familiarity with the Nim programming language
- Familiarity with zero-knowledge proofs and other ZK-technology
- Familiarity with advanced cryptographic hashing functions
[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. Just explain to us why in your cover letter]
Hiring Process
- Interview with People Ops team
- Interview with Codex team member
- Technical Task
- Interview with Codex team member
- Interview with Codex Program Lead
Compensation
We are happy to pay in any mix of fiat/crypto.
What is Zero-knowledge?
Zero-knowledge is a concept in cryptography that allows two parties to exchange information without revealing any additional information beyond what is necessary to prove a particular fact
In other words, zero-knowledge is a way of proving something without actually revealing any details about the proof
Here are some examples of zero-knowledge:
- Password authentication: When you enter your password to log into an online account, the server doesn't actually know your password. Instead, it checks to see if the hash of your password matches the stored hash in its database. This is a form of zero-knowledge because the server doesn't know your actual password, just the hash that proves you know the correct password.
- Sudoku puzzles: Suppose you want to prove to someone that you've solved a particularly difficult Sudoku puzzle. You could do this by providing them with the completed puzzle, but that would reveal how you solved it. Instead, you could use a zero-knowledge proof where you demonstrate that you know the solution without actually revealing the solution itself.
- Bitcoin transactions: In a Bitcoin transaction, you prove that you have ownership of a certain amount of Bitcoin without revealing your private key. This is done using a zero-knowledge proof called a Schnorr signature, which allows you to prove ownership of a specific transaction output without revealing the private key associated with that output.
- Secure messaging: In a secure messaging app, you can prove to your contacts that you have access to a shared secret without revealing the secret itself. This is done using a zero-knowledge proof, which allows you to prove that you have access to the secret without actually revealing what the secret is.