Technical Operations Engineer, Web3 Core Platforms

QuickNodeRemote10 months ago

QuickNode is a cloud-based infrastructure company that powers the blockchain ecosystem.

Our mission is to be the indispensable utility that empowers companies and innovators globally to build next-generation, Web3 enabled businesses & applications using blockchain technology. QuickNode is backed by some of the world's best investors including Tiger Global, Y Combinator, SoftBank, and the Seven Seven Six Fund. The QuickNode team has over 120 people maintaining high performance global data infrastructure for amazing customers serving billions of requests daily.

We are a global remote company with an HQ in Miami, Florida.

Location

Remote (with regional coverage for 24hr operations). Limited travel may be required for conferences or offsites, generally less than 10 days per year.

The Role

Make 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.

What We Actually Need

Linux + Kubernetes: ****you debug real production—networking, storage, rollouts, perf.
IaC (Terraform/Helm/Ansible): you ship repeatable infra, not snowflakes.
Go or Python (plus Bash): ****you 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); you can 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, and 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.
Pace > Ceremony: tight reviews, practical standards, minimal meetings, async‑first.
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

New Hire Onboarding: Week 1-12

Week 1–2: ship a small IaC change + a dashboard someone actually uses.
Week 3–6: own 2–3 chains/subsystems, kill a flaky alert, close a recurring papercut.
Week 7–12: lead one upgrade/cutover with clean rollback; publish an RCA and the code/infrastructure change that prevents recurrence.

The QuickNode compensation philosophy includes pillars to ensure fair and unbiased compensation for all employees. To design and deliver total reward offerings that are employee-centric. To offer a competitive benefit package in all locations where we operate. To prioritize attracting and retaining the best talent globally. To maintain a high-performing and flexible way of working.

During the hiring process, we are committed to discussing compensation openly and honestly. We encourage candidates to share their salary expectations and requirements early, allowing for an individualized discussion. We know that our total rewards practices impact the lives and wellbeing of our employees. Therefore, we will never stop learning about the market, our business, your needs, and how best to achieve our goals through thoughtful and data-driven practices. If you have any questions or require further information about the compensation for this position, please don't hesitate to reach out to your Recruiter.

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.

Apply here 👉 Technical Operations Engineer, Web3 Core Platforms

View all remote jobs at QuickNode →

FAQ

Is the Technical Operations Engineer, Web3 Core Platforms position at QuickNode remote?: Yes. This role was posted on Remote Backend Jobs, a job board that lists exclusively fully remote positions.
When was this Technical Operations Engineer, Web3 Core Platforms job posted?: This listing was posted on October 27, 2025 and is still open for applications.
How do I apply for the Technical Operations Engineer, Web3 Core Platforms position at QuickNode?: Use the apply button on this page — it takes you directly to the employer’s application page.