← Latest papers
💻 computer science

TeamUp: Semantic Project Matching and Team Formation for Learning at Scale

The paper introduces TeamUp, a lightweight, embedding-based system that leverages semantic matching and hybrid ranking algorithms to automatically form cognitively diverse student teams and align them with appropriately challenging projects, thereby significantly improving match quality, equity, and learning outcomes in large-scale project-based courses.

Original authors: Dhruv Gulwani, Basem Suleiman, Aditya Joshi, Sonit Singh

Published 2026-05-06
📖 4 min read☕ Coffee break read

Original authors: Dhruv Gulwani, Basem Suleiman, Aditya Joshi, Sonit Singh

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a massive university course where 200 to 300 students need to be split into teams to work on big, final projects. Right now, organizing this is like trying to sort a giant pile of mismatched socks by hand while blindfolded. Professors often use spreadsheets or simple surveys, which leads to three big problems:

  1. The Wrong Fit: Some students get projects that are way too hard (like giving a toddler a calculus textbook), while others get projects that are too easy (like giving a master chef a sandwich to make).
  2. The "Clone" Teams: Students often pick friends or people just like them, creating teams where everyone has the exact same strengths and the exact same weaknesses.
  3. The Unfair Advantage: The most confident or "loud" students grab the coolest projects, leaving others with fewer opportunities.

The paper introduces TeamUp, a smart computer system designed to fix this mess. Think of TeamUp not as a robot taking over, but as a super-organized, super-smart matchmaker that helps professors make better decisions.

Here is how it works, using simple analogies:

1. The "Resume Translator" (Semantic Embeddings)

Instead of just looking for keywords like "Python" or "Design," TeamUp reads a student's entire profile (skills, past projects, resume) and a project's description, then turns them into invisible "flavor profiles."

  • The Analogy: Imagine every student and every project is a smoothie. A student who loves coding and data is a "Blueberry-Banana-Code" smoothie. A project needing heavy data analysis is a "Blueberry-Banana-Data" smoothie.
  • How it helps: Old systems just check if both have "blueberries." TeamUp tastes the whole smoothie to see if the flavors actually match. It understands that "coding for a website" is different from "coding for a robot," even if they both use the same language.

2. The "Goldilocks" Filter (Difficulty Alignment)

The system uses a concept called the "Zone of Proximal Development." This is the sweet spot where a task is challenging enough to make you grow, but not so hard that you give up.

  • The Analogy: Think of it like a video game. If you are a Level 1 player, the system won't throw you into the Level 50 boss fight (too scary). It also won't let you fight a Level 1 slime for the 100th time (too boring). It finds the Level 3 challenge that makes you sweat just enough to get stronger.
  • The Result: The system penalizes matches that are too far off, ensuring students are stretched but not broken.

3. The "Jigsaw Puzzle" Team Builder (Complementarity)

When forming teams, TeamUp doesn't just group similar people. It looks for complementary skills, like pieces of a puzzle that fit together to make a whole picture.

  • The Analogy: If you are building a house, you don't want a team of five people who are all expert roofers. You need one roofer, one plumber, one electrician, and one architect.
  • How it helps: The system calculates the "distance" between students. If two students are too similar (like two roofers), it pushes them apart. It builds teams where everyone brings something different to the table, creating a stronger, more diverse group.

4. The "Fairness" Guardrail

The system also tries to make sure the "good" projects (the ones everyone wants) are distributed fairly, rather than just being grabbed by the first few people who log in. It balances the load so no single project is overwhelmed while others sit empty.

What Did They Test?

The authors didn't test this on real students yet. Instead, they ran a simulation (a "virtual experiment") using 250 fake student profiles and 60 fake projects.

The Results:

  • Better Matches: The system found matches that were much more accurate (74% match quality) compared to random guessing (43%).
  • Better Difficulty: 83% of students were placed in projects that were the right difficulty level, compared to only 34% with random assignment.
  • Better Teams: 82% of the AI-formed teams had members with three or more different skill areas, compared to only 41% of random teams.
  • Speed & Cost: It did all this in less than a second per student and cost less than 10 cents per student to run.

The Bottom Line

TeamUp is a tool to help teachers, not replace them. It handles the boring, heavy lifting of sorting hundreds of students into the right projects and teams. This frees up the professors to focus on the human side of things—like resolving personal conflicts or helping a student who is having a bad week.

The paper concludes that while the computer simulation looks very promising, the real test is yet to come: seeing how real students feel about the matches and how well the teams actually perform in a real classroom.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →