Rust Runtime & Developer Tooling Engineer — Autheo | WASM Execution, Contract SDKs & DevHub Tooling

Launch Legends•Cheyenne, WY

1d•Remote

About The Position

Autheo is seeking a Rust engineer to own its execution runtime and developer experience. The role covers WASM-compatible execution in the Eigensphere Engine, the Rust contract and SDK path, and cargo-level tooling for compiling, testing, and deploying through DevHub. This is a hands-on part-time equity cofounder role: the engineer owns a product surface, writes code, and reviews related code. The engineer will design deterministic WASM-compatible runtime modules, including host functions, gas/fuel metering, memory limits, and safe host calls for contract and DePIN compute tasks. They will build Rust contract SDKs and cargo-level tools, integrate these into DevHub, and improve performance and reliability through profiling, benchmarks, fuzzing, and CI. The role also includes working with DevRel on documentation and sample contracts and responding to developer issues in owned areas. The opportunity is remote and requires a commitment of at least 20 hours per week. Compensation is equity and token-based, including equity in Launch Legends, Autheo, and the WFO Creator Network, plus an allocation of the live THEO utility token. There is no cash salary for the role today.

Requirements

Provide a link to public Rust code personally written, such as a GitHub/GitLab profile, a crates.io crate with download history, or merged pull requests to a runtime, VM, compiler, or SDK project; applications without such a link will not be reviewed.
Production Rust experience, including ownership, lifetimes, procedural and declarative macros, traits, and async where appropriate.
Experience working inside a VM, interpreter, runtime, or compiler, such as WASM, EVM/revm, SVM/eBPF, MoveVM, or FuelVM; applicants should name the codebase and describe their contribution.
Experience publishing or maintaining a library, SDK, or CLI used by other developers; applicants should provide a reference.
Comfort with cross-compilation targets such as wasm32 and aarch64, and with CI pipelines that build, test, and release Rust.
Commitment of at least 20 hours per week.

Nice To Haves

Contributions to ink!/cargo-contract, CosmWasm, wasmtime, wasmer, wasmi, revm, Stylus, Anchor, Sway/FuelVM, Move, or a comparable project.
Experience with gas or metering design, deterministic execution, or sandboxing such as seccomp or WASI capabilities.
TypeScript SDK experience or experience designing APIs adopted by other teams.
A publicly available artifact such as a crate, talk, blog post, or design document.

Responsibilities

Design and ship deterministic WASM-compatible runtime modules, including host functions, gas/fuel metering, memory limits, and safe host calls for contracts and DePIN compute tasks.
Avoid unsafe Rust unless there is a written rationale, a test, and a reviewer who understands the invariant.
Profile execution on replay and Mainnet, and report measured p50/p99 latency, allocations, and instruction counts.
Build a Rust contract SDK with macros, storage abstractions, and ABI/metadata generation.
Build a cargo-level CLI to build, test, deploy, and verify, including reproducible builds and a local sandbox or replay node for testing without a production key.
Develop Rust and JavaScript/TypeScript client SDKs that provide a short path from the documentation to a working call.
Integrate the toolchain into DevHub with templates, examples, actionable error messages, and versioned releases with changelogs.
Work with DevRel on documentation and sample contracts, and answer developer issues in the areas owned.
Add CI benchmarks for execution and serialization hot paths so regressions fail the build.
Fuzz the host interface and contract ABI.
Within the first 90 days, produce a written map of the Rust execution and tooling surface, including what is live or stubbed and where DevHub users struggle, with a stop/continue/start list.
Within the first 90 days, deliver a runtime path measured on replay, fuzzed, covered in CI, and documented; a first versioned Rust contract SDK or CLI release with a working DevHub template and sandbox flow; and a CI benchmark for an execution hot path.