Partnerships Lead — Autheo | Live Mainnet Integrations, Enterprises & Ecosystem

Launch Legends•Cheyenne, WY

2d•Remote

About The Position

The Partnerships Lead builds the relationships that put other people’s systems on Autheo, and Autheo into other people’s systems. Mainnet has been up since May 14, 2026. Staking and fees settle on-chain. DevHub is open. THEO trades on MEXC, Hydrex, and Robinhood Chain. The work is signed, operational relationships: protocol integrations, infrastructure and node partners, GSIs and enterprises with a workload, Marketplace suppliers, custody and treasury counterparts, and academic or research collaborators. VP of Exchanges & Token Markets owns the live venue book and the next THEO listing. You do not run that book. You bring the counterparty, and you hand listing and liquidity terms to that seat. Grants owns the Foundation award file. You do not. You work with the Managing Directors, Protocol, Developer Relations, Comms, and Foundation from first conversation through a countersigned MOU or integration agreement. No announcement without a feasible technical path and an owner on both sides. Part-time does not mean advisory. Equity cofounder means you own the pipeline and you close.

Requirements

Partnerships, BD, or ecosystem work at a live L1/L2, a Web3 foundation, an exchange, an infrastructure provider, or a comparable technology company. A pre-product startup alone is not the seat.
Agreements that shipped: integrations, listings, enterprise pilots, or co-sell motions. LOIs do not count by themselves.
Enough technical fluency to sit with an engineering lead, read an integration proposal, and know when to pull Protocol in.
Deals that involve tokens, nodes, liquidity, or usage commitments, without treating THEO as a giveaway.
MOUs, term sheets, and partnership agreements marked up with counsel.
A network in Web3 or enterprise technology, and the discipline not to burn it.
Clear written English. Remote, async. A 100+ person cofounder network across time zones.

Nice To Haves

Relationships at exchanges, market makers, custody platforms, GSIs, or Cosmos / IBC / EVM teams.
Ecosystem funds, joint grants, or builder incentives you stood up with the grants seat, not around it.
DeFi, decentralized identity, DePIN, or AI on a chain.
Work after a TGE, when the token was already trading.

Responsibilities

Run a living pipeline across five lanes: protocol / L1–L2 ecosystems; infrastructure, node, custody, and security; GSIs and Web2 enterprises; DevHub ISVs and Marketplace suppliers; academic and research groups.
Source, qualify, negotiate, and close MOUs, integration agreements, co-marketing terms, and technical scopes, from first call through countersigned paper.
Treat THEO as a live utility asset: counterparties who will spend or earn it on Mainnet services, node distribution, and usage commitments. Not a marketing giveaway.
Protocol and Engineering see an integration before it is promised.
DevRel, Product, Marketing, and Foundation comms get a joint launch only when the integration is live, or has a dated ship. Co-authored posts and shared events point at a working path, not a roadmap slide.
Conferences, partner summits, and closed-door meetings. You can explain Mainnet, THEO utility, the validator set, and the Marketplace rollout without a deck.
Monthly pipeline to the Managing Directors and Foundation: signed agreements, integration status, and what actually shipped. Quarterly pack for the board.