The following is a quick note about (cold) emailing professors. You have undoubtedly seen that many professors have notes on their websites that simply say “don’t email me.” I’d like to encourage you to selectively ignore that advice but understand why, when and how.

Are you currently working with me? Email me
Are you from an underrepresented group? Email me
Are you simply telling me you applied? Thanks, low probability of a reply
Are you mass mailing every professor? Please no

Success in academia, like many aspects of society, is often a function of who you know and networking. Students of famous professors don’t need to email because they know their applications will get read carefully. Further, they may have had the opportunity to meet potential advisors at conferences and so they are already well connected when applying. If you don’t fit this description, as many of us don’t,

  • How are you supposed to break into the “in-group”?
  • How is someone from a smaller lab, a different discipline, or an underrepresented group supposed to change the field?
They have to email. They have to take the chance of getting no reply to at least put themselves out there. If this is you, please email me and everyone else.
Professors get lots of emails, that’s why you’re reading this. Many of them are generic and have nothing to do with their specific research. Let’s say a professor works 40hrs a week and works with 10 students/collaborators.
  • 40 - 10hrs of collaboration meetings = 30hrs.
  • 3hrs teaching, 6hrs preparing, & one office hour = 20hrs left.
  • Review cards, thesis committees, graduate admissions, hiring, rec letters, … = 10hrs.
  • Grant writing and staying current on the literature… = 0hrs.
All of these things actually take much longer than what I’ve listed and are worse around paper and grant deadlines, but we still haven’t budgeted any time to reply to emails from our collaborators or anybody else. This means, a professor likely is reading your email while eating lunch, on the bus on the way home, or at night when they are trying to figure out what they forgot to do today. So, a useful exercise might be to ask yourself:
  1. How much time does it take to reply to the email I’m sending?
  2. Is this email actually a DOS attack? [i.e. did it take me much less time to write than it will for them to reply?]

The following a few broad classes of common emails we receive:
❌Generic “please accept me into your program” email -- DOS attack
  • We will read your application eventually anyway, I promise, I will.
  • We have to look through our budgets, look at existing obligations, etc
  • We have to read through your previous research papers to find a fit
This email is unlikely to get a reply

👍Tailored “please accept me - we do similar work” email -- Potentially balanced
  • We still can’t promise anything, we still have to investigate funding, you still need to apply and we still will go through your application and recommendation letters in detail.
  • You brought up a specific intersection in our research and yours. This requires substantially less homework for us to say something helpful and even if we don’t end up working together now, hopefully, we’ll cross paths and learn from each other in the future.
If there is a specific question, a reply is more likely

✋Very specific technical question
  • Love that you’re in deep in the same area as me, but these often are better answered by one of the other authors. Use your best judgment here.
That’s 100% fine, and you should say that. You can indicate where you have tried looking to learn more, and details about your interests. I take no offense to receiving an email, it’s when there’s a request attached to it that things get tricky.
You don’t and that sucks, I’m sorry. Normally you can assume they will try and take one or two per year but funding changes as do other commitments. A professor deciding to have a child, work with a start-up, create a new conference, or any number of other things might eat into their time and so they may not take anybody that year.
While flattering, that’s probably not true. Related to my own multimodal research area I can quickly name a bunch of really awesome other people. Here are a few in no particular order that I wish I had more time to work with:
Henny Admoni (CMU)
Joyce Chai (U Michigan)
Yejin Choi (U Washington)
Mirella Lapata (U Edinburgh)
Devi Parikh (Georgia Tech)
Cynthia Matuszek (U Maryland Baltimore County)
Stefanie Tellex (Brown)
Yoav Artzi (Cornell Tech)
Desmond Elliott (U Copenhagen)
Dieter Fox (U Washington)
That’s legit, and please let me know. It doesn’t mean I can solve it, but with more information, I can at least try and be helpful.
Email me, let’s see what’s up. :)