Upskill, contribute, and build evidence that gets you hired, all while learning about the field.
Thousands of people finish an AI safety intro course every year. The fellowships that pick up where the courses leave off accept roughly 5%. The other 95 stall at the same place: motivated, conceptually trained, no structured way to upskill into actual contribution.
The field needs more contributors. The pipeline to make them barely exists. Mangrove is the missing layer between intro courses and the work itself. Real projects, real teams, real artifacts, in two weeks.
Mangrove is always on. No application deadline. No fixed start window. A team forms when the conditions to do good work are met, and not before.
Real teams need real overlap. The platform respects your timezone and your life.
Members and organizations post ideas. Two buttons that mean different things.
Threshold reached. Schedules overlap. The team forms itself.
First meeting writes the proposal. Roles, deliverables, what done looks like.
Async-first. Weekly check-ins. Decision log captures every pivot. Action items have owners.
Role-anchored ratings. The aggregate becomes your per-role skill graph. Your portfolio.
After a few sprints, your profile is a real piece of evidence, not a self-rated bio. Hiring managers, grantmakers, and collaborators can see the crafts you've built reputation in, anchored to projects you actually shipped, plus an honest record of whether you showed up.
Group projects fail in predictable ways. Vague feedback. Fading motivation. Coordination overhead. No artifact at the end. Mangrove is built around those failure modes so you can spend your time on the actual work.
After each sprint, your teammates rate the role you actually played: Data Wrangler, Project Lead, Comms Lead. You see which crafts you got high marks for, and which ones you're still growing into. No five-star inflation, no vague "great job."
Three teammates and a kickoff on your calendar do more for motivation than any reading list. The work gets done because four people agreed to do it, not because you white-knuckled it alone at 9 PM.
Auto-scheduled meetings into the team's overlap window. One repo, one doc, one channel, threaded together. A decision log that captures every pivot. The platform handles the coordination so the team can focus on the problem.
Every sprint ships something public: a paper draft, a prototype, a memo, a dataset. It lives at a URL you can send a hiring manager, a grantmaker, or a collaborator. No demo day theatrics. Just the work.
Two-week project arc. Async-first, with one or two live check-ins in your team's overlap window. Fits around a job, a degree, a family. Long enough that the artifact matters, short enough that trying is cheap.
Senior researchers and operators opt into weekly check-in slots in their area. Your team gets one or two from someone with the right expertise. They flag a risk, point at the right paper, or ask the question that makes you pivot on Day 5 instead of Day 12.
Sign in. Paint your availability. See what's in the pool. The next team forms when the conditions are right.