Senior Solutions Architect — Autheo | Live Mainnet, Enterprise & Partner Designs

Launch Legends • Cheyenne, WY

2d • Remote

About The Position

Autheo is recruiting a Senior Solutions Architect to turn a live chain into a design a partner can build against. Mainnet has been up since May 14, 2026. Staking and fees settle on-chain. DevHub is open. THEO trades. Identity, Marketplace compute and storage, THEO AI, and post-quantum primitives are rolling onto that network. The job is the blueprint between that stack and a real workload: finance, infrastructure, a GSI engagement, or a regulated data path. You write the architecture, the reference implementation, and the review. You do not invent a second chain in the slide. Partnerships owns the account and the close. API & Interoperability owns the packet and the schema. SRE owns the hosts and the page. You own the design those seats can ship, and you sit in the room when a customer architect asks how identity, storage, and a contract fit together. Part-time does not mean advisory. Equity cofounder means the blueprint has an owner, a repo, and a date.

Requirements

• 5+ years designing solutions a customer deployed, not only proposed. Blockchain, cloud platform, or infrastructure. Enterprise adoption weighs more than a protocol tour.
• You can sit with a consensus or API engineer and with a buyer’s architect in the same week.
• Working knowledge of EVM, Cosmos / IBC, or an equivalent production chain. Autheo is both.
• Enough compliance fluency to know what GDPR or a healthcare control actually requires, and to say when Autheo does not meet it yet.
• Clear writing. A design note someone else can build from.
• Bachelor’s or Master’s in Computer Science, or equivalent practical depth.

Nice To Haves

• A lighthouse you shipped with a GSI or a named enterprise, including what did not make the cut.
• Identity, storage, or DePIN designs that went to production.
• A reference architecture still in a public repo.

Responsibilities

• Solution design: End-to-end designs on what is live or dated to ship: Layer-1, DevHub, TheoID, Marketplace compute and storage, IBC, and the Base bridge Adevar already reviewed. Say what is on Mainnet, what is rolling out, and what you will not promise. A diagram that assumes a future runtime is marked as such. Vendor lock-in called out: what runs on Autheo, what stays in the customer’s cloud, and the exit.
• Reference implementations: One working reference per lighthouse, in a repo a stranger can run: contract, DevHub path, or integration against Chain ID 2127. Architecture notes Protocol, Security, and the partner engineer will both sign. Compliance called where it is real (GDPR, CCPA, a healthcare control). A certification is a program with an owner, not a box on the slide.
• Reviews: Architecture reviews with the customer’s engineers, a GSI, and Autheo Protocol. You can defend staking, fees, validator design, and THEO utility without a readout. Handoff to Partnerships for the commercial close, and to Engineering for the build. You do not announce a lighthouse that has no technical owner.
• Verticals: Finance, infrastructure, and regulated data, in that order of what the live stack can hold today. Government only with a named buyer and a control set. Co-marketing only after the reference implementation runs.

Benefits

• Equity in Launch Legends
• Equity in Autheo
• Equity in the WFO Creator Network
• Token allocations in the Autheo blockchain
• THEO allocation in a live utility token
• Salaried compensation is expected to begin within 4 to 5 months

What This Job Offers

• Job Type: Part-time
• Career Level: Senior