LayerZero is hiring a Systems Engineer in Engineering — Vancouver, BC. The overview below is synthesized from the employer posting on job-boards.greenhouse.io: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
LayerZero
The Future is Omnichain.
Founded in 2021, LayerZero’s vision is to create a community of cross-chain developers, building dApps that are no longer constrained by individual blockchain capabilities. With LayerZero's simple, generic messaging protocol, builders will develop cross-chain dApps designed to unify the power of individual blockchains.
We are funded by the best investors in the world including:
a16z, Sequoia, PayPal, Binance Ventures, Coinbase Ventures, Uniswap Labs, Circle Ventures, Delphi Digital, and many more.
ABOUT THE ROLE
Day-to-day scope for the Systems Engineer as described in the posting:
We’re seeking a Systems Engineer to join LayerZero. In this role, you’ll build the foundational systems that power our execution and infrastructure layers, including Zero.
This is a low-level, performance-critical role focused on runtime architecture, concurrency, and scalable execution. You will make architectural decisions that directly impact how our systems execute, scale, and remain stable under load.
WHAT YOU'LL DO
Day-to-day scope for the Systems Engineer as described in the posting:
We’re looking for an engineer experienced in building robust, high-performance systems who is excited about solving hard infrastructure problems. You’ll work on distributed execution systems with strict correctness and performance requirements.
- Architect high-performance systems and leverage AI to implement them in Rust.
- Build and optimize core runtime, networking, or state management components.
- Profile and improve performance both at low-level (CPU, memory) and cluster-scale (network, scheduling).
- Debug race conditions, deadlocks, and production performance issues.
- Contribute to architectural decisions around scheduling, synchronization, and system scalability.
- Own systems end-to-end from design through production.
ABOUT YOU
Company context from the listing:
- Bachelor’s degree in Computer Science, Computer Engineering, or equivalent practical experience.
- 2+ years of experience building systems-level or performance-critical software.
- Strong proficiency in systems programming and leveraging AI to build software.
- Deep understanding of concurrency, CPU architecture, cache hierarchy, and operating systems .
- Experience designing or contributing to low-level storage, compute, or network infrastructure.
- Strong intuition for striking a pragmatic balance between complexity for performance and simplicity for robustness
- Experience using low-level profiling and debugging tools in production environments.
- Interest in working on distributed and execution-layer systems.
Equal Opportunity Employer
LayerZero Labs is committed to fostering a diverse and inclusive workplace. LayerZero Labs is an equal opportunity employer and does not discriminate on the basis of race, national origin, religion, gender, gender identity, sexual orientation, marital status, protected veteran status, disability, age, or any other legally protected status.
Build a standout application
For the Systems Engineer at LayerZero, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.