Compensation
- Full-time
- $168k–$215k / year
- Part-time
- $95–$125/hr · 15–25 hrs / week
- Advisory
- $950–$1,250/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.
Design and implement DeFi primitives: markets, liquidity, yield, and risk — not wrap a fork and call it a protocol.
You understand how AMMs, lending, and vaults fail in the wild: oracle manipulation, leftover approvals, broken invariants, keeper gaps. Clients hire us to survive that, not to redeploy a tutorial vault. You will specify modules, write economic and invariant tests, and document operator runbooks. You work with a security engineer on launch gates. Senior bar: you have shipped or materially contributed to a live protocol other people used with money.
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
- Specify and implement DeFi modules with explicit risk (oracles, liquidations, fees).
- Write economic and invariant tests, not only happy-path unit tests.
- Review oracle, keeper, and bridge integrations before they are “done.”
- Document operator runbooks: who can pause, who can set fees, what happens on a stale oracle.
- Estimate and sequence work so an audit can happen before mainnet.
- Explain tradeoffs to a PM and a non-technical founder without hiding the danger.
- Mentor mid contract engineers on this class of bugs.
What you bring
- Shipped or materially contributed to a live DeFi protocol.
- Deep Solidity and testing (Foundry fuzz/invariants or equivalent).
- You can talk through a historical exploit and what you would have changed in the design.
Nice to have
- Quant or research background
- Restaking
- Keeper networks
- Published postmortems