Build the shipping layer for on-chain commerce.
We're a small team. We hire deliberately and only when a role unblocks something concrete. If that sounds like the kind of company you'd like to join, read on.
How we work
We ship the boring parts well
Idempotency, refunds, signed webhooks, server-authoritative pricing. The reason customers stay is that none of these break at 3am.
Small surface area, sharp tools
We pick a small set of tools (TypeScript, React, Postgres, OpenAPI) and master them. Resume-driven architecture is not a value here.
Async by default, kind in writing
Most decisions happen in writing so anyone, in any timezone, can catch up without a meeting recap.
Open roles
We don't have any open roles right now. We do keep a short list of folks we'd love to talk to when budget opens up.
Send a short intro to billy@goatlabels.ioRemote-first, compatible with US / EU working hours.
How we hire
Roles open when a concrete piece of work needs an owner, not on a headcount plan. When one does, it is posted on this page first, with the problem it exists to solve, the stack it touches (TypeScript, React, Postgres, OpenAPI) and the time-zone overlap it needs. We do not run evergreen listings.
The process is short and in writing, the same way we work. A short intro by email, a written exchange about a real problem from our backlog, then a short, time-boxed exercise or a working session with the people you would ship with. Each step ends with a clear yes or no and the reasons.
Work is remote-first. Most of the team overlaps US and EU working hours, so we ask for a few hours of overlap with one of those windows rather than a fixed location. Engineering, support and operations are the role families we expect to hire into as the product grows.
What we offer
- Remote-first across compatible time zones
- Equity in an early-stage company you can actually shape
- Hardware budget and a real coworking stipend
- Generous PTO with a documented minimum, not just a maximum