| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
Nexus | Brazil | $140k - $157k | |||
Nexus | Argentina | $140k - $157k | |||
Nexus | Argentina | $98k - $120k | |||
Aztec | Remote | $133k - $156k | |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
Aztec | Remote | $91k - $162k | |||
Aztec | Remote | $90k - $145k | |||
ChainGPT | Remote | $22k - $75k | |||
Gemini | New York, NY, United States | $140k - $200k | |||
ChainGPT | Remote | $22k - $75k | |||
ChainGPT | Remote | $22k - $75k | |||
Trillion | Remote |
| |||
Veridise | Remote |
| |||
MLabs | New York, NY, United States | $200k - $400k | |||
ChainGPT | Remote | $22k - $75k | |||
Aztec | New York, NY, United States | $62k - $75k |
About Nexus
Nexus is building the foundation for verifiable finance, an economic system where every transaction, order, and settlement can be proven on-chain with cryptographic assurance. To do this we’re developing a DEX Layer 1 blockchain purpose-built for the AI economy, powered by idle compute from millions of people around the world, and verified with zero-knowledge proofs. This is finance rebuilt for the future: verifiable, scalable, and open to all.
Nexus has raised $25M in Series A funding from Lightspeed, Pantera, Dragonfly, SV Angel, and more.
Location: Remote (Brazil)
Type: Contract
Duration: 12 months with potential for extension
The Role
We’re hiring Protocol Engineers in Latin America to work at the core of Nexus’s Layer 1 execution runtime — building and evolving the systems that define how the protocol executes transactions, processes orders, and computes state transitions.
This is not a typical backend role. You’ll work on performance-critical protocol execution paths where microseconds matter, designing and implementing systems that may be enshrined directly into the Nexus protocol.
Your work will influence the execution model, runtime abstractions, and performance guarantees of a next-generation Layer 1 blockchain and high-throughput DEX engine.
Whether you’re a strong mid-level engineer looking to grow into protocol ownership or a senior/principal engineer eager to architect execution-layer systems, this role offers the opportunity to shape how the protocol itself behaves under load.
You’ll collaborate closely with protocol, cryptography, and product teams in San Francisco while contributing remotely from Mexico or Argentina.
What You’ll Do
Design and implement protocol-level execution systems in Rust, C++, or Go.
Build and evolve the runtime responsible for transaction execution, order processing, and state transitions.
Optimize concurrency, scheduling, memory layout, and I/O for deterministic, high-throughput execution.
Define and implement execution abstractions that may be enshrined at the protocol layer.
Work with cryptography and consensus engineers to ensure safety, correctness, and composability.
Diagnose and resolve performance and correctness issues using profiling, tracing, and benchmarking.
Help establish standards for protocol correctness, reliability, and execution guarantees.
For senior/principal engineers: lead execution of architecture decisions and mentor engineers working on protocol systems.
What We’re Looking For
Strong experience with Rust, C++, Go, or other systems programming languages.
Experience working on protocols, runtimes, execution layers, or consensus-adjacent systems.
Deep understanding of distributed systems, concurrency, and low-latency execution.
Ability to reason about correctness, determinism, and invariants at the protocol level.
Practical experience optimizing performance-critical systems.
Comfort operating in environments where correctness and performance are equally critical.
Excellent communication skills in Business English (spoken and written).
Bonus Points
Experience with blockchain protocol design, execution engines, or transaction ordering.
Familiarity with lock-free concurrency, cache-aware data structures, or zero-copy designs.
Background in formal methods, static analysis, or correctness-focused engineering.
Contributions to open-source protocol or systems-level projects.
Why Join Us
Help define the execution semantics of a new Layer 1 blockchain.
Work on protocol systems where your decisions have network-wide impact.
Grow into ownership of protocol-critical execution components.
Shape primitives intended to last — performant, correct, and foundational.
Join a culture that values deep technical rigor and long-term thinking.
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.