Cloud Studios is two people building real products end to end - design, engineering, and product decisions in the same hands. Joining means direct ownership of a feature from an unclear problem through to release, not a rotation through tickets nobody senior wanted. No roles are open right now, but speculative applications that make a specific case are still read.
The studio is deliberately small: two people, one product at a time, no headcount added before there's work for it. There are no handoffs between a design team and an engineering team, because there are no separate teams - the person who decides how a screen should feel is the person who builds it.
Work ships early and gets revised in public, based on what people actually do with it, not on a roadmap written months earlier. Anyone who joins is close enough to see decisions get made, not just execute them.
Roles change as the studio's priorities do, but the shape of the work stays the same: take something from an unclear problem to a shipped feature, watch what happens when people use it, and improve it from there. You'll work directly with the founder, not through a manager relaying someone else's decisions.
No specific degree or background is required. People here have come from product, design, engineering, business, and fields with nothing to do with software. What matters is that you've built something and can show it, that you'd rather test an idea than debate it, and that you take ownership without waiting to be told what's next.
The studio is early. As it grows past its first products, the team grows with it - including full-time, paid roles. Strong work here is the clearest way in.
Roles at the studio are one track. The other is theCloud Studios Founder Residency: a paid venture-building residency for people who want to discover, validate and build a company of their own, then spin it out and lead it. It's a separate thing from the roles on this page, with its own application.
Email hello@cloudstudios.online directly. No form, no portal, no account to create. Do not send a generic cover letter - it's the fastest way to be passed over. Send:
Applications are read by the founder, not by software. Expect a reply within two business days.
No roles are open right now. The studio still reads speculative applications, and a strong one can create a role that was never planned, so the bar is higher than for a posted role, not lower. Send everything listed under How to apply, plus the part that decides it: the product you would work on, the first thing you would change about it, and why you would be the one to do it. An email asking to be kept in mind for anything that comes up gets nowhere, because there is nothing in it to say yes to.
No. There are no open roles at the moment. The studio still reads speculative applications, and a strong one can create a role that was never planned, so the bar is higher than for a posted role, not lower. Say what you would work on, the first thing you would change about it, and why you would be the one to do it.
No. The studio hires from product, design, engineering, business, and other backgrounds entirely. What matters is that you've built something and can show it.
No. The studio works in English. German is useful for some roles, like dealing with German universities or social content, but it isn't required.
No. There's no intern programme, no cohort, and no rotation. You work directly with the founder from day one, on whatever the studio is actually shipping.
There isn't a fixed one. Priorities shift with what's shipping, and a two-person studio has no queue of tickets nobody senior wanted. What you work on is real and visible immediately.
There is no guarantee, but strong work can lead to an ongoing role as a working student, or a Venture Associate position as the studio grows.
The founder reads every application personally: there's no recruiter and no applicant-tracking system. What you've built matters more than your CV.