Site Reliability Engineer

About DexTrending

We sell fixed blocks of time on the Dexscreener trending list. A customer picks twelve or twenty-four hours on Solana or one of six EVM chains, pays once in USDC, pastes a contract address, and the window opens. Behind that is a campaign engine that drives real on-chain volume, transaction count and wallet diversity across the whole window — because those are the three things the board measures, and a bot loop fails all three.

The team is small and remote. Everyone here owns something end to end.

The role

That constraint shapes everything about how this infrastructure is run. Deploys cannot interrupt a running window. RPC failover has to happen inside the retry budget of a single transaction. A queue that backs up for ten minutes is a partial refund, so the alerting has to fire well before that.

You would own the pool of RPC endpoints and their health checks, the job queue that paces campaign activity, the deposit watchers that credit payments, and the observability stack that tells us which of those is degrading. You would also own the incident process, which currently means whoever is awake.

There is real work here in making the system explain itself. Right now, diagnosing a slow window means reading several dashboards and knowing which one lies.

You will be a fit if

• Production ownership of a system with a hard latency budget, not just a uptime target
• Strong Linux fundamentals and infrastructure-as-code — Terraform, Ansible or equivalent
• Practical observability: metrics that answer questions, alerts that are worth waking up for
• Experience running services against third-party APIs whose reliability you do not control

Bonus points

• Having run blockchain node infrastructure, or managed relationships with RPC providers at volume
• LiteSpeed or Apache tuning under sustained load
• An opinion about when Kubernetes is the wrong answer

Compensation

$125k–$170k per year, paid monthly in USD or USDC, whichever you prefer. The range is real: where you land in it depends on experience, and we will tell you which end we are thinking of before the final conversation rather than after.

Location and hours

Fully remote, anywhere. There is no core-hours requirement, but campaigns run continuously and someone has to be reachable when one misbehaves — on-call is shared and compensated, never assumed.

Process

1. Email us. A CV, a repository, or a piece of writing — whatever makes the case.
2. A conversation. Forty-five minutes, two of us, no panel.
3. A technical session. Ninety minutes on a real problem from our backlog, worked through together. Never unpaid homework.
4. Decision. Within three working days, with the reasoning either way.

How to apply

Write to careers@dextrending.net with Site Reliability Engineer in the subject line. Tell us what you would want to own in the first three months. That single paragraph tells us more than a cover letter does.

Posted 11 August 2026 · open until 11 December 2026.