You will be the bridge between the engineering team and the non-profits/social sector orgs who need to discover, understand, and adopt the product. You own everything from the first Google result someone sees to the community conversation that turns them into a user/contributor.

What you'll own: 1. Documentation: Docs should be written like a tutorial, not a reference manual. It should guide the reader through understanding key concepts within AI evals and the best practices to be followed, while showing them how Calibrate can help them do that. The end user should feel they learnt something by reading the docs (e.g. Pipecat docs). Keep the docs up-to-date and helpful by using simple language over jargon, easily understandable screenshots, worked examples, and clear narratives. 2. Demo videos & product content: Create and maintain short product demo videos showcasing features. Update them as the product evolves. 3. Content & thought leadership: Take rough brain dumps from the builders and turn them into polished posts. Topics span releasing public benchmarks for different Indic language use cases, showcasing new features, sharing latest AI eval best practices, use-case deep dives, sharing AI agent evaluation research relevant for non-profits in a digestible way, and more. 4. Community management: Run the WhatsApp community, answer questions thoughtfully, surface bugs/feedback to the team, keep conversations alive, and make users feel heard. 5. Events & workshops: Plan and execute community sessions, webinars, and workshops end-to-end. Handle logistics, promotion, invites, and follow-ups so that the builders can just show up and speak. 6. Marketing & distribution: Get Calibrate in front of the right people: non-profits and social-sector teams building AI agents who need to evaluate and improve them before deploying to real users. Think Product Hunt launches, HN posts, dev community cross-posts, conference CFPs, and presence in AI-for-good and civic tech circles.

1. Have 1–3 years in developer relations, developer marketing, or technical content for dev tools / open-source projects 2. Can write clean technical prose and are comfortable with CLIs, APIs, and YAML configs 3. Have created product demos or technical walkthroughs (video or written) 4. Have managed developer communities (Discord/Slack/forums) 5. Are self-directed and don't wait to be told what to post or when to update docs 6. Have a basic understanding of how LLMs work or show the ability to learn quickly during the interview process 7. Bonus: A deep understanding of the challenges with evaluating AI agents through projects/experience building real AI products