Zero-knowledge proof engineer
New York City
-
In-office
Roughly
195k
Low-level / cryptography
Crypto / Web3
Brief description
Implement and optimize zero-knowledge proofs based on Ethereum blockchain data for a small series-A (9 people) crypto company. They're building tools that allow smart contracts to compute over ETH blockchain data.
This role is a mix of implementation and optimization. Part of your role will be implementing novel ZK proof circuits, and part of it will be optimizing provers directly. This role is a good fit for people with deep backgrounds in theoretical math/cs/physics, high-frequency trading, or hardware engineering.
What they're looking for
[Required]
Willing to work in-office in New York City
2+ years of experience with a low-level programming language like Rust, C++, or Go
Experience working on blockchain OR rollup nodes OR sequencers
Experience working with distributed systems in production
Deep background in mathematics and cryptography OR strong problem-solving skills and a deep interest in zero-knowledge proofs.
[Nice to have]
Experience with compiler frameworks like LLVM or MLIR.
Familiarity with low-level computer architecture like RISC or experience e.g. programming FPGAs
Familiarity with database internals (e.g. query planning/engines)
Research background in theoretical mathematics, computer science, or physics
Experience with low-level details of Ethereum
What they're offering
Salary: wide range but centered a bit below 200k. Dependent on seniority.
Equity: substantial early stage equity (we can't give you an exact number, but on the order of half a percent, well into six figures if taken at face value)
Highly technical role on a small team. The founders are both mathematics PhDs (one from MIT), and you'll get lots of exposure to mathematical theory.
Hiring process
Interview with us (otherbranch)
30 min culture fit/background review
1h technical round, 30m past project deep dive, 30m live coding (not a leetcode thing, cryptography related)
One-day take-home project, half a general back-end problem and half related to their zero-knowledge proofs.
Reference checks
