Lootrushs
Lootrushs engineering team

Engineering

Smart Contract Engineer

Implement and test production Solidity — tokens, vaults, staking, and BrickFi issuance — with Foundry, not tutorial repos.

← All roles
Full-timePart-timeAdvisoryMidRemoteSolidity · Foundry

Compensation

Full-time
$142k–$178k / year
Part-time
$80–$105/hr · 15–25 hrs / week

15–25 hours a week. Billed hourly.

Advisory
$800–$1,050/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.

Implement and test production Solidity — tokens, vaults, staking, and BrickFi issuance — with Foundry, not tutorial repos.

You join a protocol pod with a senior contract engineer and whoever owns the dApp. Typical work is a specified module: access control, events, tests, a deploy script, and an ABI frontend can use. We use Foundry. PRs that merge without tests or without a note on upgrade and admin powers get bounced. You do not need to have led an audit. You do need a public network you have shipped to. First projects are likely a BrickFi module or a client vault/staking piece.

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

  • Implement contract modules for BrickFi (share token, distribution, allowlists) and client protocols.
  • Write Foundry unit, fork, and invariant tests for the code you own.
  • Document admin roles, pause paths, and what happens if a keeper misses a window.
  • Gas-review your own diffs before asking for a senior look.
  • Help frontend with ABIs, events, and expected revert reasons.
  • Join testnet and mainnet deploys for the modules you wrote.
  • Read OpenZeppelin and our internal patterns before inventing a new access-control story.
  • Leave a changelog and a threat note on every module that can move funds.

What you bring

  • 2+ years professional software, including Solidity in production. A public explorer link helps.
  • Daily fluency with Foundry or Hardhat: tests, forks, scripting.
  • You can explain how you would upgrade, pause, or migrate a live contract.
  • Clear written English for PRs and client notes.

Nice to have

  • An audit you participated in
  • ERC-4626, 3643, or 1155 in production
  • TypeScript deploy scripts