Find people whose skills
cover what yours don’t.
Teams are how a problem becomes work that actually ships. You join one because of what it works on, not because of what it is called — and most projects need more than one.
The core team.
Office bearers for the current term. They set direction and unblock work — the building itself happens in the teams below.
Paridhi Laxkar
Direction of the chapter, and what ACM @ Amity commits to each term.
Vanshika Gupta
Operations, events, and keeping projects moving between sessions.
Harshita Agarwal
Budget, resourcing and everything a project needs in order to run.
Anuansh Tiwari
Technical direction across projects, research and the BuildHub platform.
AI Team
Retrieval, language models and the discipline of knowing when a system is wrong.
We are interested in systems that answer questions from real documents, and in the far harder problem of measuring whether those answers are correct. We prefer a boring pipeline with a known accuracy to a clever one with none.
- AI / LLMAdvanced
Retrieval over real documents
- TestingBeginner
Build the evaluation question set
Weekly working session
6 (demo)
Software Team
Services, data models and the unglamorous engineering everything else depends on.
APIs, storage, scheduling, workflow. We own the parts of a project that have to keep working after the demo. If a design cannot be explained on a whiteboard, it is not finished.
- BackendIntermediate
Replace BuildHub’s demo data with a real store
- DevOpsAny
Deployment and CI for team projects
Weekly working session
8 (demo)
Research Team
Reading carefully, testing honestly, and writing down what we actually found.
We treat a negative result as a result. Membership means reading a difficult paper and presenting it to people who will disagree with your reading. No prior research experience is required — willingness to be wrong in public is.
- ResearchAny
Reading group — the entry point for everyone
- Technical WritingIntermediate
Annotated bibliography and write-ups
Weekly reading group
5 (demo)
Web Team
The surfaces students actually touch, built to a standard we are willing to sign.
Interfaces, performance, accessibility. We care about the 360-pixel screen as much as the 1440. A page that is beautiful and unusable on a phone has failed.
- FrontendAny
Components and interaction detail
- UXBeginner
Empty states, refusals and error copy
Weekly build session
7 (demo)
Design Team
Making complicated systems legible, and holding the line on quality.
We work on information architecture, interface design and the written voice of everything ACM publishes. Design here is not decoration applied at the end — it is the argument about what the thing is.
- DesignIntermediate
Editorial layout and the contribution record
- UXAny
Research and flow design for the Problem Lab
Weekly critique
4 (demo)
Cybersecurity Team
Reviewing what we build before anyone else has to, and learning to attack in order to defend.
We review ACM projects for access control, data handling and privacy before they go anywhere near real data. Everything we do is scoped, consented and documented — that constraint is the discipline, not an obstacle to it.
- SecurityAny
Review track — start by reviewing, not attacking
- ResearchAdvanced
Applied cryptography reading
Fortnightly review
4 (demo)
Not sure which one?
Most people pick a team by picking a project first. Start from a problem that interests you and the team follows from what that problem needs.