Senior SRE - Blockchain Mainnet, Equity Cofounder (Remote)

Recooty

Cheyenne (WY)

Remote

USD 120,000 - 180,000

Part time

7 days ago

Be an early applicant

Application generator

Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.

Get past ATS filters

Benefits offered by this job

Equity in Launch Legends and Autheo

THEO token allocation

Remote work

Job summary

Launch Legends Inc. (Autheo) seeks a Senior Site Reliability Engineer to own validator, RPC, and cloud operations for Autheo Mainnet. You will manage SLOs, incident response, and a production-grade cloud platform, with equity cofounder status and token allocations.

This is a remote, part-time opportunity with potential for future salaried compensation. Ideal candidates have 7+ years in cloud/SRE, deep AWS and Kubernetes experience, strong observability skills, and a track record running

Qualifications

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.

Responsibilities

Operate validator, sentry, and RPC infrastructure for Autheo Mainnet.
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.
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.
SLOs for the paths that matter: RPC availability, bridge, DevHub API, staking and fee submission.
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.
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.
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.