Senior Site Reliability Engineer — Autheo | Live Mainnet, RPC & Validator Operations

Shape the Future of Blockchain—Bringing Business On-Chain

We’re offering a unique opportunity to join Launch Legends (and Autheo ) as a part-time Equity Cofounder . Founded in July 2021 , Launch Legends is at the forefront of bridging Web3 blockchain technology with the next evolution of Web2 integration—bringing businesses on-chain through enterprise-grade solutions, DePIN innovations, and decentralized financial infrastructure.

Our flagship project, Autheo , is an AI-enabled Layer-0 Operating System with an integrated Layer-1 blockchain and complete decentralized infrastructure that includes decentralized compute, storage, identity, and service marketplaces, as well as a full-stack development environment ( DevHub )—engineered for scalable enterprise adoption, developer innovation, and real-world blockchain integration.

Our Projects

• Autheo —
• THEO token launch & verified markets —
• Docs —
• Autheo Team —
• Launch Legends (Parent Company) —
• X / Twitter —

About Autheo

With nearly 100 equity cofounders from leading companies and institutions—many with advanced degrees and PhDs—Autheo is solving the critical challenges blocking business adoption of blockchain technology.

Autheo Mainnet has been live since May 14, 2026 (Chain ID 2127). Staking and transaction fees are operating on-chain. DevHub is available to builders. Sovereign identity ( TheoID ), decentralized compute and persistent storage through the Autheo Marketplace , AI inference ( THEO AI ), and post-quantum cryptography are rolling out on Mainnet.

THEO is live. This role starts after mainnet, not before it.

As of October 2, 2026 , THEO trades on four Autheo-verified markets across two chains and one centralized exchange, with Enflux supporting liquidity across the venues:

• THEO/USDT on MEXC — first centralized order book, opened October 1, 2026 at 13:00 UTC . Deposits are accepted on Autheo Mainnet (native THEO). Withdrawals opened October 2, 2026 at 13:00 UTC .
• THEO/USDC on Hydrex (Base) — live since August 20, 2026 . Official Base contract: 0xebE516a20238F79dc20b07eaD6768e08891Ed309
• THEO/USDG on Uniswap v3 (Robinhood Chain) — live since September 10, 2026
• THEO/NVDA on Uniswap (Robinhood Chain) — live since September 24, 2026 . Official Robinhood Chain contract: 0x3dc751e0da01812e6d9143cc696e7f07ea94da48

Verified trading links, contract addresses, and network information:

Key Features

• Layer-0 OS + Layer-1 — Sovereign Cosmos-based coordination layer with an EVM-compatible execution environment, IBC interoperability, and Proof of Autheo consensus.
• DevHub & full-stack SDKs — One workspace for frontend, backend, smart contracts, and orchestration.
• TheoID — Sovereign identity for people, services, and AI agents, with a post-quantum roadmap ( Kyber, Dilithium, Falcon / NIST ML-KEM, ML-DSA, SLH-DSA).
• Autheo Marketplace — Decentralized compute, storage, and service markets rolling out on Mainnet.
• THEO AI — Inference and agent orchestration as a native primitive, not a third-party bolt-on.
• DePIN infrastructure — On-chain networks for real-world infrastructure ownership and resource sharing.

Traction

• Mainnet: Live since May 14, 2026 . Staking and fees on-chain. Secured by the live validator set (149 active of 156 total as of September 23, 2026).
• Public testnet history: 2 million+ wallets , 10 million+ transactions , 1.1 million+ smart contracts .
• Audits: Halborn (testnet and validator node platform), CertiK (Mainnet and smart contracts), Adevar Labs (Base to Autheo Mainnet bridge).
• THEO markets: Four verified venues — MEXC , Hydrex on Base , and two Uniswap pools on Robinhood Chain — with Enflux as liquidity partner across DEX and CEX.
• Token: THEO , native utility coin. Maximum supply 7.0 billion . Approximately 5.33% designated as initial circulating supply at the August 20, 2026 TGE ($0.05 reference price on Hydrex).
• Organization: Launch Legends Inc., a Wyoming corporation, parent of Autheo LLC. Stewarded in part by the Autheo Foundation . 100+ equity cofounders across 25+ countries .

Compensation & Growth Path

This is a part-time equity / token-based cofounder opportunity. You will receive equity in Launch Legends , Autheo , and the WFO Creator Network , along with token allocations in the Autheo blockchain. THEO is already trading; this is an allocation in a live utility token, not a promise against a future TGE. We have already completed an initial financing round to support infrastructure and marketing, and are currently in discussions with VCs and crypto investors to fund expansion and salaries. Salaried compensation is expected to begin within 4 to 5 months , following our node, token sales, or funding.

