Get Involved
Learning and collaboration before titles.
These are contribution roles, not jobs — none of them come with a salary, and it is better to say that in the first line than the last. What they do come with is published work, real code review, and a network of people who ship.
Where help is needed
Six ways in.
Your own pace
Open-source contributor
Fix what breaks, improve what is unclear, or add the example that was missing. The repositories are public and the issues are real.
A good fit if
- You have shipped Python and can read someone else's code
- You would rather send a PR than an opinion
Project-based
Research collaborator
Take on one of the open research problems — routing, legacy modernization, neuro-symbolic autonomy. Joint publication where the work earns it.
A good fit if
- You can design and run an experiment
- You have a dataset, a domain, or a deployment nobody else has
Per event
Workshop facilitator
Help run hands-on sessions on campuses and at conferences — debugging in the room while someone else teaches from the front.
A good fit if
- You are comfortable fixing someone's environment under time pressure
- You are based near a city where we run events, or happy online
A few hours weekly
Community moderation
Keep Discord useful: answer what you can, route what you cannot, and hold the Code of Conduct.
A good fit if
- You are already active in the community
- You are patient with beginners on their fifth question
Per piece
Content and technical review
Read tutorials and course material before publication and find the step that does not actually work.
A good fit if
- You are the person who always spots the missing import
- You will run the code rather than skim it
Ongoing
Academic partnerships
Connect us with departments running AI programs, and help shape what campus workshops cover.
A good fit if
- You teach, study, or work inside an institution
- You know what a syllabus committee actually needs
What it is like
Co-building, not staffing.
Contributors describe the same two things: it keeps them current in a field that moves weekly, and it puts them next to people whose work they would otherwise only read. Several have gone on to publish, to speak at conferences, or to start their own companies out of it.
What we ask in return is honesty about capacity. Contributing nothing for a month is fine. Saying you will own something and then disappearing is what actually costs the community.
Read the Code of Conduct →FAQ
Before you get in touch
Are these paid positions?
No. These are contribution and collaboration roles, not employment — nothing on this page comes with a salary, and we would rather say that plainly than waste your time. Paid delivery work on client engagements is arranged separately and case by case.
What do contributors actually get out of it?
Published work with your name on it, open-source contributions that are visible to anyone reviewing you, co-authorship where the research earns it, speaking and judging opportunities, and access to a network of engineers who ship. Several contributors have used it as the springboard for their own ventures.
How much time does it take?
Whatever you have. Open-source contribution is entirely self-paced; moderation is a few hours a week; facilitation is per event. The one thing that does not work is committing to something ongoing and then going quiet — say what you can actually sustain.
Do I need to be in India?
No, except for on-campus facilitation. Everything else is remote, and contributors are spread across timezones.
I am a student. Is that a problem?
It is not. A good share of contributors are students, and the research problems in particular suit a thesis. Get in touch early so scope can be cut to fit a semester.
How do I apply?
There is no application form. Send a note through the contact form saying which area interests you and what you would bring — or skip that entirely and open a pull request. A merged PR says more than any application.