Responsibilities

• Bespoke program design. Conceive and run the formats that work for frontier-lab audiences: topical dinners, paper discussions, intimate researcher-to-researcher working sessions, focused workshops on data development and post-training. Most of these don't exist yet (you're inventing them!). Develop the discussion frames, agendas, pre-reads, and seating that make a gathering feel high-signal.
• Recruit the right room. Know who's working on what at which lab. Reach the right people 1:1 through outreach, mutual connections, and showing up where they already are. The room makes the program.
• Hackathons and technical activations. Evaluate, design, and run hackathons, evals jams, or similar technical formats where Snorkel's work on data shows up naturally rather than as a sponsor pitch.
• Champion and advocate development. Identify the most engaged researchers and lab operators, deepen those relationships, and develop them into speakers, contributors, and trusted voices who help shape what we do next.
• Editorial and social presence. Represent Snorkel in the channels where this community actually lives — X, TBPN-adjacent corners of the internet, technical Substacks, Discords, GitHub. Amplify community members' work and surface what they're talking about.
• Researcher feedback loop. Bring what the community is debating, frustrated by, and excited about back into product, research, and marketing. You are how Snorkel listens to this audience.
• Test, measure, iterate. Run programs as experiments. Track the right signals — return attendance, depth of conversation, follow-up meetings, downstream relationships and pipeline. Retire formats that aren't earning their keep.

Requirements

• 3–5 years of experience in community, developer relations, technical event programming, experiential marketing, or similar roles aimed at technical audiences (researchers, engineers, or sophisticated technical operators)
• Prior experience running hackathons or technical jams; existing relationships in the SF AI/research community; technical fluency to read papers and structure programming around them.
• A track record of building or growing a community/program from scratch — examples might include running a meetup that grew into a recurring fixture, producing executive or researcher dinners that people came back to, building a developer community around an AI/ML or infrastructure product, or running a successful hackathon series
• Strong taste for what makes a technical event feel high-signal versus a sponsor-driven slog, and clear views on the difference
• Comfort and credibility with researchers and AI lab employees — you don't have to be one, but you need to read the room, recognize what matters to this audience, and earn trust quickly
• Excellent written and verbal communication, especially in 1:1 outreach — your DMs and emails need to land with people who get a lot of pitches
• Self-direction and ownership — you're comfortable building the strategy as you go and managing your own pipeline of programs end-to-end
• Familiarity with CRM tools (Salesforce or equivalent) and a habit of tracking what your programs produce
• Genuine interest in AI and a desire to be part of a company shaping how frontier labs and enterprises put it to work