Lootrushs
Lootrushs engineering team

Engineering

Blockchain DevOps Engineer

Keep nodes, indexers, relayers, and deploys healthy when the chain gets noisy.

← All roles
Full-timePart-timeAdvisoryMidRemoteRPCs · Kubernetes · CI

Compensation

Full-time
$128k–$164k / year
Part-time
$75–$95/hr · 15–25 hrs / week

15–25 hours a week. Billed hourly.

Advisory
$750–$950/day · 1–4 days / month

Day rate for reviews, working sessions, and office hours. Typical cadence is 1–4 days a month. A monthly retainer is an option in the offer.

All figures are USD cash, remote, with US Eastern overlap. Location and the client brief can move the number. Token or equity only appears if that client has it.

Keep nodes, indexers, relayers, and deploys healthy when the chain gets noisy.

You own merge-to-mainnet: CI, deploy keys, RPC strategy, and on-call dashboards. We are a studio, not a 24/7 trading firm, but we have keepers, relayers, and client mainnets. You share on-call for production protocols with the engineer who wrote the module. Rotations are written down. We do not page you for a marketing-site outage. Kubernetes is useful; chain-specific ops is the job.

How hiring works

Roles are posted by Lootrushs as full-time, part-time, or advisory — pick one on the form. We source, screen, and interview — or a client introduces a candidate to us. After you pass our process, you may interview with the client company. If both sides agree, you join through Lootrushs and work on that client’s product.

What you will do

  • Run CI for contracts and dApps, including fork tests and preview deploys.
  • Operate RPCs, indexers, bots, and relayers.
  • Instrument logs, traces, and on-chain alerts (failed keepers, stalled subgraphs, unusual admin txs).
  • Secure secrets and signer infrastructure; no keys in chat.
  • Run deploy playbooks: hardware wallet or multisig, dry run, then mainnet.
  • Write the runbook the next person on-call actually follows.
  • Keep staging and prod from drifting without a PR.

What you bring

  • Production DevOps or SRE.
  • At least one chain’s node, RPC, or indexer stack you have operated when it was broken.
  • Comfortable with GitHub Actions (or similar) and Linux.

Nice to have

  • Foundry CI
  • Tenderly or Defender
  • SOC2
  • Kubernetes you did not only tutorial