Studios
We put one senior developer on each project, so you own the whole system, design it directly with the owner who depends on it, and see your work running their business.
You earn a set share of what we bill for your work, agreed before you start, and we tell you the exact figure on the first call. One part-time project already pays well, and most developers settle into two, which is a comfortable living. Our top-performing developers sometimes find they have room for a third project, which is where we cap you out. Our cash pay beats the base salary at most top tech companies. We don’t offer equity, so we won’t pretend the whole package matches theirs, but what we pay is cash, and it lands every month (without a vesting cliff).
The hard problems here aren’t usually pure computer science. You’re not tuning a compiler or scaling a cluster for its own sake; you’re working out how a business actually runs, building the system it depends on every day, and seeing the difference it makes to the people who use it. The engineering is still mission-critical, but it leans on range and plain communication, not depth alone, because you hold the whole problem from the database to the owner you built it for.
And no two projects look alike. One month you’re reverse-engineering forty years of undocumented Visual FoxPro, and the next you’re building a GLP-1 dosing application. Across legacy migrations, spreadsheet-to-app rebuilds, and greenfield platforms for distribution, manufacturing, healthcare, and construction, the work stays varied and none of it is throwaway.
There are no timesheets and no hours to account for. You’re paid for the work itself, so the faster you solve something, the more of your time you keep. We keep meetings to a minimum too, because most of them pull people away from the actual building. The ones we do hold are high-impact, with the owner and the people who depend on the system.
Most of all, you run your own work. Nobody manages your day or hands you tickets, so you make the architectural calls and carry a system from its first decision through to production.
We hire senior, full-stack developers who work remotely from the US, and beyond the resume, the people who do their best work here tend to share four traits.
You’re at home across the front end, the back end, the data, and how it all ships, and you’re comfortable making the call yourself rather than routing every decision through a committee.
When a distributor or a clinic owner describes their problem, you hear the system underneath it, and you can talk it through in plain English they actually understand.
Legacy doesn’t scare you, so you can open a codebase no one has touched in years, work out why it runs, and modernize it without breaking the business that depends on it.
Remote work demands that you’re self-directed, so you set your own pace, you write the tests because you’ll want them later, and you stay accountable without a daily standup.
In exchange you get work that ships and stays in production, and work that keeps you close to the people it’s for. If that trade sounds right, we should talk.
I’m Adam, co-founder and CTO. Send me a note about the work you’re proudest of and why you’re looking right now. You don’t need a cover letter, and you don’t need to dress it up. I read each email myself, and you can expect to hear back from me within 24 hours.