Hyperliquid Labs is hiring a Backend Engineer in Engineering — APAC. The overview below is synthesized from the employer posting on jobs.ashbyhq.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
Key Responsibilities
Day-to-day scope for the Backend Engineer as described in the posting:
- Design, implement, and optimize all layers of the Hyperliquid protocol stack. This includes consensus, execution (HyperCore and HyperEVM), and API/RPC servers.
- Design and implement financial and trading primitives on the Hyperliquid L1
About You:
- Very strong systems engineering ability: writing modular, maintainable code within a complex codebase, where correctness and performance are critical
- Interest in performance optimization
- Strong first principles thinker
- Excellent problem-solving skills, attention to detail, and communication skills
- Competitive programming experience (e.g., IOI, ICPC) or similar level of programming ability
- Experience with Rust
- Able to work in-person
Build a standout application
For the Backend Engineer at Hyperliquid Labs, 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.