Aspiring academics - older page

If you're an undergraduate/recent undergrad who wants to understand what doing research is all about, resources on this page should help you get a sense for it.

Tags: aspiring-academics 

I cover the following topics.

The journey [top]

Currently, undergrads in science and engineering ought to be exposed to the following milestones in landing on a career in research/a researchy job.

  1. Why: why is a career in research worth pursuing? generally motivated by powerful stories in science and innovation; addresses the romantic notion of doing science many imagine while in high school
  2. What: Big picture: what does a career in research look like? perspective of getting a job, financial requirements/constraints, life trajectory, etc. Careers after an advanced degree–need not be an academic professor. can try out others like science communication, freelancing, etc. May not even require an advanced degree.
  3. How - doing research: what to expect. what your research mentor would expect of you. what value system to acquire: curiosity driven investigation, not doing research for the sake of prestige value, not hell bent on a publication as an end goal, etc.
  4. How - details: skills you will benefit from: learning and gaining expertise in tools relevant to your research area (MATLAB/R, Pytorch, STATA, etc.), critically reading and evaluating current literature, the importance of understanding prior art, thinking of experiment design, determination when experiments fail, writing/articulating your thought process, etc.
  5. First RA experience: resources for applying to your first RA experience. Example - could be writing an email to a professor in your university, a pre-doctoral program at different universities/research labs like Microsoft Research or Google.
  6. Post first-research experience: enjoyed your first RA experience? Resources for applying to grad school/research jobs.

Information gaps [top]

There exist the following twin problems which undergrads face.

The aim of this document is to address each of these points in some detail. This document is a work in progress (WIP).

Why: Why research?

I am yet to complete this section. WIP.

What: Big picture

Is research for me? [top]

If you’re generally curious about how the world works, and have an interest in understanding details of how things around you work, you should definitely give research a shot. If you’re an undergraduate at a school with a vibrant research community, it is that much easier to give it a go, and to see if you enjoy it.

From experience, if you’re interested in your coursework, and have a curious mind, and if you end up disliking research - then it is most likely the case of poor mentorship. Your mentor did not show you the ropes well, and did not give you the time you deserved. Please do not be discouraged by it. Give it a shot anyway! It can be a lot of fun.

(Note - there’s a reverse ask here as well. If they do give you that time, what can you do to ensure they feel their time is well spent on you. Doing research is definitely more commitment than doing courses. Read Jason Eisner’s article below to learn more about this.)

What research is not [top]

Doing research [top]

This article, penned by Prof. Jason Eisner at JHU, is an excellent primer on how you can equip yourself in having a fruitful research experience. I strongly urge you to read it, and imbibe the recommended steps in your research stint. In his famous talk ‘You and your research’, Richard Hamming describes the process of doing good research.

This talk transcript I have hosted on this site is a clone of https://www.cs.virginia.edu/~robins/YouAndYourResearch.html

If you’re an undergrad at a school with a great research program [top]

If you’re an undergrad at a school like MIT (or some other xIT in your country), which is primarily known for its research, you should definitely give research a shot to get your money’s worth. Making the most of your xIT experience != taking more grad classes – these classes are pointless after a while. The best bang for your buck is in doing a UROP (undergraduate research program).

Every PI (principal investigator) in such colleges is super accomplished at what they do, and is at the bleeding edge of defining their field. They maybe bad teachers in the classroom, and even bad research mentors - but they definitely know their field well. You stand to learn and gain a lot.

So, do give it a shot, and see if it works well for you. It is very likely you’ll work with someone in their group (as against directly working with them, and that’s fine), and that someone can spur your interest in research.

Here’s an informative article on how to accommodate research in your otherwise busy undergraduate schedule – making the most of an undergrad at CMU

The Jason Eisner article in the section above provides great information on what to keep in mind while you start off your research project.

Aspiring researchers from India-like countries [top]*

If you are an undergrad/aspiring young researcher from India reading this - it’s great you are interested in research!

If you are from a college where there is a good culture for research, read the above section on how to make the best of it.

If your undergrad college does not have a strong research environment [top]

And importantly - if you are not from a “tier-1” school, where research opportunities do not exist for undergrads, worry not :-) I didn’t have such opportunities either, and I made it through just fine.

