| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
Nexus | San Francisco, CA, United States | $87k - $150k | |||
Anza | United States | $90k - $150k | |||
Succinct | Remote | $125k - $175k | |||
Aztec | Remote | $140k - $150k | |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
IO Global | Remote | $105k - $150k | |||
ether.fi | New York, NY, United States | $150k - $200k | |||
Matter Labs | Remote | $90k - $150k | |||
Aztec | Remote | $84k - $112k | |||
Horizenlabs | Remote | $84k - $110k | |||
Gemini | New York, NY, United States | $168k - $240k | |||
Provable | San Francisco, CA, United States | $10k - $32k | |||
Kraken | United States | $127k - $203k | |||
Mundy Buddy Publishing LLC. | United States | $72k - $112k | |||
Old Harmony | Palo Alto, CA, United States | $108k - $173k | |||
Ritual | New York, NY, United States | $88k - $101k |
About Nexus
Nexus is innovating at the intersection of artificial intelligence, blockchain, and zero-knowledge cryptography to build a Layer 1 for the AI era. Our team of world-leading experts is developing the Nexus Layer 1 blockchain, Nexus zkVM, and other breakthrough products with the goal of creating a verifiable financial world.
Nexus has raised $25M in Series A funding from Lightspeed, Pantera, Dragonfly, SV Angel, and more.
Role Overview
Remote in New York or hybrid in San Francisco
Nexus is seeking a Senior Infrastructure Software Engineer — with the potential to grow into a Tech Lead — to design and scale the core infrastructure powering our Layer 1 blockchain and its first core application: a high-performance DEX enshrined in the L1 protocol.
This role requires deep expertise in low-latency distributed systems and the ability to deliver secure, production-grade infrastructure for financial applications. You’ll work closely with Product, Research, and Security to build a system that meets the performance, reliability, and fairness requirements of modern trading systems — in a decentralized context.
Responsibilities
Architect and implement low-latency, high-throughput financial infrastructure for Nexus’s Layer 1 and DEX.
Own major roadmap milestones: public testnet → mainnet → institutional-grade performance.
Optimize consensus and transaction pipelines for speed, determinism, and security.
Collaborate with cryptography and protocol teams to integrate cutting-edge zero-knowledge proofs into production systems.
Mentor mid-level engineers and establish engineering best practices for reliability, security, and observability.
Ensure high availability and fault tolerance for mission-critical financial systems.
What Success Looks Like
Mainnet launch with enterprise-grade reliability and sub-second transaction finality.
DEX achieves low-latency trade execution comparable to centralized systems while maintaining decentralization.
Engineering systems and tooling enable <10 min developer onboarding to first transaction.
High-frequency trading performance benchmarks met or exceeded.
Engineering team scaled while maintaining high velocity and code quality.
Requirements
6–10+ years in software engineering, with at least 3+ years in infrastructure or systems roles.
Expertise in low-latency, high-throughput systems (e.g., HFT, distributed trading platforms, real-time financial exchanges).
Strong programming background in Rust (preferred), C++, Go, or similar systems languages.
Deep knowledge of network protocols, concurrency, and distributed systems.
Experience delivering secure, production-grade systems with measurable performance gains.
Bonus Points:
Previous experience in DeFi infrastructure, Layer 1 blockchains, or consensus protocols.
Familiarity with MEV prevention, transaction ordering, or fairness protocols.
Exposure to cryptography, zero-knowledge proofs, or formal verification.
Benefits
Competitive salary
Meaningful ownership in the Nexus protocol
Health insurance for employees and their dependents.
-
401(k)
Why Join Us
Define the engineering strategy and technical foundation for the future of decentralized finance.
Work on bleeding-edge technology at the intersection of AI, blockchain, and zero-knowledge cryptography.
Shape the engineering culture, processes, and products at an early, high-impact stage.
Play a pivotal role in building the next generation of financial infrastructure on Nexus Layer-1.
Nexus is committed to diversity in our workforce and is proud to be an Equal Opportunity Employer (EEO).
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.