Senior Engineer, API & Interoperability — Autheo | Live Mainnet, IBC & Bridge APIs

Launch Legends•Cheyenne, WY

2d•Remote

About The Position

Autheo is recruiting a Senior Engineer, API & Interoperability to own the contracts other systems use to reach a chain that is already live. Mainnet has been up since May 14, 2026. It is EVM-compatible and IBC-connected. Staking and fees settle on-chain. THEO moves on Autheo Mainnet, and it already trades on Base and Robinhood Chain. Adevar Labs reviewed the Base to Autheo Mainnet bridge. DevHub is open. The job is the API and message path under that: gRPC, GraphQL, and REST for DevHub and partners; IBC packets and relaying; the bridge surface that already exists; event delivery a dApp can retry. You write Go and Rust. You sit with Protocol and with SRE. SRE owns the hosts, the RPC tier, and the page. You own the schema, the packet, and the failure mode when a message tears. You do not own exchange listings, consensus design, or the grant file. Part-time does not mean advisory. Equity cofounder means you own a surface, you ship the contract, and you review the code next to it.

Requirements

5+ years in protocol or API engineering.
Production Go or Rust, and a second of gRPC, GraphQL, or both. Both languages if you have them.
A bridge, an IBC path, XCM, CCIP, or an equivalent message layer you have operated. Name the chain and the failure.
Distributed systems you can defend: retries, idempotency, timeouts, and a saga or outbox you shipped.
Kubernetes and tracing (OpenTelemetry or equivalent).
Bachelor’s or Master’s in Computer Science, or equivalent practical depth.

Nice To Haves

Cosmos SDK, an EVM client, or a bridge audit you sat through.
SDKs in more than one language, with a stranger able to run the example.
Kafka or an equivalent log, if that is how you delivered events. Not required as a brand.
A public artifact: a spec, a relayer, a crate, or a design doc.

Responsibilities

API contracts: Versioned gRPC and GraphQL for the paths DevHub and partners call: staking, fees, identity, and the Marketplace methods as they land. REST where a caller will not take a stub. Schema evolution, idempotency keys, and backpressure. A breaking change has a version, not a surprise. Go and Rust clients, plus a JavaScript binding DevHub can ship. Python if a partner is already on it.
IBC and the live bridge: IBC channels and relaying against Autheo Mainnet. Packet timeout, ack, and the case where the other chain halts. The Base to Autheo bridge, and the Robinhood Chain path THEO already uses. Name the custody, the signer set, and what Adevar already reviewed before you add a route. Saga or an equivalent durable workflow where a multi-step flow can tear. Name the compensation step.
Events: Logs and transactions out to dApps and DevHub: webhook or stream, idempotency, per-endpoint health, and a latency budget you can show on a trace. Exactly-once only if you can show the dedupe. At-least-once with a key is an acceptable design. A slogan is not.
Reliability of the path you own: Kubernetes deploys, circuit breakers, and retries that match how SRE runs the platform. OpenTelemetry from the API call to the packet. A partner ticket should not require a private log. Benchmarks in CI on the hot adapter. Report what you measured.
Developer surface: Docs and a sandbox so a caller can finish one cross-chain operation without reading the node. Reviews, a short design note, and mentorship of the engineers on the same surface.