Rust backend roles (SF on-site): what proof gets you shortlisted for production Rust services (reliability + concurrency + scale)?

I posted a Rust Backend Engineer role (Svix) — SF on-site, $130k–$180k. It’s not “Web3”, but the skill signal is the same as many infra/protocol teams: production reliability, concurrency, and system judgment.

If you were screening this in 10 seconds, what 2 proof signals would you want to see?
Pick any two and explain in one line: benchmarks/load tests, idempotency + retries, backpressure/queues, incident/SLO write-up, graceful shutdown, OSS crates.

Bonus: what 3 questions would you ask about on-call + failure modes + throughput expectations?

Job link: https://artofblockchain.club/job/rust-backend-engineer-rust