Community Manager

Responsibilities

• Develop and deliver a practical community plan focused on adoption of, participation in and contribution to Scenario Builder’s open core, aligned with TransitionZero’s open-source strategy. Understand the needs of different user and contributor groups through direct conversations, observed activity and feedback.
• Build on the existing community channels and relationships, using targeted outreach and thoughtful onboarding to attract people who will benefit from and contribute to the community. Establish clear community guidelines, constructive discussion practices and dependable coverage. Develop relationships with relevant practitioner, research and open-source networks in coordination with the Head of Market Development.
• Manage day-to-day community activity, ensuring that questions receive a useful response or clear triage within the agreed one-UK-working-day response norm. Coordinate specialist input through agreed routes, provide sufficient context for colleagues to respond efficiently, and keep users informed as questions progress.
• Turn recurring questions and expert answers into durable resources, including FAQs, how-to guides, worked examples and learning materials. Work with technical colleagues to check accuracy and keep resources current. Protect confidential models, data and account information, and direct sensitive requests to appropriate private channels.
• Run a repeatable engagement programme of webinars, community calls, demonstrations and contributor sessions, choosing formats that respond to real user needs and available capacity. Attend and speak at relevant in-person open-source and energy events, including forums such as LF Energy, to build relationships and attract users and contributors to the open-core community.
• Coordinate speakers, technical input, invitations, facilitation and follow-through. Make recordings, answers and other useful outputs accessible after events so their value extends beyond the live session.
• Work with Marketing and Communications and Product to share approved updates, useful examples and community stories. Help members understand what is available, how it can support their work and what practical step they can take next.
• Identify and support users who can become peer mentors, community champions and external contributors. Create accessible routes for people to contribute through documentation, examples, testing, issue reporting, and, where appropriate, models, data and code.
• Work with Engineering and project maintainers on contributor onboarding, contribution guidance and suitable entry points as open-source components become available. Help prospective contributors understand the relevant processes and expectations, recognise their work, and support their continued involvement.
• Coordinate community readiness for releases while keeping technical acceptance, release decisions and public commitments aligned with the responsible teams.

Requirements

• A demonstrable track record of building or developing a software, developer, open-source, scientific or comparably technical community, with evidence of sustained participation and useful contributions.
• Experience owning a community programme from planning through hands-on delivery, including prioritisation, member engagement, moderation and measurement.
• Excellent written communication and facilitation skills, with the ability to turn specialist input into clear guidance, useful discussions and accessible learning resources.
• Sufficient technical fluency to learn a complex software product, understand user workflows, ask informed questions and distinguish routine support needs from issues requiring specialist input.
• Experience enabling peer learning and contributions, including working with technical teams on documentation, issue reporting or contributor workflows.
• Strong organisational judgement and the ability to work across functions, cultures and time zones, manage expectations, handle sensitive information appropriately and follow through reliably.

Preferred

• Experience in energy, climate, scientific computing, data or analytical software, particularly with users in emerging markets and developing economies.
• Practical familiarity with GitHub Issues, Discussions, documentation and contribution processes, alongside community platforms and engagement analytics.
• Experience developing community champions, supporting an open-source release, or measuring how community participation contributes to product adoption and retention.
• Deep software engineering or power-system modelling expertise is not required. You should be able to develop a strong working understanding of the tools and collaborate credibly with the people who build and use them.