寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 6,472

← 返回搜索结果

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

Autheo

地点
Anywhere
发布日期
2026年10月6日

申请前,请在雇主网站确认职位仍在招聘,并检查完整要求和条件。

职位描述

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

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 — https://www.autheo.comTHEO token launch & verified markets — https://www.autheo.com/token-launchDocs — https://docs.autheo.comAutheo Team — https://www.autheo.com/teamsLaunch Legends (Parent Company) — https://www.launchlegends.ioX / Twitter — https://x.com/Autheo_Network 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: 0xebE516a20238F79dc20b07eaD6768e08891Ed309THEO/USDG on Uniswap v3 (Robinhood Chain) — live since September 10, 2026THEO/NVDA on Uniswap (Robinhood Chain) — live since September 24, 2026. Official Robinhood Chain contract: 0x3dc751e0da01812e6d9143cc696e7f07ea94da48 Verified trading links, contract addresses, and network information: https://www.autheo.com/token-launch 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 Mainnet and RPCOperate 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. Cloud platformProduction 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. ReliabilitySLOs 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. ObservabilityMetrics, 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. Security and keysKMS 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.

查找职位、比较要求,再准备申请

从你希望从事的职位或运用的技能开始搜索。调整地点和职业筛选,打开职位比较工作职责。如果没有结果,可以使用更短的关键词,或逐一移除筛选条件。

区分必备要求和优先条件,检查已列出的工作安排、薪资和地点。远程职位也可能要求特定居住国家、工作许可或工作时间重合。请向雇主确认职位信息和完整条件。

选择能够回应职位要求的真实经历,说明你的贡献,只使用能够证实的数字。遵循雇主的申请说明,并在提交前检查联系方式、文档内容和 PDF。

提交申请前的检查清单

求职常见问题

为什么有些职位使用英文?

职位名称和描述由招聘企业撰写。为避免改变招聘要求或工作条件,我们保留原文。操作界面和本指南使用简体中文。如果中文搜索没有结果,可以尝试使用职位发布语言中的名称或技能,例如“software engineer”。搜索词不会自动翻译,界面语言也不代表企业要求的申请语言。

远程职位是否允许从任何国家工作?

不一定。企业可能对居住国家、工作许可或工作时段有要求。请查看原始招聘页面中的具体条件。如果未说明,应先向企业确认,再判断能否从你所在的地区工作。“远程”标签本身并不代表没有地点限制。

搜索没有结果时应该怎么办?

尝试更通用的职位名称或单个技能,并逐一移除筛选条件。不同企业可能用不同名称描述相似工作。如果某个职位已经消失,请在企业招聘页面搜索其职位编号。扩大搜索范围不会让已经关闭的职位重新开放。

申请会通过 ResumizeAI 直接提交吗?

申请按钮会打开外部网站。请按照企业或招聘服务的说明,在该网站完成并确认提交。在 ResumizeAI 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。