Four roles on each team
These are volunteer roles for university students in Singapore. You join a small team, take on one brief from a business or charity, and build a system that stays in use after you leave. How the teams run is on the build teams page.
The roles
You do not need to fit a role perfectly. Tell us which one you could actually carry.
Builder
You write the system and the integrations the partner already uses. You should be comfortable reading unfamiliar code, calling APIs you have not used before, and shipping something small early instead of something big late.
AI workflow lead
You own how the agent behaves: prompts, tool use, guardrails, and how the team checks that the output is right. You break a messy human workflow into steps an agent can run, and you say so when a step should stay with a person.
Partner lead
You sit with the business or charity, watch how the work is really done, and turn it into a one-page scope the team can build against. You need clear writing, patience with people who are not technical, and the discipline to turn down features nobody will use.
Documentation and handover
You make sure the partner can keep what the team builds: the one-page runbook, the list of accounts, and a training session for the people who will use it. On small teams this role is often shared with another.
What we ask
One working session a week with your team, plus a few hours on your own, for the whole build cycle. Builds stall when people disappear, so we ask you to commit once you are in.
Your user is a person at a partner organisation, not a marker. Leave behind code the partner can read, a runbook they can follow, and honest notes on what the system cannot do. The roles are unpaid and free to join.
Apply
Tell us who you are and what you are good at. We read every application and reply from williamyang0013@gmail.com before the first build cycle begins.