ROLE: Senior Site Reliability Engineer — Autheo | Live Mainnet, RPC & Validator Operations Job code: LA380

About the Role

Autheo is recruiting a Senior Site Reliability Engineer to keep the live network usable.

Mainnet has been up since May 14, 2026 . Staking and fees settle on-chain. DevHub is open. THEO deposits and withdrawals run on Autheo Mainnet. The job is the production path under that: validator and RPC health, the public endpoints builders hit, the bridge and API surfaces already in production, and the rollout of Marketplace, TheoID, and THEO AI onto the same operations standard.

You design and run the cloud and node platform. You own SLOs, the on-call you can actually staff, and the automation that keeps a repeat incident from being a page. You sit with Protocol, Engineering, and Support. You do not own consensus design, exchange listings, or the grant file.

This is Autheo Mainnet (Chain ID 2127) , an EVM-compatible, IBC-connected chain. Operating someone else’s Ethereum, Polygon, or BNB RPC is related experience. It is not the job.

Part-time does not mean advisory. Equity cofounder means you own a surface, you are on the incident, and you write the fix.

Key Responsibilities

1. Mainnet and RPC

• Operate validator, sentry, and RPC infrastructure for Autheo Mainnet. Full and archive where the product needs them.
• Watch the chain, not a generic host: block height, peers, sync, missed blocks, mempool, and endpoint error rate.
• Capacity for public RPC: load balancing, caching, throttling, and a clear split between public and private peers.

2. Cloud platform

• Production on AWS : VPC, IAM, KMS, Secrets Manager, load balancers, and the compute the nodes actually run on.
• Terraform for anything you expect to rebuild. Kubernetes (EKS or equivalent) where the service is a service, not a node that must not move.
• Helm or GitOps for the deploy path. A console click is not a change.

3. Reliability

• SLOs for the paths that matter: RPC availability, bridge, DevHub API, staking and fee submission. Error budget in writing.
• On-call for S1 and S2. Incident command, a timeline, and a review that names the next control.
• Toil removed by automation. CI for Terraform plan, image build, and Helm. Python, Bash, or Go.

4. Observability

• Metrics, logs, and traces on the paths you own. Prometheus, Grafana, OpenTelemetry , CloudWatch. Datadog or ELK if that is what is already running.
• Alerts a human can act on. A page without a runbook is a draft.

5. Security and keys

• KMS and secret handling for node keys, bridge keys, and service credentials. No key in a repo, a chat, or a disk image you cannot account for.
• Guardrails that match the audits already done ( Halborn on the validator platform, CertiK on Mainnet, Adevar on the Base bridge). SOC 2 work only where a control owner exists.

Qualifications

Required

• 7+ years in cloud, SRE, systems, or DevOps, including production on-call.
• 5+ years operating production workloads on AWS .
• Kubernetes and containers in production, and Terraform you have applied, not only planned.
• Observability you can walk through: Prometheus, Grafana, OpenTelemetry, CloudWatch, or Datadog.
• A blockchain network you have run or supported: nodes, RPC, sync, and a failed transaction you traced to a cause.
• Distributed systems: retries, backpressure, failover, and a capacity number you measured.
• Incident response and a post-incident review you can share.

Preferred

• Cosmos SDK or EVM client operations, IBC relayers, or a bridge you have kept up.
• GitOps (Argo or equivalent) and a pipeline you owned.
• AWS certification. Useful, not required.
• A runbook or a public postmortem.

Not persuasive on its own

• A list of every AWS service, every wallet, and every explorer. Name the chain you operated and the incident you closed.

First 90 Days

• A map of what is in production versus what is still a laptop: validators, RPC, bridge, DevHub, and the rollout surfaces.
• One SLO with an error budget, and the dashboard that shows it.
• On-call that has a roster, a severity definition, and a runbook for RPC stall and validator miss.
• Terraform or Helm for one path that today is a manual rebuild.
• One repeat incident turned into a control, with the review written down.

About Our Organization

Autheo is building a Layer-0 Operating System and an integrated Layer-1 so identity, compute, storage, developer tooling, and AI sit on one network instead of a pile of bridges. Mainnet is live. THEO is trading. Reliability is what keeps that network something a builder can call.

🌐 🚀 WHY JOIN LAUNCH LEGENDS?

• The chain is up. Staking, fees, DevHub, and four verified THEO markets are already public.
• The seat is production. Validators, RPC, and the API path, next to Protocol and Engineering.
• Equity in Launch Legends and Autheo , plus a THEO allocation in a token that already trades.
• 100+ equity cofounders across 25+ countries . Remote. Direct line to the engineering leads and the Managing Directors.