Responsibilities

• Community & Developer Relations: Be a real presence in our Discord, on Reddit, and on X. Answer the actual technical questions people ask, the kind they post at 1am when a container won’t start. Set the tone for how Vast talks to developers.
• Content & Creator Ecosystem: Produce technical tutorials, example repos, and short videos that show people how to run on Vast; nurture relationships with developer-focused creators who have real audiences.
• Events & Feedback: Run our presence at hackathons, meetups, and conferences; travel when needed; capture and relay product feedback clearly to the team so issues get addressed.
• Product Feedback: You’ll hear what’s broken before anyone else does and get it back to the product team, clearly and often.
• Creator Partnerships: Work with developer-focused YouTubers and other creators, the ones with real audiences rather than bought ones.

Requirements

• You've been an engineer. You can deploy a model and debug someone's setup, and developers can tell you've done the work yourself. This part can't be faked.
• You've built a developer community before, ideally close to from scratch. You know what makes one grow and what quietly kills it.
• You like people more than most engineers do. Writing, posting, talking, showing up at events. That's the actual day-to-day.
• You run yourself. Nobody's going to hand you a content calendar, and you'd rather ship something than sit in a planning meeting about it.

Preferred

• Time at a cloud, GPU, AI-infrastructure, or developer-tools company.
• Something you've made that traveled: a tutorial series people reference, a repo with real stars, a talk that got passed around.
• Working knowledge of the AI/ML stack: model deployment, inference, fine-tuning.

Benefits

• Travel and conference budget covered.