Singapore Rust jobs in Web3: which teams actually hire Rust (L1/L2/infrastructure) — and how do they screen?

I’m exploring Rust jobs in Singapore and I’m trying to map the real market (not just “Rust preferred” in a JD). In Web3, who actually hires Rust engineers here — L1/L2 protocol teams, validator/client teams, blockchain infrastructure roles (indexers, RPC, data availability), or more “systems engineering + networking” heavy infra groups?

If you’ve hired for, interviewed for, or worked in these teams in Singapore: what did the stack actually look like day-to-day (node performance, p2p networking, runtime/WASM, devops/SRE overlap, etc.)? And what screening patterns are you seeing?

I’m especially curious about:

• What gets used as the first filter: open-source contributions, a proof repo, past “protocol-grade” Rust, or just leetcode/systems rounds?

• Do teams test Rust fundamentals (ownership/lifetimes) or production debugging (profiling, memory/perf, observability, incident writeups)?

• For hiring teams: what “proof” makes you confident someone can ship on a distributed system and not just write clean Rust?

Would love concrete examples of interview loops you’ve seen in Singapore and what candidates usually underestimate.