Senior WebAssembly / Rust-to-Wasm Architecture & Review Specialist

We are rebuilding a browser-based content-protection layer. The code is written by AI coding agents, not by hand. We need a senior WebAssembly specialist to own the client-side (Rust to WebAssembly) architecture and review - to make sure our architecture document and the agent prompts derived from it are complete and correct, and to review the Wasm the agents generate and direct their fixes. You will not be writing the module yourself. You will be the judgment that makes the generated code near-correct the first time, and the reviewer who catches what is wrong. You will work under our lead cryptography architect, who owns the server-side and cryptographic design. You own the browser/Wasm boundary. The context (so you know exactly what you're walking into) Content is encrypted server-side (AES-256-GCM) and decrypted client-side in a Rust to WebAssembly module. The decryption key is a non-extractable WebCrypto key held outside Wasm - usable from JS/Wasm, but its bytes never enter Wasm linear memory. The browser is hostile: the user may own and instrument it. Wasm is treated as cost-raising obfuscation, not as a security boundary. Our whole development model is agentic: agents generate the Rust/Wasm from prompts, which are generated from an architecture document. Humans set direction, shape prompts, and review output. What you'll actually do Pressure-test the architecture document for the WebAssembly / browser boundary - is it complete, correct, and free of design mistakes before anything is generated? Make the prompts correct - review the prompts derived from the architecture so the agents produce near-correct Wasm on the first pass. Review generated output and direct fixes - when the agent-generated Rust to Wasm has a boundary bug, a memory-marshalling flaw, a key-exposure mistake, or a performance cliff, diagnose it and tell the agent precisely how to fix it. This is a reviewer / architect seat. If your value is writing Wasm by hand, this is not the role. If you can look at an architecture doc, a prompt, or a block of generated Wasm and immediately see what's missing or wrong - this is exactly the role. You must have Deep, production Rust to WebAssembly experience: wasm-bindgen, wasm-pack, web-sys / js-sys. Real command of the JS - Wasm boundary: marshalling data across it, calling browser APIs (including WebCrypto) from Rust/Wasm, and the memory model (linear memory as an ArrayBuffer - what is visible, what is copied, what leaks). The ability to review and audit Wasm for correctness, security, and performance by reading it - not just by writing it. A security mindset for the browser surface: non-extractable WebCrypto keys, keeping key bytes out of linear memory, minimizing plaintext exposure, CSP, same-origin, dependency controls. Comfort directing AI coding agents - shaping prompts and review feedback precise enough that a model produces correct code. Nice to have Client-side cryptography or DRM/content-protection exposure. Web Workers, streaming compilation, bundler integration (Vite/webpack/esbuild), binary-size and performance profiling. Experience reviewing AI-generated code. How we hire Five targeted questions below (answer in your proposal). The strongest candidates then do a short working session: we put an architecture excerpt and a block of agent-generated Rust to Wasm in front of you and you review it out loud - exactly the real job. Individual contractors only (no agencies); this is a senior review seat and we want the person doing the work.