Senior Rust developer

Worklo Group

Contact person: David Gomez
New York,  USA
100% remoteAgency contract (e.g. ANÜ)Start date 8/2026Duration 6 months100% workload50,000.00 $ Budget

Description

Worklo is a Professional Services Automation platform for agencies and consultancies — projects, time tracking, capacity planning, workflows, client collaboration, and analytics in one system. Our customers run their entire delivery operation on Worklo, down to what each project costs and what each person is owed. We're now building the layer that turns that compensation data into on-chain payouts.

About the Role
We're introducing an on-chain settlement layer for compensation, and we want to be specific about why — because "put it on a blockchain" usually isn't a real reason.

Worklo already computes what every team member has earned: hours, role multipliers, milestone bonuses, department rules. Paying that out across many recipients each cycle, in stablecoins, with a verifiable and auditable record of who was paid what, is where a contract earns its place. The calculation stays off-chain where the data lives; what goes on-chain is distribution and its guarantees — batch stablecoin transfers, a tamper-evident payment record, and correct handling of the ways a payout can fail.

As a Senior Rust Engineer, you'd own that settlement layer end to end: the on-chain programs and the Rust services around them, plus the Next.js surfaces where operators review and trigger payout runs. Greenfield, real architectural ownership, and the decisions — chain, contract model, upgrade strategy, payment semantics — are yours to make and defend.

Responsibilities
  • Design and implement the on-chain settlement contracts in Rust for batch stablecoin compensation distribution — payment model, failure semantics, and a verifiable payout record
  • Build the Rust services around them: constructing, submitting, and confirming transactions, reconciling on-chain state against Worklo's off-chain compensation data, and handling retries and reorgs
  • Make batch distribution safe against real-world conditions — a single failing or blocked recipient must not brick an entire payout run (pull-over-push where appropriate), and retries must never double-pay
  • Design the boundary between the existing Express.js/Supabase platform and the settlement layer, with clean interfaces, auth passthrough, and clear error propagation
  • Own the operator-facing Next.js pages — payout review, run status, and audit history — using React Server Components and streaming so large runs stay responsive
  • Build observability in from the start: structured logging, metrics, tracing, and health checks across both services and on-chain interactions
  • Write comprehensive tests: unit and property/fuzz tests for the contracts, integration tests for the settlement services against a testnet
  • Work with an independent third-party audit ahead of any mainnet deployment — you build and defend it, someone else signs off on it

Requirements
  • 3+ years of professional Rust, with production experience
  • Real smart contract / on-chain program experience in Rust, and the security instincts that come with irreversible, money-handling code — reentrancy, access control, arithmetic safety, and adversarial account/input validation
  • Understanding of stablecoin (ERC-20 or SPL) mechanics and the failure modes of batch token transfers — non-standard tokens, blocked recipients, fee-on-transfer
  • 3+ years of Next.js/React, including performance-sensitive pages and complex state
  • Comfortable making architectural decisions independently and defending them, including whether something belongs on-chain at all
  • Fluent in English
Nice to Have
  • Solidity/EVM (Polygon, Base, or similar L2s) and/or Solana/Anchor experience
  • Experience with transaction lifecycle handling: confirmation, reorg safety, idempotent submission
  • Familiarity with account abstraction, multisig, or timelock patterns for treasury-grade controls
  • Observability tooling (Prometheus, Grafana, OpenTelemetry)
  • Prior work taking a contract through an external security audit
Why Worklo
  • Greenfield settlement layer with real architectural ownership — no legacy baggage
  • You'd own a money-handling system end to end, with an external audit backing it — not marking your own homework
  • Full depth of the stack: on-chain Rust through to complex React frontends
  • Small team, flat structure, direct impact on what ships
  • Remote-friendly

Application form