Senior DeFi Engineer — Autheo | Live Mainnet, Staking, Pools & THEO Utility

Launch Legends•Cheyenne, WY

2d•Remote

About The Position

Autheo is recruiting a Senior DeFi Engineer to ship the contracts that sit on a chain that is already live. Mainnet has been up since May 14, 2026. Staking and fees settle on-chain. THEO trades on MEXC, Hydrex (Base), and Robinhood Chain. The job is the on-chain money path: staking and fee surfaces a user can finish, pools and vaults if a design is approved, oracle reads, and the accounting a reviewer can follow. Solidity on an EVM-compatible chain. Tests before a deploy. The VP of Exchanges owns the external venue book. The DEX GM owns Autheo’s own matching engine, if that venue is built. API & Interoperability owns the IBC packet and the bridge schema. You own the contract. You do not own a CEX integration, a wallet with a fiat ramp, or a governance token. THEO is not a governance token. Autheo is not a DAO. Part-time does not mean advisory. Equity cofounder means you write the contract, you write the test, and you sit the review.

Requirements

5+ years shipping smart contracts that held value. A mainnet address, not a hackathon repo alone.
Solidity in production. EVM traces you can read. Gas and storage you have measured.
An AMM, a staking contract, a vault, or a bridge-adjacent pool you can walk through, including the bug you fixed or the one an auditor found.
Tests you wrote: unit, fork, and at least one invariant or fuzz suite.
Bachelor’s or Master’s in Computer Science, or equivalent practical depth.

Nice To Haves

Cosmos SDK or IBC enough to know when a transfer is a packet, not a function call.
An audit you sat through, with the findings list.
A public contract still in use.

Responsibilities

Staking, fee, and THEO utility flows a user can complete. Extend what is live. Do not fork a tutorial and call it a product.
Pools, vaults, or a routing contract only against a written design. Invariants named: share price, fee, and who can move the funds.
Token accounting you can explain to Security. Supply, emissions, and a pause. No hidden mint.
Assets that already move: Autheo native, and the Base path Adevar reviewed. A new route needs Protocol and API & Interoperability before you code it.
Oracle or price reads with a stale-price check and a failure mode. Name the feed.
Foundry or Hardhat, fuzz or invariant tests on the paths that move value.
An audit scope written before the audit, not after. You do not “conduct the audit” yourself and call it done.
Post-quantum work stays on the platform roadmap (Kyber, Dilithium, Falcon). You do not bolt a PQC scheme onto a pool unless Security has a spec.
A short SDK or ABI notes in TypeScript so DevHub can call what you shipped. Python only if a partner is already on it.
A simulation or a fork test a reviewer can run. Five minutes is a goal, not a slogan.