Location: London preferred; remote okay
Commitment: 4 months, extendable
Compensation: £1,000/month stipend
Start date: ASAP
We are seeking a dynamic and mission-driven Public AI Fellow for a focused four-month engagement to serve as a technical organizer for the larger distributed movement for public AI. If the work goes well, the fellowship may extend. This is a builder-and-coordinator role: part systems thinker, part organizer, part infrastructure engineer for a network that spans the US, UK, and peer efforts around the world.
The public AI movement is growing faster than its shared tooling. People, projects, commitments, and knowledge are scattered across Slack workspaces, docs, calendars, and GitHub orgs. This fellowship invests in new automations and infrastructure that improve coordination and legibility across that network—so the movement can see itself, work together, and scale without becoming opaque.
This isn’t a product-engineering job for one platform. It’s movement technology: the connective tissue that lets a distributed coalition act like one.
You will
- Map and improve the technical stack the movement already relies on—comms, CRM/CMS, knowledge sharing, events, forums, GitHub, websites—and identify where automation or new infrastructure would unlock coordination.
- Design and ship tooling and automations that make the global public AI network more legible: who is working on what, where efforts overlap, what needs attention, and how people find each other across the US, UK, and beyond.
- Work as a technical organizer—translate movement needs into concrete systems, ship iteratively, and bring distributed collaborators along rather than building in isolation.
- Strengthen shared infrastructure that peer organizations can reuse, so local chapters and partner efforts don’t reinvent the same coordination layer.
- Partner closely with Public AI’s engineering and organizing work, and with communities around the London College of Political Technology.
- Document what you build so others can fork, operate, and extend it.
First projects may include
- Regular Slack export → annual and monthly reports → (maybe) live discussion summaries on the site
- Curating the movement’s collective context and provisioning access to it via a RAG or Public AI agent
- Experiments with automatic newsletters
- Helping particular Public AI projects become more autonomous / agentic
- Technical and marketing infrastructure to help college chapters form
- Setting up a forum
- Setting up a movement calendar / calendly / assistant
- Setting up a Pol.is for the community
- Deciding on a triage plan for all the ideas above
- And other coordination and legibility work as priorities emerge
You might be a fit if you have
- Experience building or operating infrastructure for distributed communities, movements, campaigns, or open-source networks—not only shipping features inside a single product org.
- Strong technical instincts and the ability to ship: scripts, automations, lightweight apps, integrations, or ops systems that people actually use.
- Organizer energy—you care about coordination, follow-through, and making messy multi-org work legible.
- Comfort working across time zones and institutional cultures (nonprofits, research labs, civic tech, government-adjacent partners).
- Working familiarity with the public AI / civic tech landscape, or the social intelligence to learn it quickly.
- Bonus if you’ve built CRM, knowledge-base, community-ops, or campaign-tech systems.
- Bonus if you’ve worked in or around London civic technology, political technology, or Newspeak House networks.
- Bonus if you’ve maintained shared infrastructure used by multiple organizations rather than one team.
This is an opportunity to build the technical backbone of a growing international movement at a moment when coordination capacity is the binding constraint. You’ll work with a network of technologists, organizers, policymakers, and public-interest institutions across the US, UK, and beyond.
#J-18808-Ljbffr
