Compensation
- Full-time
- $162k–$202k / year
- Part-time
- $95–$115/hr · 15–25 hrs / week
- Advisory
- $950–$1,150/day · 1–4 days / month
15–25 hours a week. Billed hourly.
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.
Own Java services that sit next to the chain — settlement, custody, indexers, and investor APIs — on BrickFi and client products.
This is a backend seat, not a Solidity seat. You write Java services that read and write chain state: confirmations, retries, idempotent settlement, and the APIs product actually calls. Contract engineers own the on-chain logic. You own everything that has to stay correct after the tx lands. Current load includes BrickFi investor and distribution services and client work that needs a JVM shop, not another TypeScript service. You review mid-level backend PRs. You will not be asked to also own the frontend.
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
- Design and ship Java services that talk to EVM or other chains we support: RPC, events, receipts, and reorgs.
- Build settlement, custody-adjacent, or reporting APIs that are idempotent under retries.
- Model confirmations, nonce and key use, and what happens when a node lies or lags.
- Own persistence for positions and payouts so the UI does not scrape RPC.
- Review backend PRs and raise the bar for tests, timeouts, and observability.
- Work with contract and DevOps engineers on ABI changes, deploy order, and runbooks.
- Join client scoping when the work is a Java shop integrating a protocol.
- Leave services another engineer can operate: metrics, alerts, and a written failure mode.
What you bring
- 5+ years production Java (or JVM) backend work.
- You have shipped software that talks to a blockchain — indexer, settlement, custody, payments, or equivalent — not only a CRUD API next to a wallet.
- Comfort with SQL, queues, and at-least-once delivery.
- You can read a Solidity interface or ABI well enough to catch a mismatch.
Nice to have
- Spring or Quarkus
- web3j / web3j-ext
- Kafka or equivalent
- RWA / payments / custody