Backend Engineering
Backend work here means APIs and data infrastructure that has to actually hold up — under real load, with real clients depending on it, not a demo that only has to survive one presentation.
Go is where we have the deepest experience, but the studio picks whatever fits the task rather than forcing one stack on every project.
What you'd work on
- Design and build APIs — REST or another protocol where it fits better
- Work on schema design, migrations, and query performance, not just endpoints
- Integrate external services: payments, auth, notifications
- Stay on after launch for monitoring and further development
What we look for
- Ownership. You see a task through to done, not just your slice of it.
- Direct communication. You can explain a decision to a client who isn't technical, without hiding behind jargon.
- Craft. You care about the code nobody's reviewing as much as the code everyone sees.
- Curiosity. You pick up a new stack or protocol when the project actually calls for it.
How we work
No layer of managers between you and the client — you talk to them yourself, the same way founders do. We don't run a fixed hiring pipeline: if this role fits how you think, apply below and tell us what you'd actually bring to it.