The Role
Make mainnet boring. We launch chains, keep them fast, and fix the stuff that shouldn't break.
What We Actually Need
- Linux + Kubernetes: debug real production—networking, storage, rollouts, perf.
- IaC (Terraform / Helm / Ansible): ship repeatable infra, not snowflakes.
- Go or Python (plus Bash): automate noise away and build small, sharp tools.
- Blockchain operations: JSON-RPC internals; running / tuning RPC / validator nodes; log analysis.
- Observability: SLOs / error budgets, Prometheus / Grafana instrumentation that people use.
- Networking: strong fundamentals (DNS / TLS / LB); reason about anycast / BGP when needed.
What You’ll Do
- Launch & upgrade chains: standups, hard-forks, snapshots, pruning, clean rollbacks.
- Automate everything: modules, golden images, CI / CD, zero-touch deploys across regions.
- Run K8s at scale: safe rollouts, HPA / VS / ingress tuning, capacity & cost plans that hold up.
- Own incidents: lead SEV0-2, publish RCAs, ship the change that prevents a replay.
- Build signal, not noise: SLOs / error budgets, useful dashboards, alerts that only page when users hurt.
- Code 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.
Why This Role Stands Out
- Impact: your work lights up production; chain launches, reliability wins, performance gains.
- Growth: own big surfaces; learn protocol internals while leveling up distributed systems chops.
- Remote‑first: follow‑the‑sun coverage; humane on‑call.
- Compensation & benefits: region‑aligned, bonus‑eligible and shared early; no bait‑and‑switch.
The Bar: Signals We Care About
- Clear production ownership: blast radius understood, rollback plan ready.
- SLO thinking with before / after on alert noise, latency, or MTTR.
- Real RPC / validator ops experience (beyond a laptop demo).
- Tooling / code that made ops better (Go / Python, IaC modules, or a small upstream fix).
- You explain complex failures simply, and leave systems simpler.
- Production experience with one or more of EVM (Geth / Erigon / Nethermind / Besu), Cosmos SDK / CometBFT, Solana (Agave / QUIC), or Substrate.
- Multi‑cloud experience plus capacity & cost modeling that survived contact with reality.
Process
- Steps may vary slightly by region / seniority; we keep it lean.
- 30‑min intro + context with Talent Acquisition.
- 60‑min technical deep dive with the Hiring Manager (incidents you led, K8s / IaC trade‑offs, tooling you built).
- 60‑min hands‑on with Team Members (pair on a small plan / code review or targeted tool fix).
- 30‑min meet a Founder.
We 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.