Careers

Developer Bounties

Scoped integration work for Go developers. Build a real production connector, ship within two weeks, get paid on completion.

Workmind builds Operational Agents that automate the operational backbone of growing businesses. We connect the systems companies already rely on and turn operational processes into reliable automated workflows.

We don’t have open staff roles at this time. Instead, we’re launching a paid developer bounty program for scoped integration work.


Developer Bounties

Bounties are for developers who want to build a real, production integration on a defined scope — on their own time, without a long-term commitment.

Each bounty is a UMA integration connector: connecting a third-party platform to UMA so that when an employee is onboarded, given a new role, or offboarded, UMA can automatically provision or deprovision the correct access in that system. A Slack integration, for example, lets UMA assign and remove the right Slack channels and roles based on an approved change in Paycor or BambooHR — without manual IT intervention.

Integrations follow a consistent pattern: implement the API client, map roles to UMA’s access model, handle provisioning and deprovisioning actions, and cover the edge cases. The work is in Go. Each integration is scoped, documented, and specced before any bounty is posted.

Bounties are posted as clients request specific integrations. When a client needs a connector that doesn’t exist yet, it goes on the board. You build the exact thing a real organization is waiting to use.

We expect each integration to take roughly 8 hours of focused work. Each bounty pays $250 on completion.

How it works

1. Review the bounty. Each listing includes a full technical spec, acceptance criteria, and the payment amount — before you commit to anything.
2. Claim it. Only one developer can work a bounty at a time. Once you claim it, a two-week completion window begins immediately.
3. Build and submit. Follow the spec, meet the acceptance criteria, and submit your work before the two-week deadline. Uncompleted bounties at the deadline are released for another developer to claim.
4. Get paid. Payment of $250 is issued once your submission passes review — meaning it meets our code quality standards and is ready to merge into the existing codebase. Before you start, we provide orientation materials and documentation so you know exactly what that bar looks like.

Available Bounties

Coming Soon

We’re finalizing program terms before launching. Bounties will appear in the dropdown below as soon as the program is live.


Program Rules

  • One developer may hold a bounty at a time. Bounties are not shareable or transferable.
  • The two-week window begins the moment a bounty is claimed. Deadline extensions are not granted.
  • All submissions must meet the published acceptance criteria to qualify for payment.
  • Payment is $250 per bounty, fixed. Payment is issued on acceptance — not on submission.
  • To qualify for payment, the submission must meet our code quality and documentation standards and be merge-ready. Orientation materials and documentation covering those standards are provided before you begin work.
  • If a submission is not accepted, Workmind does not retain or use the code. It stays with the developer.
  • Specifications and acceptance criteria are published in full before any claim is accepted.

Could this lead to more?

Workmind’s developer hiring pipeline runs entirely through this program. When we bring on developers full-time or on contract, we look first — and exclusively — at developers who have completed bounties here. It’s how we see how someone actually works, not just how they interviews.

If that’s interesting to you, the bounty program is the starting point.