Finding Research as a Premed: Where to Start and What Matters

Every fall, I get some version of the same message from a student who's realized, usually around week five or six of the semester, that they still don't have a research position and everyone around them seems to already be in a lab. If that's you right now, take a breath. September and October are the best window of the year to lock something down for spring semester or next summer, because this is exactly when PIs are thinking about who they'll need once the current crop of seniors graduates and their spots open up. You are not behind. You are, if anything, emailing at the right time.

What I want to do in this article is walk through the mechanics of finding a position, because most of the advice out there stops at "do research" without explaining what that means in practice, what counts, and why it matters beyond just filling a line on AMCAS.

Cold Emailing Labs the Right Way

Cold emailing is still the most reliable way undergraduates get into a lab, and it works far better than most students expect, provided the email is written correctly. The biggest mistake I see is a generic template blasted to twenty professors with nothing more specific than "I am interested in your research." Adcoms never see these emails, but PIs absolutely notice the difference between a form letter and a student who did their homework, and that difference determines whether you get a response at all.

A strong cold email is short, three or four paragraphs at most, and it does a few specific things. It states who you are and what year you're in. It names one or two specific papers or projects from that lab, not the department, that lab, and says something real about why that work interests you. It's fine to be a beginner. You don't need to understand the methods section in depth. What you need to show is that you read past the lab's homepage and found something concrete to react to. Then it asks directly for what you want, whether that's a fifteen-minute meeting, a spot as a volunteer research assistant, or information about how the lab typically brings on undergraduates. Attach an unofficial transcript and a short resume. Keep the whole thing readable in under a minute.

If you're reaching out to a large number of labs at once, which is a completely reasonable strategy, a mail merge tool can save you a huge amount of time on the repetitive parts: the greeting, your background paragraph, your closing ask. Google Sheets combined with a mail merge add-on, or a simple Python script if you're comfortable with one, will let you personalize the salutation and the lab-specific paragraph automatically while keeping the rest of the email consistent. The part that cannot be automated is the sentence or two referencing that lab's specific work. If you skip that step to save time, you've turned your mail merge into exactly the kind of generic blast that gets ignored. Do the reading first, build a short list of labs with a specific note on what caught your attention about each one, and then let the merge tool handle the formatting and sending.

Expect a low response rate. Getting responses from ten to twenty percent of the labs you email is normal, not a sign you're doing something wrong. Professors are busy, many don't have space, and some simply don't check a specific inbox often. Send more emails than feels necessary, follow up once after a week or two if you haven't heard back, and don't take silence personally.

Learning to Talk About Research Like You Belong There

One thing that trips up a lot of premeds, even after they've secured a position, is not having the vocabulary to describe what they're doing. "I do research in a biology lab" tells an adcom nothing. Being able to say "I study how a specific protein regulates inflammation in a mouse model of colitis" tells them you understand your own project, and that specificity is worth cultivating early, not just when you sit down to write your AMCAS work and activities section.

This means asking your PI or your graduate student mentor to explain not just what to do at the bench or in the code, but why the lab is asking the question in the first place. What's the broader hypothesis? What would a positive result mean, and what would a negative one mean? Keep a running document of this, even informally, because eighteen months from now when you're writing your application, you will not remember the details as clearly as you think you will right now.

The Different Kinds of Research, and Why the Differences Matter

Premeds tend to imagine research as one thing: pipetting in a wet lab. In reality, the landscape is much wider, and understanding the categories will help you figure out what you're looking for.

Wet lab versus dry lab. Wet lab work involves physical experimentation, handling reagents, cell cultures, animal models, tissue samples, running assays at the bench. Dry lab, or computational, work involves analyzing existing data, writing code, building statistical models, or working with large datasets, often without ever touching a pipette. Neither is more prestigious than the other, and which one suits you depends heavily on your own working style. If you like working with your hands and want a defined protocol to follow, wet lab tends to fit. If you like coding, statistics, or pattern recognition and don't mind sitting at a computer for long stretches, dry lab work in bioinformatics, biostatistics, or computational biology is worth exploring, and it's often easier to get into as an undergraduate because the barrier to entry is lower.

