| Job Position | Company | Posted | Location | Salary | Tags |
|---|---|---|---|---|---|
Nexus | Remote | $105k - $180k | |||
Nexus | United States | $140k - $180k | |||
Very AI | San Francisco, CA, United States | $77k - $107k | |||
ether.fi | New York, NY, United States | $180k - $260k | |||
| Learn job-ready web3 skills on your schedule with 1-on-1 support & get a job, or your money back. | | by Metana Bootcamp Info | |||
Char Network Labs | Miami, FL, United States | $72k - $150k | |||
Old Harmony | Palo Alto, CA, United States | $108k - $173k | |||
Signature IT World Inc | United States | $77k - $84k | |||
ThoughtStorm | United States | $77k - $84k | |||
Layerzerolabs | Remote | $89k - $180k | |||
BITFIT LABS PTE LTD | Remote | $150k - $180k | |||
ether.fi | New York, NY, United States | $150k - $200k | |||
Nomos | Remote | $81k - $95k | |||
Logos | Remote | $81k - $95k | |||
Aztec | Remote | $91k - $162k | |||
Aztec | Remote | $84k - $87k |
About Nexus
Nexus is the engine for verifiable finance — a blockchain designed to natively embed the world’s financial system into one compounding system. Built to support every major financial market on a single global exchange, Nexus unifies infrastructure that has historically been fragmented across chains and intermediaries.
Headquartered in San Francisco with a growing presence in Buenos Aires, Nexus is proud to be a cross-continental team of engineers, cryptographers, and market builders. We’re investing deeply in the Latin American ecosystem — and always looking for world-class talent to join us.
Nexus is backed by leading investors, including Pantera, Lightspeed, Dragonfly, Faction, Blockchain Builders Fund, Alliance, and SVA, and works with more than 100 partners across the global finance and blockchain stack.
Location: Remote (Argentina)
Type: Contract
The Role
We are looking for a Technical Lead to own the technical architecture across Nexus’s product surface and ensure the code shipped by our engineering pods is coherent, performant, and built to last. You’ll set the bar for how we design systems, write code, and review each other’s work — and you’ll do it with your hands on the keyboard, not just on a whiteboard.
You’ll partner closely with engineering management to grow pod maturity, raise the level of technical decision-making across the team, and turn architectural intent into shipped product. This is a senior individual-contributor role with broad influence — ideal for someone who has been a staff/principal engineer or hands-on tech lead and wants the autonomy and leverage of a small, ambitious team.
What you’ll do
Own the architecture. Define and evolve the technical architecture spanning our Rust services, Go infrastructure, and Next.js/TypeScript surfaces on GCP — and make sure what gets built actually matches it.
Stay hands-on. Write production code in the highest-leverage parts of the stack: critical services, shared libraries, complex integrations, and load-bearing changes that set patterns for the rest of the team.
Guide pods of engineers. Work across multiple pods to align on system boundaries, interfaces, data models, and non-functional requirements. Lead design reviews and unblock teams on hard technical decisions.
Raise the engineering bar. Shape how we do code review, testing, observability, on-call, and incident response. Drive the practices that make a team able to ship quickly and safely at scale.
Cultivate engineering maturity. Partner with engineering managers to grow ICs, mentor tech leads, calibrate seniority, and develop the next generation of architects on the team.
Translate strategy into systems. Work with product, research, and leadership to turn ambiguous goals into clear technical plans and sequenced execution paths.
Communicate clearly. Write crisp design docs, RFCs, and post-mortems. Make complex systems understandable to engineers, leadership, and partners.
What we’re looking for
Experience. 5+ years building production software, including 2+ years in an engineering leadership capacity — tech lead, staff engineer, or architect responsible for system-level design across multiple teams.
Tech stack fluency. Deep, hands-on proficiency in our core stack: Rust, Go, Next.js / TypeScript, and Google Cloud (GCE/GCP). You’ve shipped non-trivial production systems in these technologies, not just read about them.
High-throughput, low-latency systems. You’ve designed and operated production systems where throughput and tail latency are first-class constraints — think trading systems, real-time matching/order flow, high-frequency event pipelines, or comparable performance-critical infrastructure.
Architecture chops. Demonstrated track record designing distributed, performance-sensitive systems and making sound trade-offs around correctness, latency, throughput, and operability.
Engineering judgment. Strong instincts for code quality, testing strategy, and sustainable abstractions. You know when to invest, when to ship, and when to pay down debt.
Leadership without authority. You influence through clear thinking, written artifacts, and credible code — not titles. You’ve mentored senior engineers and helped grow tech leads.
Communication. Fluent written and spoken English. You can run a design review with senior engineers and explain a system to a non-technical stakeholder in the same day.
Remote-readiness. Based in Latin America, comfortable working asynchronously, and able to maintain meaningful overlap with US Pacific working hours.
AI-native. Embrace AI as a core part of how you work, think, and build.
Bonus points
Experience building web3 trading venues — DEXs, on-chain exchanges, or trading/matching systems with on-chain settlement.
Experience in crypto, zero-knowledge, or other cryptographically intensive systems.
Open-source contributions in Rust, Go, or the broader systems ecosystem.
Background scaling consumer or developer products with millions of users or nodes.
Experience standing up engineering practices (CI/CD, observability, on-call) inside a fast-growing org.
Prior work as a founding or early engineer at a high-velocity startup.
Our stack
Backend & systems: Rust, Go
Web & product surfaces: Next.js, TypeScript
Infrastructure: Google Cloud (GCE/GCP), containerized services, modern CI/CD
Domain: Layer 1 blockchain, zkVM, distributed proving network
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.