{"schemaVersion":"jobsearcher.job.v1","id":"70c60ac79c760ad14ee6d0dc","url":"https://jobsearcher.com/jobs/70c60ac79c760ad14ee6d0dc","canonicalUrl":"https://jobsearcher.com/jobs/70c60ac79c760ad14ee6d0dc","title":"Technical Operations Engineer, Web3 Core Platform","description":"The Role\nMake mainnet boring. We launch chains, keep them fast, and fix the stuff that shouldn’t break. You’ll run K8s at scale, ship IaC, lead incidents, and write the tooling that keeps production sane. If you can occasionally patch a client or upstream a small fix, even better.\n\nWhat We Actually Need\n\nLinux + Kubernetes: you debug real production—networking, storage, rollouts, perf.\n\nIaC (Terraform/Helm/Ansible): you ship repeatable infra, not snowflakes.\n\nGo or Python (plus Bash): you automate noise away and build small, sharp tools.\n\nBlockchain operations: JSON‑RPC internals; running/tuning RPC/validator nodes; log analysis.\n\nObservability: SLOs/error budgets, Prometheus/Grafana instrumentation that people use.\n\nNetworking: strong fundamentals (DNS/TLS/LB); you can reason about anycast/BGP when needed.\n\nWhat You’ll Do\n\nLaunch & upgrade chains: standups, hard‑forks, snapshots, pruning, clean rollbacks.\n\nAutomate everything: modules, golden images, CI/CD, zero‑touch deploys across regions.\n\nRun K8s at scale: safe rollouts, HPA/VS/ingress tuning, capacity & cost plans that hold up.\n\nOwn incidents: lead SEV0–2, publish RCAs, and ship the change that prevents a replay.\n\nBuild signal, not noise: SLOs/error budgets, useful dashboards, alerts that only page when users hurt.\n\nCode where it counts: write/extend tools (snapshots, replay/load, state sync checks); occasionally patch client bugs that bite production and upstream when it’s worth it.\n\nWhy This Role Stands Out\n\nImpact: your work lights up production; chain launches, reliability wins, performance gains.\n\nPace > Ceremony: tight reviews, practical standards, minimal meetings, async‑first.\n\nGrowth: own big surfaces; learn protocol internals while leveling up distributed systems chops.\n\nRemote‑first: follow‑the‑sun coverage; humane on‑call.\n\nCompensation & benefits: region‑aligned, bonus‑eligible and shared early; no bait‑and‑switch.\n\nThe Bar: Signals We Care About\n\nClear production ownership: blast radius understood, rollback plan ready.\n\nSLO thinking with before/after on alert noise, latency, or MTTR.\n\nReal RPC/validator ops experience (beyond a laptop demo).\n\nTooling/code that made ops better (Go/Python, IaC modules, or a small upstream fix).\n\nYou explain complex failures simply, and leave systems simpler.\n\nProduction experience with one or more of EVM (Geth/Erigon/Nethermind/Besu), Cosmos SDK/CometBFT, Solana (Agave/QUIC), or Substrate.\n\nMulti‑cloud experience plus capacity & cost modeling that survived contact with reality.\n\nWe at Quicknode are an equal opportunity employer and all qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity or expression, pregnancy, age, national origin, disability status, genetic information, protected veteran status or any other characteristic protected by law.\n\n#J-18808-Ljbffr","company":"Quicknode","rawCompany":"quicknode","city":"Doral","state":"FL","isRemote":false,"isActive":false,"createdAt":"2026-04-19T03:06:34.100Z","occupations":[{"code":"15-1299.08","title":"Computer Systems Engineers/Architects","slug":"computer-systems-engineers-architects"},{"code":"15-1244.00","title":"Network and Computer Systems Administrators","slug":"network-and-computer-systems-administrators"},{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"}],"industries":[{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Technical Operations Engineer, Web3 Core Platform","description":"The Role\nMake mainnet boring. We launch chains, keep them fast, and fix the stuff that shouldn’t break. You’ll run K8s at scale, ship IaC, lead incidents, and write the tooling that keeps production sane. If you can occasionally patch a client or upstream a small fix, even better.\n\nWhat We Actually Need\n\nLinux + Kubernetes: you debug real production—networking, storage, rollouts, perf.\n\nIaC (Terraform/Helm/Ansible): you ship repeatable infra, not snowflakes.\n\nGo or Python (plus Bash): you automate noise away and build small, sharp tools.\n\nBlockchain operations: JSON‑RPC internals; running/tuning RPC/validator nodes; log analysis.\n\nObservability: SLOs/error budgets, Prometheus/Grafana instrumentation that people use.\n\nNetworking: strong fundamentals (DNS/TLS/LB); you can reason about anycast/BGP when needed.\n\nWhat You’ll Do\n\nLaunch & upgrade chains: standups, hard‑forks, snapshots, pruning, clean rollbacks.\n\nAutomate everything: modules, golden images, CI/CD, zero‑touch deploys across regions.\n\nRun K8s at scale: safe rollouts, HPA/VS/ingress tuning, capacity & cost plans that hold up.\n\nOwn incidents: lead SEV0–2, publish RCAs, and ship the change that prevents a replay.\n\nBuild signal, not noise: SLOs/error budgets, useful dashboards, alerts that only page when users hurt.\n\nCode where it counts: write/extend tools (snapshots, replay/load, state sync checks); occasionally patch client bugs that bite production and upstream when it’s worth it.\n\nWhy This Role Stands Out\n\nImpact: your work lights up production; chain launches, reliability wins, performance gains.\n\nPace > Ceremony: tight reviews, practical standards, minimal meetings, async‑first.\n\nGrowth: own big surfaces; learn protocol internals while leveling up distributed systems chops.\n\nRemote‑first: follow‑the‑sun coverage; humane on‑call.\n\nCompensation & benefits: region‑aligned, bonus‑eligible and shared early; no bait‑and‑switch.\n\nThe Bar: Signals We Care About\n\nClear production ownership: blast radius understood, rollback plan ready.\n\nSLO thinking with before/after on alert noise, latency, or MTTR.\n\nReal RPC/validator ops experience (beyond a laptop demo).\n\nTooling/code that made ops better (Go/Python, IaC modules, or a small upstream fix).\n\nYou explain complex failures simply, and leave systems simpler.\n\nProduction experience with one or more of EVM (Geth/Erigon/Nethermind/Besu), Cosmos SDK/CometBFT, Solana (Agave/QUIC), or Substrate.\n\nMulti‑cloud experience plus capacity & cost modeling that survived contact with reality.\n\nWe at Quicknode are an equal opportunity employer and all qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity or expression, pregnancy, age, national origin, disability status, genetic information, protected veteran status or any other characteristic protected by law.\n\n#J-18808-Ljbffr","datePosted":"2026-04-19T03:06:34.100Z","dateModified":"2026-04-19T03:06:34.100Z","hiringOrganization":{"@type":"Organization","name":"Quicknode","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Doral","addressRegion":"FL","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"70c60ac79c760ad14ee6d0dc"},"url":"https://jobsearcher.com/jobs/70c60ac79c760ad14ee6d0dc"}}