Project Manager · Contributor Community

Remote (UK / US)  ·  Full-Time  ·  Mid–SeniorABOUT WORLDMODELDATAWorldmodeldata is building critical data infrastructure for the next generation of AI. We work with frontier AI labs and operate a platform that spans data collection, processing, and delivery at scale. Strategically advised by Prof. Yann LeCun. We are lean, well-funded, and operating at high speed.THE ROLEWorldmodeldata's data platform depends on an active, reliable community of external contributors — the people who supply the raw data our pipeline processes and our AI team trains on. This role owns that community entirely: recruiting contributors, onboarding them, keeping them engaged, and making sure their output stays on track. Your primary metric is simple: contributor hours produced per week. Everything else — communication cadences, onboarding quality, issue resolution speed — exists in service of that number. You will be measured on whether the contributor supply is growing, consistent, and healthy.This is not a passive community management role. You will run structured onboarding for new contributors, proactively identify contributors and be the first point of contact when contributors have questions or hit problems. When those problems are technical — an issue with the desktop application or the platform — you do not need to solve them yourself. You will work closely with the Senior Full-Stack Engineer (Contributor Success) who handles the technical side; your job is to triage accurately, communicate clearly, and make sure the contributor stays informed until the issue is resolved.WHAT YOU WILL OWNContributor Pipeline & OnboardingEnd-to-end onboarding of new contributors — from initial contact through account setup, platform orientation, and first successful data submissionMaintaining a pipeline of prospective contributors — identifying, recruiting, and qualifying candidates who meet our contribution requirementsDesigning and improving the onboarding process over time to reduce time-to-first-submission and support burdenCommunity Management & EngagementPrimary point of contact for the contributor community — managing inbound questions, issues, and feedback across all communication channelsProactive outreach to contributors who are inactive or underperforming — diagnosing the cause and re-engaging themRegular contributor communications — announcements, software update notices, platform changes, and recognition of top contributorsBuilding and maintaining a contributor knowledge base: FAQs, setup guides, and troubleshooting documentation that reduces repetitive inbound queriesOutput Tracking & ReportingTracking contributor output metrics weekly — hours produced, active contributor count, submission rates, and drop-off pointsReporting contributor community health to the management team: what is working, what is not, and what is needed to hit targetsFlagging systemic issues — patterns in drop-off, recurring technical complaints, or process bottlenecks — to the relevant teamSKILLS & EXPERIENCECommunity & Operations3+ years of experience in community management, partner operations, or a similar externally-facing operational roleProven track record of managing a contributor, creator, or supplier community with measurable output targetsStructured approach to onboarding: you document processes, iterate on them, and measure whether they workComfortable managing a high volume of contributor relationships simultaneously without losing individual contextCommunicationExcellent written communication — you can write clearly for a non-technical audience, adapting tone and register to the situationComfortable delivering difficult messages: telling a contributor their output is insufficient, or that a technical issue will take time to resolveExperience maintaining community documentation — guides and FAQs that are genuinely useful, not just written once and forgottenTechnical LiteracyYou do not need to be an engineer, but you need enough technical comfort to understand the problems contributors face with a desktop application — to gather the right information, describe the issue clearly to an engineer, and explain the resolution to a non-technical userFamiliarity with support tooling (Intercom, Linear, Notion, or similar) to manage contributor issues and track resolutionFamiliarity with video games industry or at least actively playing video gamesWHAT WE LOOK FORYou think of contributor output as a supply chain metric — when it dips, you want to know why before anyone has to askYou are proactive by default: you do not wait for contributors to come to you with problems; you spot early signals and act on themYou can hold a professional, responsive relationship with a large and diverse contributor base without letting quality slipYou understand the difference between a technical issue and a motivation issue — and you know which one to escalate and which one to solve yourselfNICE TO HAVEExperience working with a geographically distributed or remote-first contributor or creator communityBackground in game community management, operations, supply chain, or marketplace management — thinking about contributors as a supply side comes naturallyExposure to a technical product where users interact with installed software, not just a web interface