| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
Nexus | Buenos Aires, Argentina | $84k - $164k | |||
Matter Labs | Remote | $90k - $110k | |||
Horizenlabs | Remote | $72k - $100k | |||
Zircuit | Remote |
| |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
Boundless Networks, Inc. | Remote | $54k - $72k | |||
ChainGPT | Remote |
| |||
The Paradigm Shifters (Team TPS) | Austin, TX, United States | $81k - $95k | |||
Provable | New York, NY, United States | $81k - $100k | |||
Matter Labs | Remote | $84k - $112k | |||
Matter Labs | Remote | $62k - $90k | |||
Axiom | New York, NY, United States | $125k - $200k | |||
Polygon Labs | New York, NY, United States | $90k - $125k | |||
Polygon Labs | New York, NY, United States | $90k - $125k | |||
Alpha Hub | United States | $175k - $240k | |||
Succinct | Remote | $175k - $225k |
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 (commutable distance to Buenos Aires)
Type: Contract
Duration: 12 months with potential for extension
The Role
We’re hiring Systems Engineers in Latin America to work at the core of Nexus’s execution stack — contributing to the runtime behind our Layer 1 protocol and the high-performance engine that powers decentralized trading.
This is not a typical backend role. You’ll design, implement, and optimize all layers of the Nexus protocol stack — including consensus, execution, and API/RPC servers — while helping define new financial and trading primitives on the Nexus L1.
You’ll work on performance-critical systems where microseconds matter, building execution paths that may evolve into core protocol primitives. Whether you’re a strong mid-level engineer ready to grow into system ownership or a senior/principal engineer eager to architect high-throughput distributed systems, this role offers the opportunity to build software that runs at the heart of a global execution layer.
You’ll collaborate closely with protocol, cryptography, and product teams in San Francisco while contributing remotely from Argentina.
What You’ll Do
Design, implement, and optimize high-performance components in Rust, C++, or Go for Nexus’s DEX engine and protocol runtime.
Design, implement, and optimize all layers of the Nexus protocol stack, including consensus, execution, and API/RPC servers.
Build low-latency pipelines for order execution, event propagation, and state updates.
Design and implement financial and trading primitives on the Nexus L.
Optimize concurrency, scheduling, memory layout, and I/O paths for determinism and throughput.
Contribute to the evolution of execution abstractions that may be enshrined at the protocol layer.
Work with protocol engineers to ensure safety, composability, and consensus compatibility.
Investigate and resolve performance bottlenecks using profiling, tracing, and benchmarking techniques.
Help define standards for reliability, correctness, and high-assurance distributed execution.
-
For senior/principal candidates: drive system design decisions, shape execution architecture, and mentor others in performance engineering.
What We’re Looking For
Very strong systems engineering ability: writing modular, maintainable code within a complex codebase where correctness and performance are critical.
Experience with Rust (or C++/Go with strong performance focus).
Understanding of high-performance or distributed systems (e.g., low-latency engines, runtimes, databases, OS-level concurrency).
Ability to think in terms of execution flows, concurrency models, resource lifecycles, and system invariants.
Interest in performance optimization and low-level profiling (CPU, memory, synchronization overhead).
Strong first-principles thinker with excellent problem-solving skills, attention to detail, and communication ability.
Competitive programming experience (e.g., IOI, ICPC) or similar level of programming ability is a plus.
Excellent communication skills in business English (spoken and written).
Bonus Points For
Experience building matching engines, databases, compilers, blockchain runtimes, or HPC systems.
Familiarity with lock-free concurrency, zero-copy data structures, or cache-aware design.
Exposure to protocol engineering, consensus systems, or transaction ordering.
Background in correctness-focused engineering (e.g., formal verification, static analysis).
Open-source contributions to systems-level projects.
Why Join Us
Build the execution backbone of a Layer 1 blockchain and next-generation DEX engine.
Work on systems where your optimizations translate directly into global performance gains.
Grow from mid-level contributor to system owner — or drive execution architecture as a senior/principal.
Shape primitives designed to last — correct, performant, and potentially enshrined at the protocol level.
Join a high-performance engineering culture where ambition and deep technical work are expected.
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.