Build the tools you
wish existed.
We are a small, remote, independent team building a generative studio for people doing real production work. If that sounds like the job you would do anyway, we should talk.
How we work
Four things that are actually true here.
01
Remote, async-first
Written proposals over meetings. Deep work is the default, not a perk you have to negotiate for.
02
Small scope, real ownership
You will own surfaces, not tickets. That includes the boring parts: the migration, the error state, the docs.
03
Ship, then talk about it
Every release goes in the public changelog. If it is not visible to a user, it is not done.
04
Use what you build
Everyone on the team makes things with the studio. Bad taste in our own product is the fastest thing we catch.
Open roles
Currently hiring.
We keep this list honest — if a role is here, we are reading applications for it. If nothing fits, send us the work you are proudest of anyway.
Full-stack Engineer
Own features end to end across a Next.js front end and a FastAPI service — the studio surfaces, the render queue and the credit ledger behind them.
- Comfortable shipping both React and Python to production
- You have debugged a queue, a race condition and a billing bug, and you have opinions about all three
- You care about what an interface feels like, not only whether it works
Product Designer
Design dense, professional creative tooling: prompt composers, model galleries, result viewers and the small interactions that make a studio feel fast.
- A portfolio with real product work, not only concepts
- You can design in the browser or work fluently with engineers who do
- Strong instincts for typography, spacing and dark interfaces
Support & Community Lead
Be the first human a creator meets. Own the Help Center, keep the AI assistant genuinely accurate, and turn recurring questions into product changes.
- You write clearly and quickly, and you enjoy it
- Hands-on with generative tools — you can answer a prompting question yourself
- Comfortable turning support patterns into documentation and bug reports
Content & Creator Advocate
Make the tutorials, model comparisons and workflow breakdowns that actually teach people something — and bring what you learn back to the roadmap.
- You already make things with generative models every week
- You can shoot, edit and write without a production team
- Allergic to hype; you would rather show the failure cases
How hiring works
- You write to us. Use the contact form and point at work — a repo, a product, a case study, a reel. A short note about why this specific job beats a long cover letter every time.
- A conversation. Forty-five minutes on what you have built and what you want to build next. We will be straight with you about scope, stage and what is hard here.
- A paid exercise. Small, scoped to a few hours, and always paid. It reflects real work from the roadmap — never a puzzle for its own sake.
- Decision, quickly. We aim to close the loop within two weeks of first contact, and we tell you either way.
What we can promise
- Work fully remote, on your own hours, with async-by-default communication.
- Real ownership of a surface, and your name on the changelog entry that ships it.
- Direct contact with the people using what you built — support is a shared responsibility, not a wall.
- A hard no on process theatre: no status meetings that could have been a paragraph.
What we cannot promise
- A big team to hide inside. Roles here are broad and the surface area is wide.
- A finished playbook. Plenty of what we do is being figured out as we go.
- Every question answered on day one. We will always tell you what we do not know yet.
Nothing on the list fits?
Send us the thing you are proudest of and tell us what you would build here. We read all of it.