How to Email a Professor About a Research Opportunity

You want lab experience, a summer project, or just a foot in the door of a research group. The only thing standing between you and that is one email to someone who has never heard of you. This guide covers exactly what to put in it, in what order, with a full example you can adapt, plus the follow-up to send when nothing comes back.

Start with a realistic picture of how that email gets read. Assume it is opened on a phone, in a gap between other things, and that the opening lines are all you reliably get. You cannot make anyone read to the bottom. What you can do is make the top of the message do the work: who you are, what you read, what you want, and what you are offering.

What this email is actually asking for

Be clear with yourself before you write. There is a difference between asking for a paid position, asking for unpaid summer experience, asking to sit in on lab meetings, and asking for fifteen minutes of advice about how people get into the field. They are four different emails and they get four different answers.

The version that is easiest to say yes to is usually the smallest one. A request for a short conversation, or a question about whether the group takes undergraduates at all, costs the reader almost nothing. A request that commits money, space and supervision for three months is a much bigger thing to agree to in a reply written between meetings.

You can still want the big thing. Just do not lead with it.

Do fifteen minutes of reading first

The line that separates a real email from a mass mailing is evidence that you looked. You do not need to have understood a whole paper. You need one specific, true sentence about the work that could not have been written about anyone else.

A workable method: find the group's page, pick the most recent paper you can actually follow, and read the abstract, the figures and the last paragraph of the discussion. The discussion is where researchers say what they could not do and what they want to do next. That is where your sentence usually comes from.

Then write your interest as a fact about the work, not as flattery. "I found your work fascinating" tells the reader nothing and could have been pasted into forty emails. "The part I keep thinking about is that the same resistance genes turned up in plots with no recent manure" tells them you opened the paper.

The subject line

The subject line has one job: make it obvious who is writing and why, before the message is opened. Say what you are and what the email is about. Aim for something you could take in at a glance, roughly ten words.

Use this shape:

Avoid "Hello", "Quick question", "Opportunity", or an empty subject line. Avoid marking it urgent or high priority, because nothing in this email is urgent to the person receiving it and saying otherwise sets the wrong tone before they have read a word.

The six parts of the message

Keep the whole thing under about 200 words. That is not a rule handed down from anywhere, it is a working limit that forces you to cut the padding. Six parts, in this order:

• Who you are: course, year, institution. One line.
• What you read: one specific sentence about their actual work.
• What you want: the ask, stated plainly, in one sentence.
• What you bring: techniques, software, hours you are free, in concrete terms.
• What you are not asking for: the sentence that removes the awkward part.
• The close: one clear question, and how to reach you.

The fifth part is the one most drafts leave out, and it does a surprising amount of work. Saying "I am not asking you to create a funded position" removes the thing the reader was quietly worried about while reading, which makes the reply easier to write.

A full worked example

Here is the whole email. Names, university and paper are invented, so change them, but the shape and the length are the point.

Notice what the example does not do. It does not explain why the field matters. It does not describe the student's passion for science. It does not ask three questions. It names one paper, one skill set, one date range and one question, and it ends.

Keep the ask answerable in one sentence

The most useful test you can run on your draft is whether the reader could answer it in a single line without checking anything with anyone else. If the answer is no, the email is likely to sit in the inbox as a task rather than a message.

Funding, visas and place counts are usually not one person's decision, so an ask that depends on them cannot be answered in a sentence. If money or credit is genuinely part of what you need, it is better to say so briefly and ask who handles it, rather than asking the researcher to solve it.

Compare these two closes. "Could you let me know what funding is available and whether the placement counts towards my degree?" needs two enquiries elsewhere before anyone can reply. "Are you taking any undergraduates this summer, and if not, is there someone else I should write to?" can be answered while walking to a meeting.

What to attach, and what not to

Attach one thing: a one-page CV as a PDF, named with your actual name. A file called "CV final v3 (2).docx" makes the reader do filing before they have read anything.

Do not attach transcripts, coursework, certificates, folders of photographs, or anything in a compressed archive. If any of that is wanted, you will be asked. A large attachment from an unknown address is also more likely to be treated with suspicion by a mail filter, which is a plain, mechanical reason to keep it small.

Put the essentials in the signature instead: name, course, year, institution, and the email address you actually check. If your university address forwards somewhere you never look, fix that before you send anything.

Common failure modes

These are the ways cold emails go wrong. They are listed as a set, not in any order of frequency, because nobody has counted them:

• The blank compliment. "I am very interested in your research" with nothing that shows you read any of it.
• The wrong person. Emailing someone whose group left the topic years ago, or who does not supervise undergraduates, because their name came up first in a search.
• The visible mail merge. A greeting with the wrong name in it, or a paragraph that clearly belongs to a different department.
• The essay. Six paragraphs about your journey into science, with the actual request buried in paragraph five.
• The unanswerable ask. A question that needs a committee, a budget line or an immigration decision before anyone can reply.
• The missing next step. Enthusiasm with no question in it, so there is nothing to reply to.
• The apology opening. "Sorry to bother you, I know you are busy" spends your first line on nothing.
• The formatting mess. Coloured fonts, three sizes of text, a signature image, or a wall with no line breaks.
• The name and title slip. Getting the surname or the title wrong in the greeting, which is the one detail that is easy to check and hard to excuse.

Most of these are easier to see from the outside than from inside your own draft, which is the argument for reading it once out loud before you send it. If you run out of breath in a sentence, cut it.

When to send it

Send it early. If you want summer work, aim to write at least eight weeks before you want to start, and preferably before the end of the spring term, because plans for the summer tend to be made well ahead of the summer.

Send it to one person at a time. If you want to write to three groups in the same department, that is fine, but write three different emails and be ready for them to compare notes. Do not put several researchers on the same message.

How long to wait, and the follow-up

Wait ten working days. Silence at that point is not usually a verdict on you. An unanswered email is more often an email that was opened at a bad moment and slid down the screen.

Send exactly one follow-up, in the same thread so the original is right there. Keep it shorter than the first. The rule for the follow-up is to add something new, rather than repeating yourself in a louder voice.

Look at what changed between the two messages. The first email offered R and basic statistics. The follow-up offers a technique the writer did not have in March. That is new information, and it gives the reader a reason to open the message rather than a reminder that they owe you a reply.

After one follow-up, stop. Chasing a third time costs you more than it gains, and the same effort spent on a different group is likely to be worth more.

If the answer is no

A short no is a good outcome. It ends the uncertainty and it opens one more move: reply once, briefly, thanking them and asking whether there is anyone else working on similar problems who takes undergraduates. A referral inside a department is worth far more than another cold email into the same building.

Keep a simple record of who you wrote to, when, and what came back. Three months later you will not remember, and writing to the same person twice with the same first email is an avoidable mistake.

A last pass before you send

• Is the name in the greeting spelled the way it is spelled on their own page, with the right title?
• Is there one sentence in the email that could only have been written about this person's work?
• Can the whole thing be answered in one line?
• Is it under about 200 words?
• Is there exactly one attachment, one page, PDF, named after you?
• Is your reply address one you actually check?
• Have you read it out loud once?

That is the whole method. One specific sentence about the work, one clear ask, one honest list of what you can do, one question, one follow-up. It is not a trick and it does not guarantee anything, because you do not control the person at the other end. It is the version of the email that is easiest to say yes to, which is the only part of this you can control.