About the role
People find CloudCrane where they find tools for their assistants: Claude's connectors directory, ChatGPT, the MCP registries and directories. We're listed in several already; what each listing says, and how well it reads, is the first job.
After that, you'll find the first communities where "ask your assistant for an app" lands, and measure what matters: how many apps a person makes, and whether they come back after two weeks.
What you'd do
- Own the directory listings and keep them accurate as the product changes
- Find and test the first channels and communities
- Write the website and launch copy with the product team
- Measure what people do after they connect, and report it plainly
What we need
- Four or more years in growth or marketing for a consumer or developer product
- You've launched something from nothing and can show what worked and what didn't
- You write clearly, and you won't overclaim
Nice to have, not required
- You've marketed a developer tool, an AI product or an app platform
- Community building
How we work
- Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
- Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by someone using it.
- Private by default. A person's app data stays on their phone, and nothing we build may need to read it.
- We only claim what ships. That applies to the product, the roadmap and the offer letter.
How hiring works
- 1A 30-minute call about something you've built and what was hard about it.
- 2A working session on a real problem from this codebase. You can drive, or we can pair.
- 3A conversation about how you make decisions when the evidence is thin.
- 4References, then an offer. We aim to answer within a week at every stage.