The catch is - it’s a lot of work. Lot more than it usually takes to do research.

* I believe the information that follows applies to most countries with an education system similar to India - very few top univerisities where world-class research happens, and a long tail of engineering colleges which focus on teaching and not research.

The summary of it is – earnestly understand your undergrad course material. During undergrad, or right after, work as an RA in a relevant lab in India to gain concrete skills and experience in research – this could be through a summer research program (see the Resources section for links), or by you reaching out to labs you think are interesting. Doing this will require you to first learn concrete skills and technologies. See the talk/slides below, and email 1, email 4, FAQs for details.

If you ended up having an excellent RA experience at an academic lab, or at pre-doctoral programs offered by the likes of Google, Micrsoft, etc., and you now have a strong sense for what you want to work on and who you think will best be able to guide you, then you should just go ahead and apply for a PhD with them.

But if you are still not sure, liked your RA experience, and want to explore this further, then consider one of –

  1. doing an M.Tech/M.S. at any of (and only) the top universities in India by writing and excelling at GATE. A few IITs provide the option of doing an MS-by-research without needing a GATE score. This education will be essentially free of cost, while offering world class graduate level coursework+research opportunities.
  2. doing an MS program outside India which has a strong thesis component + will fund you fully. Most universities in Canada provide an MASc, which is different from a professional masters degree, and is fully funded (tuition + stipend), or
  3. working at a cutting edge corporate research lab. Finding such labs are hard, since they generally require advanced degrees to get in in the first place (see the Resources section for a few that I know of which hire undergrads).

Hence, your best bet is to do a solid masters degree where you will be exposed to advanced coursework, and state of the art research.

In this process, figure out what problems in a particular research area really bother you which you see yourself solving, and then consider who are the best researchers in the world who might support you to solve that problem. You should then consider applying to them/their university and doing your Ph.D. with them. Don’t worry too much about the “name” and “prestige value” of the school you apply to - people matter more. You are significantly better off doing your Ph.D. with a professor whose research interest matches yours but is at an “okay” university, than doing it with a professor with unrelated interests but who’s at an “elite” university. See also this note by Prof. Charles Sutton on how to use websites which rank different universities and departments. He reaffirms some of the points I’ve summarized above.

Details. [top] This talk provides more details.


These are the slides I use in this talk.

Also see the FAQs where I’ve responded to common queries which aspiring researchers typically send out to faculty. See also Prof. Shriram’s talk listed in the Resources section which gives you a perspective on how faculty evaluate Ph.D. candidates and applications.

Feel free to reach out to me if you have specific questions. When you reach out, make sure you have read the link on the slide on how to write effective emails (it’s towards the end of the google slide deck I’ve linked above). A post detailing best practices to follow when writing out emails is long pending. I’ll get to it one day.

M.S. (outside India) vs. Ph.D. At this point, you may be quite confused about why I’m dwelling on the specifics of Ph.D. programs. After all, you may have a bunch of friends who head out to the US to do their masters/M.S. degrees who didn’t seem to follow most of the resources provided on this page. How are these degrees different?

Short answer – it is totally different, as these programs neither expect nor will train you with the skills a Ph.D. demands/trains you for. These M.S. programs are meant to be professional degrees which promise to teach you skills which you can directly use in the industry. Most people join these M.S. programs not to improve their skills in doing research, but to land a job in the country they do their M.S. in (mostly the United States)—it’s the most established route to land such jobs in another country.

Perhaps the biggest tangible difference is the finances involved – in a Ph.D. program, you are being paid a modest salary while you produce knowledge, and on the other hand, you pay upwards of 2-3 million Indian rupees for your masters degree (which they expect you will earn in 2-3 years on joining their workforce upon graduation). Note - these MS degrees are different from degrees which also support an honors thesis (typically offered by universities in Canada, and a few in the US, Europe). See point 2 in the summary above.

Resources [top]

I intend to keep the lists below updated. Feel free to write me an email in case you come across any more such relevant resources.

Advice on applying to competitive Ph.D. programs [top]

