How to find a research team in medicine

Most students are told to "join a research team" without anyone explaining where these teams are, how to tell a good one from a dead one, or how to get on it. The teams exist, plenty of them have an open seat right now, and getting on one is mostly a matter of looking in the right places and being easy to say yes to.

A research team is just a small group of people working on one or more projects together, usually a senior person setting direction and a few others doing the work. You do not need to build one from scratch to get started. Joining an existing team that already has momentum is the fastest way to your first finished project, because the hard parts (the question, the ethics approval, the data access) are often already handled.

Where the teams actually are

Look in this order, closest first, because the closer the team the lower the friction.

Inside your own institution

Departments run research groups, and most of them are quietly short-handed. The labs and clinical research groups at your own school or hospital are the obvious first stop. Read your department's research page, then check who has published recently on PubMed, an active group has a reason to take on another pair of hands, a dormant one does not. A two-line email to a group that just put out a paper lands very differently than a cold email to someone whose last output was years ago.

Through people who have seen you work

The attending who liked your presentation, the lecturer whose course you did well in. A warm introduction beats a cold email every time, because the thing a team most wants to know about a stranger is whether they will follow through, and someone who has watched you already knows. This overlaps heavily with how you find a mentor, which we covered in a separate guide on finding a research mentor.

Beyond your own walls

Here is the part the standard advice skips: the best team for you may not be at your school. A lot of medical research now runs remotely, chart reviews, systematic reviews, surveys, registry analyses, none of these require you to be in the same building. If the strongest match for your interests is two time zones away, that is no longer a problem.

This is the gap iCohort is built to close. You can browse open projects to see which teams are actively looking for people right now, or look through the researcher directory to find people working on what you care about and reach out. Both are open to read without an account, so you can scout before you commit to anything.

How to tell a functional team from a stalled one

Not every team is worth joining. Before you commit, look for the signs of one that actually ships.

• Recent output. Have they published, presented, or submitted anything in the last year or two? Momentum is the single best predictor that your project will finish.
• A defined role for you. "Come help out" is a warning sign. "We need someone to screen abstracts" or "we need help with data extraction" is a real seat.
• Someone who does day-to-day mentoring. On a well-run team there is often a senior resident or postdoc handling the hands-on guidance while the lead sets direction. That person is who makes or breaks your experience.
• Clear expectations on time and authorship. A team that can tell you plainly how many hours they need and where your name would fall is one that respects the people doing the work.

How to get onto one

Once you have found a team worth joining, the move is the same one that works for finding a mentor: be specific, and be easy to say yes to. Name something they actually did, state what you bring and how many hours you have, and make a small concrete ask rather than "will you take me on." A short, specific message beats a long, vague one.

And treat it like a funnel, not a single shot. A reasonable reply rate from cold outreach is one in five to one in ten, so contact several teams, not one. The students who "can't find a team" almost always asked once and stopped.

The short version

Functional research teams exist, many have an open seat, and the work is finding them and being easy to add. Start with active groups at your own institution, lean on anyone who has seen you work, and look beyond your own building when the local match is weak. Check for recent output and a defined role before you commit, then reach out to several teams with a short, specific message. Your first team is the hard one. After one finished project, the next is far easier.