Clinical versus translational versus basic science. Basic science research investigates fundamental biological mechanisms, often in cell lines or animal models, with no immediate application to a patient. It's slower to produce results and the papers take longer to publish, sometimes years, but the work tends to carry more scientific weight and is viewed by many programs as the most rigorous training ground for the scientific method. Translational research sits in the middle, taking findings from the bench and moving them toward clinical application, often through biomarker studies or early-phase trials. Clinical research works directly with patient populations or patient data, and it moves considerably faster since you're often working with data that already exists rather than generating it from scratch. A single semester in a clinical lab might realistically produce a conference abstract or even a co-authored paper, where a comparable stretch of time in a basic science lab might only get you partway through one experiment in a much longer project.

Biomarker discovery versus therapeutics. Within the clinical and translational space, some labs focus on identifying biomarkers, measurable indicators that can predict disease risk, diagnosis, or prognosis, while others focus on developing or testing therapeutics, the actual drugs, devices, or interventions used to treat a condition. Biomarker work often involves large datasets and statistical analysis, while therapeutics work can involve anything from early cell-based testing to human clinical trials, depending on the phase. Both are valuable, and both give you something specific and real to talk about.

Retrospective studies. A retrospective study looks backward at data that already exists, such as patient charts or a hospital database, to identify patterns or answer a question, rather than collecting new data going forward. These projects are common in clinical research labs and are genuinely useful for undergraduates because the timeline is often compressed into a single semester or summer, and there's a real chance of ending up as a co-author on a case series or a data analysis paper before you graduate.

None of these categories is the "correct" choice for a premed. What matters is understanding which type of work you're signing up for before you commit a semester or a summer to it, so the experience matches what you're hoping to get out of it.

Research Doesn't Have to Mean a Bench or a Hospital

A lot of students assume research only counts if it looks like a wet lab or a clinical trial. That's not true, and treating it that way closes off some genuinely strong opportunities. Health economics research, examining how policy, insurance structures, or access shape health outcomes, is legitimate and often easier to break into than a bench lab, especially if you have any comfort with statistics or economics coursework. Psychology and behavioral health research, public health research, health services research, and even bioethics research all count, as long as the work is systematic, involves a real question, and produces something you can point to at the end.

What makes any of these types of research work for a medical school application is whether you can tell a coherent story about why you did it, what you learned, and how it connects to the kind of physician you want to become. A student who spent two years in a health policy lab studying insurance coverage gaps and can speak fluently about how that connects to their interest in primary care access is in a much stronger position than a student who spent one disengaged semester in a prestigious wet lab and can't explain what the project was testing.

What Counts as a Real Output

Time spent in a lab matters less than what you can point to at the end of it. Adcoms want to see a tangible output piece, something that proves the work was real and that you contributed to it meaningfully. That can be a peer-reviewed publication, a conference poster, a podium presentation, or even a well-documented internal report if the lab doesn't publish externally. What it can't be is just hours logged with nothing to show.

Authorship position matters here, and it's worth being direct about it. First authorship signals that you drove a substantial part of the project, wrote a meaningful portion of the analysis or manuscript, and were central to the work, not peripheral to it. A middle-author position on a large paper still counts and is still worth having, but it carries less weight than being first author on a smaller project. If you're choosing between two labs and one offers you a clearly defined sub-project you could plausibly first-author within a year, and the other offers you a spot as the sixth person on a massive ongoing study, the first option is often the better bet for your application, even if the second lab is more well known.

If publication timelines in your lab are slow, and in basic science they often are, ask your PI early about presenting at a university research symposium or a regional conference instead. A poster presentation with your name on it, completed before you apply, is worth far more than a paper that's still sitting in peer review the day you submit your primary application.

Paid Research and Formal Summer Programs

Research does not have to be unpaid, and paid research is not viewed as less serious than volunteer research. If anything, being accepted into a competitive, funded summer research program adds a layer of external validation to your application, since it means an outside selection committee, not just your home institution, evaluated your application and decided you were worth investing in.

Formal programs like NIH Summer Undergraduate Research Fellowships, offered at many academic medical centers, and the Amgen Scholars Program, which places students at research-intensive universities for an eight to ten week funded summer, are two of the more recognizable examples, and there are dozens of similar programs run by individual universities, hospital systems, and disease-specific foundations. These typically provide a stipend, sometimes housing, and place you in a structured cohort with weekly seminars and a final presentation. Getting into one of these is genuinely competitive, often more competitive than getting into the lab itself, so treat the application with the same seriousness you'd give a secondary essay.