I strongly recommend you go through this talk by Shriram if you aspire to apply to Ph.D. programs in the US. [top] While he talks about computer science specifically, a lot of what he talks about should hold for other disciplines, and will help you understand what faculty look for when reviewing applications. Importantly, it will help you appreciate the intellectual maturity that is expected of you as a Ph.D. candidate.

Note - There’s a sizeable overlap in the contents of each of the resources shared above. Do go through each of them nevertheless.

Academic statements to graduate schools [top]

Note - Adding keywords like PhD CS computer science SOP statement of purpose sample example MIT CMU Stanford Berkeley so that it gets picked up by search engines.

Research internships for undergraduates [top]

Research jobs in India offered to undergrads [top]

I don’t know a lot of product research groups where academic-style research happens, with publications at good venues as one of its goals. The orgs I list below may no longer maintain active research groups/fit the above criteria. You should definitely reach out to the founders directly (these are typically small orgs) and check with them. Also note - these are mostly jobs in computer science, since that’s the field I’m most familiar with. If you come across any more, please do write to me.

Sharechat , Aspiring Minds Research , Sensara.tv , Gram Vaani , Qure.ai , Nirmai , Strand life sciences , Ati motors

Publishing your first paper [top]

This excellent blog by Achu Wilson documents what it took him to publish his first research paper in one of the best conferences out there for robotics. Achu did not have typical RA-like opportunities during his undergrad.

Jason Eisner has this excellent page on writing your first paper.

Note - a publication need not be necessary to be successfully admitted to an MS/Ph.D. program/a research job. Instead, writing will teach you to make cogent arguments, and go through the process of scientific peer review. If you do end up in a career in research, you would end up regularly writing and communicating your work. Writing a paper during undergrad is a great way to test whether you enjoy this process. Additionally, papers are not the only way for you to learn and test this skill–you could perhaps write out a blog, a tech report, etc. which will serve the purpose equally well.

See my talk/slides above on where to publish–most academic conferences and journals out there are outright fraudulent. If you’re not sure, aim for a workshop at the top conference in your field, or a student-friendly journal/conference to begin with. These generally encourage student submissions, and have high quality peer-review processes. If not, a thoughtful blog post or tech-report should work equally well.

FAQs [top]

My responses to some queries I have received over email and other social media over the years. My responses echo most of the content mentioned on this webpage.

My background [top]

I did not have a great undergrad research experience. I wanted to, but I was too ill-equipped to learn how I could have gained quality experience. I had a scholarship in my junior year to do a research internship at the CS dept. of one of the IITs in India. While I learned a couple of things there, I knew right away it wasn’t a “high quality” experience. My undergrad thesis experience was great - I had a great advisor, I learned a ton of things, but it didn’t train me to do quality research, and I was painfully aware of this limitation.

Thereafter, I put in a great deal of effort in finding such opportunities. By the end of my senior year, I was writing horrendous emails to academic research groups I wanted to work in. I was not skilled enough to demonstrate what my value addition would have been to a group that potentially hired me. Despite all of this, I managed to land a great first job upon graduating, where I “made my bones” in research. That’s right - I was fortunate to have a job right out of undergrad which had a strong research component to it. I learned to do good research there, and went on to managing a small team of researchers on a variety of interesting and innovative projects. Had I not landed this specific job, I’d likely have applied for a full time RA with professors I’d marked out as doing “interesting work”. I had offers from other good places for a generic software engineer’s role - I knew I did not want to explore those options.

Looking back, I was an absolute fool at most times in my research journey. I would be stuck on silly things, I would ask trivial questions, I would just not understand certain concepts, I would not see the big-picture until a long time had passed, etc. But I kept at it because I thoroughly enjoyed learning these bits. And importantly, I had a great mentor who was patient enough to show me the ropes and indulge my inadequacies, while being encouraging.

I am where I am because of a bunch of such people who showed me the way. And I would love to support others like you who want a taste of this experience.

Over these years, I’ve worked on and developed an expertise in problems in machine learning, data science, program analysis, natural language processing, and systems building.

Acknowledgement [top]

Thanks to the following for their very helpful feedback on this page.

Srishti Yadav , Jeevanjyoti Chakraborty , Neeldhara Misra, Anna Ivanova, Vivek Seshadri, Greta Tuckute, Kaveri Iychettira