Outside of formal programs, plenty of individual PIs pay their undergraduate research assistants an hourly wage or a stipend directly out of grant funding, particularly for work that requires more time commitment than a volunteer would reasonably give, like running a full set of weekly experiments or maintaining a database. There's nothing wrong with asking directly whether a position is paid once you've established real interest. Most PIs won't be offended by the question, and many have more flexibility on this than students assume.

Summer Versus School Year Research

Both have real advantages, and the right answer depends on your schedule and what you're trying to get out of the experience. Summer research lets you go essentially full-time, often forty hours a week, which compresses a project timeline dramatically. A student working full-time over ten weeks can sometimes accomplish what would take an entire academic year of eight to ten hours per week. This is where formal summer programs and paid positions tend to concentrate, and it's often the fastest route to a real output piece.

School-year research, by contrast, lets you build a sustained relationship with a lab over multiple semesters, which matters more than people initially realize, both for the depth of what you learn and for the strength of the letter you'll eventually get. A student who works in the same lab for six consecutive semesters, even at only eight hours a week, ends up with a far more detailed and personal letter of recommendation than a student who did one strong ten-week summer program and never worked with that PI again. The ideal, when your schedule allows it, is both: start during the school year to build the relationship, then use a summer to go deep and produce your output piece.

The Relationship Matters More Than the Line on Your Application

Here's the part that gets underweighted the most. The primary reason to do research, beyond the experience and the output piece, is to build a real relationship with a principal investigator who can eventually write you a detailed, specific, enthusiastic letter of recommendation. Research letters carry particular weight with admissions committees because they come from someone who has watched you work through problems, handle setbacks, and think critically over an extended period, which is a very different vantage point than a professor who only knows you from a lecture course.

You earn that kind of letter by showing up consistently, asking questions that show you're thinking about the project rather than just executing tasks, being reliable enough that your PI starts trusting you with more responsibility, and staying visible enough in lab meetings and one-on-ones that your PI genuinely knows who you are as a person, not just a name on a spreadsheet of research assistants. The goal is a PI who is, in a real sense, looking out for you: someone who checks in on how your semester is going, who thinks of you when a conference presentation slot opens up, who remembers your name three years later when you email asking for a letter. That kind of relationship rarely happens by accident. It comes from consistent, visible effort over time.

A Few Other Things Worth Knowing

Lab meetings are not optional extras even when you're technically not required to attend them. Sitting in on your lab's weekly meeting, even as the least experienced person in the room, is one of the fastest ways to pick up the vocabulary and context that makes you look competent in your cold emails, your interviews, and eventually your secondary essays. It's also where PIs quietly notice who's engaged and who isn't.

Don't be afraid to switch labs if the first one is a bad fit. A semester spent in a lab where you're disengaged, poorly mentored, or doing work you can't explain is not better than no research at all, and it's certainly not better than switching to a lab where you'll build something. Adcoms are far more interested in depth and genuine engagement in one or two labs than in a scattered list of three or four short, shallow stints.

If your school has an office of undergraduate research, use it. These offices maintain lists of labs currently looking for undergraduates, run funding opportunities for independent projects, and can often connect you with faculty faster than a cold email alone. It's a resource that goes underused simply because students don't think to check it before starting their own search from scratch.

Finally, don't wait for a perfect fit before reaching out. Interests shift once you're in a lab and see what the day-to-day work looks like. A student who thought they wanted oncology research sometimes discovers they love health services research instead, and that only happens by getting a foot in the door somewhere and paying attention to what you genuinely enjoy doing, not what sounds impressive on paper.

Every Situation Is Different

Not every applicant has the bandwidth for extensive research, and that's a fair and common situation. Between coursework, clinical hours, work obligations, and everything else competing for your time, research is often the piece that gets squeezed. The good news is that there's a type of research suited to almost every schedule and every interest, from a low-commitment dry lab data project you can do remotely to an intensive funded summer fellowship, and finding the right fit matters more than finding the most impressive-sounding one.

If you're not sure where to start, or you want help figuring out which type of research fits your schedule, your interests, and the story you're trying to tell in your application, click below to set up a consultation and we'll walk through it together.

How We Help Our Clients

You can also reach us directly at success@admitmd.com, or call or text 512-693-9228.