Towards applying to CS Ph.D. programs

Introduction

After going through and learning from tens, if not hundreds, of blog posts on applying to Ph.D. programs, it would almost be inappropriate if I didn't write down something and throw in my two cents about this exhausting but ultimately self-enriching and fascinating process.

This blog post will hopefully be a useful guide to the students who are planning to apply to Ph.D. programs. I will try to give you a glimpse of what the application process looks like and offer some advice on how to best approach, embrace, and enjoy this unique journey. I hope this helps you! If so, please consider paying it forward, maybe start by giving a hand to students in your research group who will be applying for Ph.D. programs.

Note that whatever I write down is biased because of my background and experience. For context, I grew up and went to high school in China, and then did my bachelor's in the United States, majoring in computer science and mathematics. During my undergraduate, I worked on systems (scheduling/cluster resource management) for ML starting from the summer of my second year, and I fully committed to doing a Ph.D. in my third year. My research interests fall under the big topic of "systems and networking", and for my Ph.D. application, I applied to professors whose areas of interest range broadly across all system aspects of big data, including systems for ML (training, inference, video analytics, etc.), ML for systems (congestion control, video streaming, etc.), cloud computing/data center resource management (e.g., serverless, scheduling training/inference workloads), etc. Also, my honest opinions can be straight-up wrong, so take everything with a grain of salt.

Overview

A CS Ph.D. application package should be the culmination of your previous academic career. It usually includes three recommendation letters, a curriculum vitae (CV), a list of publications (if any), a research statement of purpose (and possibly another personal/diversity statement), your college-level transcripts/GPA, standardized test scores, and a bunch of other personal information.

While your technical ability is instrumental to your Ph.D. application, doing the application right is also critical but is often neglected. This blog post aims to point you to some common practices for wrapping your application package nicely with the following chapters:

  • Chapter 1: Why do a Ph.D. at all?

  • Chapter 2: Narrowing down the programs/professors of interest

    • §2.1: How do you put up the big list of POI?

    • §2.2: How do you narrow the list down?

  • Chapter 3: Getting in touch with the POI

    • §3.1: Make a CV and a webpage first

    • §3.2: How and when should you reach out?

  • Chapter 4: Asking for recommendation letters and sending out requests

    • §4.1: Who should you ask for letters?

    • §4.2: How should you ask for letters?

    • §4.3: What's next?

  • Chapter 5: Writing up the statement of purpose

    • §5.1: How should you write a statement?

    • §5.2: What should be in your statement?

  • Chapter 6: Preparing for interviews

    • §6.1: What's a typical interview like?

    • §6.2: What to do before, during, and after an interview

  • Chapter 7: Towards good mental health during the application season

    • §7.1: Before sending out applications

    • §7.2: After sending out applications

  • Chapter 8: Choosing a Ph.D. program (WIP)

    • §8.1: Understanding your offer

    • §8.2: What to do on the visiting day

  • Appendix I: My application timeline

  • Appendix II: Meta-references

Each chapter includes some of my personal opinions followed by a list of references. Moreover, my application timeline and some meta-level references are provided in the appendix.

Chapter 1: Why do a Ph.D. at all?

In my opinion, you should do a Ph.D. if you have already done some research, been through the ups and downs (or at least know a bit about what they are like), and still absolutely love doing research. If you are applying for a Ph.D. because your Asian parents are forcing you to do one or if you want to stay in academia because you didn't get an industry job, think twice: it's a huge commitment.

This is a million-dollar question and I don't feel entitled to write more about this right now, so please take a look at all the references below.

References

Chapter 2: Narrowing down the programs/professors of interest

Most people agree that when applying to Ph.D. programs, the advisor is the most significant factor (even more so than the school/department itself). Thus, picking awesome professors/person of interest (POI) is arguably the most crucial part of the application process: pick good (in terms of research interest match and personality match), and you might be happy for life.

95% of the students I know apply for 5-15 programs and they typically target 1-3 POI for each program. In my case, I checked out ~50 professors in my field of interest and ended up boiling the list down to ~30 professors that I especially liked from ~15 schools. This chapter will try to answer two questions: (1) how do you put up the big list of professors that you are generally interested in working with, and (2) how to narrow the list down to those who you are particularly interested in working with?

How do you put up the big list of POI?

  • Check out your advisor's former lab mates, recent collaborators, and direct connections in their network. These people are likely to share similar interests with your current advisor, plus they know your advisor personally, so these folks should be fun to work with, assuming you love what you are doing right now.

  • The math folks have a great thing called The Mathematics Genealogy Project where you can see this tree of academic relationships. You can also trace the tree of professors in cs, starting from very senior professors who work in your field of interest, and then go down the genealogy tree to look for those holding tenure-track positions. For me, I started with Ion Stoica. Fun fact: as many as six of my professors of interest have had direct connections with Ion!

  • CSRankings is also a great place to visit. You would want to first list the target conferences that you mostly read papers from (for me, it was SOSP, OSDI, MLSys, EuroSys, ATC, SoCC, NSDI, and SIGCOMM). Then, go to CSRankings, select your target conferences, check out the professors from each school who has published in these venues, and go through them one by one. Unless you already have a specific topic that you would like to work on, IMO you should be open-minded in this part of your search and try to check out as many professors as possible. When I was going over csrankings.org, I had also marked professors who publish in venues like SIGMOD & VLDB, SIGMETRICS, HPC conferences, and ML conferences like ICML. Although I still ended up applying to system professors, it was fun to get to know what folks are working on outside of your main areas of interest.

  • Take the same list of venues that you like. Then, take a look at the program committee of the recent conferences, and go to their personal sites one by one. Doing so will produce a list that overlaps very much with the one you got from csrankings.org, but csrankings.org may not have the most up-to-date information.

  • Talk with other people, e.g. current students and alumnus in your lab, your current advisor, random people you met online, etc. You will genuinely get a lot from this! My personal story is that I didn't consider applying to the program I ended up committing to until after a friend of mine strongly recommended that I shoot this POI an email. I ended up getting in touch with the POI and found that I liked him a lot and that he was hiring. So yeah: talk to people!

  • Follow a bunch of professors on Twitter. This generally helps with catching up with the latest news in academia. For example, professors post hiring ads and tweet about their opinions on various things (example), and incoming professors tweet about their employment (this information is usually not listed on any official website).

  • Although the POI is arguably the most crucial factor for a happy (and successful) Ph.D., the program itself has to be taken into consideration during your application. People usually apply to some schools at their level (match), some schools above their level (lottery), and some schools below their level (safety). To that end, look at students with a similar background as yours and refer to their school list and application results. You can also have your current advisor go over your school/POI list and provide some feedback. It is also a good idea to modify your school list based on your feedback from cold-emailing the professors.

How do you narrow the list down?

On the one hand, you should work with people whose research interests truly excite you. Although I had a few professors who work on databases/HPC on my first list, I ended up throwing them away because I prefer some topics over others.

On the other hand, you should not work with people who are bad advisors. Advisors who ghosts/abuses students are a big no-no! I used two approaches to filter out these professors:

  • Check out their RateMyProfessors reviews. I get that teaching isn't for everyone and some professors put more emphasis on doing research, which is fine by me -- but ultimately, I honestly don't want to be working with someone who is a 1.2, because I think if a professor fails to create a supportive learning environment for their students, then it's unlikely for them to do so for their advisees. IMO a series of reviews that start with a 1 is somewhat of a red flag.

  • Talk with their current students or search for their posts online. More practically, talk with people who might have heard about some bad news -- they tend to travel very fast. There has to be something wrong if many Ph.D. students quit a lab halfway through.

And also, you should be careful about applying to a program that only has one professor you are interested in working with, because a lot of things can happen in five years, e.g., your advisor doesn't get tenure and goes to the industry or gets poached by a school you hate. In that case, you will most likely switch to a different advisor in the department. Be prepared for contingencies.

References

Chapter 3: Getting in touch with the POI

Now that you have narrowed down a list of 10~30 professors you want to work with, it is time to get in touch with them. Some people don't bother to do this at all -- I do not recommend this, as I know professors who will only skim through your application package if you haven't reached out. Plus, getting in touch with them helps you figure out how many students they are taking this season, their ongoing/future interests, how enthusiastic they feel about your background, etc.

Make a CV and a webpage first

If you are not able to create a web page, you probably shouldn't be applying to CS graduate programs. -- David Evans

Before you start emailing people, I strongly recommend making a personal webpage. Quite a few professors have also talked about the importance of personal sites in academia. A good Ph.D. student/research should be visible in the community/on the Internet, and Linkedin/Facebook/department-generated webpages are just not enough for that. Some good templates include Jon Barron's website and academicpages.github.io. Prof. Timothy Roscoe recommended including the following information on a personal webpage:

  • A picture, preferably a recent one that actually looks like you. If you have a goofy picture that you really like, consider hiding it behind your main picture and make it show on hover.

  • A list of publications. No pressure if you haven't published, especially for undergraduates who do research in systems.

  • Some biographical information:

    • How long have you been a student? And how long have you got left?

    • Who do you work with? And what do you work on?

    • Random (but non-embarrassing) details for color.

Although a personal website makes you easily accessible on the internet, you should also spend some time putting up a high-quality CV. Looking at other people's CVs and trying to emulate their formats/highlights most certainly helps. Your POI is not the only person who will look at your CV, especially if the Ph.D. admission committee has a huge influence on the admission decision: other professors and senior graduate students (who might be focusing on different research topics) will also go over your CV, and it needs to impress them enough during the first round of the admission process for a professor to even see your package (?). When you cold-email the professors, attach your CV.

How and when should you reach out?

The de facto way to get in touch with professors is to cold email them. If you are lucky to have the opportunity to meet with professors during a conference or have already known the professor, that would be great! But most people send emails anyway unless they know a POI very well, so getting the email (and the first impression) right is vital. Here are a couple of tips.

  • Figure out the timing. My recommendation is to start as early as you feel comfortable once the fall semester begins and professors start to check their inboxes regularly so they will hopefully have enough time to get back to you. If you do this a few weeks after you submit the application, the POI might already have a batch of good candidates in mind (but still, better late than never). On a more fine-grained level, a good trick is to send a timed email scheduled for something like 8 AM, so that your email will be on the top of the inbox when professors check their inboxes.

  • Be concise but on-point. There is a reference below that covers how to send out cold emails, but take it with a grain of salt, as that's more for emailing professors for undergraduate research opportunities. My suggestions are:

    • You must mention who you are working with right now and your research interests.

    • You must mention why you would like to work with the POI, and you should probably mention a bit of their existing work and why you like them. Better yet, go in-depth and ask a technical question/ask if xxx is an interesting idea for possible follow-up work.

    • You must attach your CV. I had attached a draft research statement just in case the POI has some time to take a look, but in retrospect, I don't think any of them had the time to read it (?).

    • You should probably put a link to your webpage in your email signature. I had also included a link to my calendar for the easier scheduling of meetings.

  • Know the email etiquette (there are two articles in the references that cover this). To that end, triple-check your email for missed attachments and spelling mistakes before sending it out! Better yet, have your roommate proofread it.

  • Within a school, reach out to professors one at a time and only move on to the next professor if the previous one doesn't get back to you in a week or so. Please don't reach out to five professors whose offices are right next to each other at the same time -- they talk.

  • Please don't send three emails in a day to try to catch someone's eye. Professors are busy, but they will get back to you if they see a good fit. They might forget about things, and in that case, send a kind reminder after some time (say a week?) of not hearing back.

  • Use your institutional email account. Gmail/outlook addresses are fine but don't use your QQMail.

References

Chapter 4: Asking for recommendation letters and sending out requests

Most CS Ph.D. programs ask for three letters of recommendation.

First of all, IMO it is necessary to understand what the other side looks like about this recommendation system. Except for the actual letter itself, your recommenders will also be asked about your clarity of goals for graduate study, English skills, creativity, etc. The "scores" recommenders can give are chosen from truly exceptional (top 1%), outstanding (top 10%), above average (top 25%), not applicable/unable to respond, etc. Some other questions include (source):

  • How long have you known the applicant?

  • What group are you using for comparison?

  • Admission recommendation to the program is {strongly recommended, recommended, recommended with reservation, etc.}

Who should you ask for letters?

Moving on. Before sending out requests for letters, you have to figure out who your letter writers will be. It would be best if your letter writers are:

  • Well-known in the research community. Having a senior professor/big name write a strong recommendation letter for you helps immensely. Either that or some junior professors who are actively publishing in a relevant field. These professors have a strong network of connections, which is valuable considering how critical connections are. In contrast, a letter from a postdoc is probably less helpful -- but if a postdoc is writing a letter for you, try to have them co-write a letter with their advisor.

  • Someone who knows you well. Whoever has worked with you extensively will have plenty of chance to know you and see that bright side of yours. If you mainly worked with Ph.D. students/postdocs during your research and a professor who wasn't very hands-on toward your research is writing the letter, I would suggest coordinating with those people so that the professor can put some insights from the others into the letter.

  • Preferably someone in academia instead of the industry, and if they are from the industry, they should be involved in doing research (e.g., leading a research team. At least they should have a Ph.D. degree?). I'm not too sure about this, but rumors say that letters from people in the industry are pretty much useless. This makes some sense because the qualifications of a good Ph.D. student are somewhat different from those of a good intern, and letter writers from the industry would have no idea of what the program committee is hoping to see. Note that when I say people from the industry, I'm referring more to an average SWE intern's mentor -- if Lidong Zhou or Amar Phanishayee writes you a letter, then obviously it's very good!

How should you ask for letters?

Now that you know who you will be asking, it would be best to let them know about it. Here are some tips for doing that.

  • Ask early. You don't need to know your exact school list when you send your first email request, but you should at least give people a rough idea of the number of letters and when they will be due. Professors are busy, like really busy. Please ask for letters as early as possible so they can plan accordingly. Two months in advance is better than one, and one month is better than two weeks. Imagine being a professor who's going through finals week and a couple of conference deadlines, and boom, five students show up to ask for a total of 100 letters that are due in one week. Just thinking about that makes me uncomfortable. Besides that, if you apply to 30 (?!) programs, some professors may not be too happy about submitting all those letters and will only agree to submit 10 of them. In that case, you should, of course, ask for some other professors to fill in the gap, but anyway, you don't want to know about this a week before the application deadline.

  • Communicate clearly. It would suck if professors finish your letter but don't know where to submit them. My advice is: (1) It is preferable to send official requests through application portals in batches, so those emails don't get lost in the professor's email inbox. (2) Create a table in Google Sheet to keep track of the programs you are applying to, the application deadlines, and the status of the requests. For example, knowing the date of when you sent a request will be helpful when a professor looks up that email in their inbox. Of course, share this google sheet with your letter writers. (3) Send email reminders to remind professors about an upcoming application deadline, preferably a week in advance, if not more. Note that for most programs, the deadline for people to submit letters is some time after the application deadline, so don't panic if a professor uploads a bit late.

  • Provide enough information. Once a professor agrees to write you a letter, attach many files when you get back to them, e.g., your cv, draft SoP, transcript, and final project report. Some professors will also ask you to provide a list of relevant personal information, e.g., professors you have taken classes with and the grades you got, major accomplishments, etc. Besides those, remind professors about how your opportunity with them helped you grow as a scholar.

  • Ask for strong letters. It goes without saying that strong letters from professors say a lot about who you are as an applicant -- they will make a difference in your application. When you ask for letters, explicitly ask for strong letters, so that professors who will otherwise write average letters can give you the chance to pivot.

What's next?

And last, you should write them a thank you letter. Send a small gift (something under $20 should be fine depending on the department policy, e.g., a box of chocolate provided that they are not allergic to chocolate :P). When you commit to a program a few months later, also remember to send another email to let your writers know about the good news -- they will like it very much!

References

Chapter 5: Writing up the statement of purpose

The statement of purpose (SOP) is arguably less important than some other things in your application package, but still, it is one of your first files that get looked at. First impressions are critical: IMO, an exceptional SOP will not make your application stand out as much as one would do in undergraduate admissions, but a bad SOP might ruin your application.

How should you write a statement?

  • Before you start writing your statement, make sure to read through many other people's (good) SOP. Prof. Phillip Guo had shared a few statements that are really nice examples. Although he has taken down most of the content and has asked people not to distribute them, some of these statements are scattered across the Internet, and I'm sure you are good at Googling stuff. There are also some other good examples online.

  • Start early to write up the first draft. I was applying to a pre-doctoral summer program so I was very lucky to have my first draft ready in the summer before the application season, but still, I didn't finalize my statement until a few days before Dec 15: it takes a lot of time to do the endless revisions. Another thing is that except for the research statement of purpose, different schools might ask for additional materials such as diversity statements, short answers to random questions, etc., so make sure to figure out those requirements way before the deadline.

  • Go through a lot of iterations. Just like writing up a paper, the first draft is guaranteed to be bad, and good papers go through O(10) rounds of revisions. To that end, try to get a lot of feedback by having as many people read your statement as possible: writing center, (former) lab mates, high school classmates who are majoring in computer science, roommates, etc. Five people can probably offer you 50 suggestions, and if you go by 20 of them, your sop will rise to a new level.

What should be in your statement?

Keep in mind that professors will use this to judge your writing skills. If you are good at writing, it's time to show off. Otherwise, at least make sure there are no grammatical/spelling mistakes: that would look terrible. Consider using something like Grammarly to fix those mistakes and clarify your writing.

A significant portion of the statement should be on your past research. People usually spend one paragraph for each project, and the ranking is either by relevance or by date. IMO if your projects connect well, by date is a more natural way since you get to tell the story behind your motivation to get a Ph.D., but don't worry if you rank them by relevance.

In each paragraph, describe the project (e.g., collaborators, short background & motivation, major technical contribution, your contributions & takeaways). Keep in mind that the people reading your statement might be working in a different subfield (I don't suppose the bioinformatics people will know anything about Cuckoo hashing), so don't just copy-paste the abstract of your past papers.

Depending on how much space you have left, IMO you should talk about your research interest using at least one sentence and at most one paragraph. If possible, IMO you should identify some rising research topics in the next few years and describe why they pique your interests: the POI might resonate with you if you come up with some good ones.

It's a good idea to mention which professors you would like to work with. Try to aim for 1-3 professors in the statement, and briefly discuss why you are interested in working with them.

References

There are also a bunch of blog posts by people who know more about writing up statements than I do, so make sure to take a look at these articles, including but not limited to:

Chapter 6: Preparing for interviews

Congratulations on sending out all of your applications! Take a little break first, both physically & mentally. Then, it's time to start preparing for interviews!

What's a typical interview like?

  • Duration: A typical interview lasts an hour or so. The ones I had been in lasted as short as 20 minutes and as long as two hours.

  • Content: You usually start with some chit-chat, followed by a quick self-introduction. Then, the POI will likely ask you to talk about your research project(s), during which they will evaluate both your hard and soft skills. Afterward, you can ask the POI some questions, including the lab culture & dynamics, the graduate program, their research, etc.

  • Will there be coding/technical questions? (???) It depends, but most professors don't ask these kinds of questions. From what I've heard, there are professors who ask about things like page fault handling in operating systems or how web indexing works (those are extreme outliers though). But there will of course be technical questions for your past research projects!

What to do before, during, and after an interview

  • Before an interview: Go over your statement and resume, since the professors will likely refer to them if they ask questions about you. If you included a topic that you are less familiar with in your future research interests, it doesn't hurt to delve a little bit deeper into that topic.

    • For every project listed on your resume, prepare the following:

      • One sentence that summarizes the project. This is like the title of your project but maybe with some more info for context.

      • A 3-minute introduction that expands a little bit more, say on the background, motivation, technical contributions, and results.

      • A 10-minute overview of the project that can be expanded into a 30-minute discussion. Totally write stuff down beforehand if you feel like it.

      • Your contributions to the project. Undergraduates often get carried by Ph.D. students/postdocs in their research, so it's important to highlight what you did and what you got out of a project.

    • Note that the interviews vary in duration, and you might have multiple projects to talk about (I only focused on the most significant one), so be flexible about the timing.

  • Before an interview: Read your POI's work. It's ok to prioritize the POI who you are really interested in or who showed great interest in you. They won't ask you about the technical questions in their past research projects, but still, getting to know about what a POI used to work on shows your seriousness and enthusiasm. Different students spend various amounts of time on this phase of the preparation, but I think you should at least do the following. For each POI:

    • Do a quick pass through the title/abstract/collaborators/venues of all their past work.

    • Pick 2-4 of their projects to dive deeper into. I had focused on (1) their most highly-cited paper, (2) their most highly-cited first-author paper, (3) a highly-cited paper in the recent two years, and (4) a recent work that you are particularly interested in, either because you can relate to the project regarding motivations/techniques or because you are genuinely captivated. And by diving deeper into it, I meant going over all the figures, learning about the background/motivation/nuggets (high-level contributions and techniques), etc.

    • If you like this POI very much, you can totally go over the technical details of some of their papers. Because why not? Reading papers are fun! If not, then you should probably think twice about your application.

    • Take a quick skim at their Ph.D. thesis, especially the acknowledgments section to know more about them as a person.

  • Before an interview: Do mock interviews (or research presentation talks) with your friends/labmates. I didn't, so I totally screwed up my first interview, but it was a good practice and I got the chance to learn from my mistakes. In retrospect, I really should have done an actual mock interview with some labmates and had them ask all kinds of questions.

  • Before an interview: Make sure you have a quiet environment, a stable internet connection, and a good microphone. If you have noisy roommates or bad routers, you might want to reserve a quiet study room in a library in advance.

  • Before an interview: Dress properly. FYI, the chats are mostly casual unless the interviewer specifically mentioned a (multi-person) serious interview.

  • During an interview: Chill out, and be yourself. IMO a significant purpose of interviews is so that you can get a sense of the vibe/chemistry between you and the POI, so don't force things like saying you are interested in something that you are not.

  • After an interview: Send the POI a thank-you email. If you had a good chat, maybe it's time for some follow-ups. Anyway, you should let the professor know your thankfulness and reassure your enthusiasm for collaborating with them.

References

Chapter 7: Towards good mental health during the application season

My mental health was surprisingly good during my application season (probably because I only took three credits in the fall and spent most of my time polishing up a paper & applying to Ph.D. programs). Although I am no expert, here is some advice for staying positive during the six months. If things get too tough, please talk to the professionals.

Before sending out applications

  • Make plans to abide by so that you don't stay up and rush things. "Rushing is the path to the dark side. Rushing leads to staying up. Staying up leads to bad health. Bad health leads to suffering." - Master Yoda

  • Maintain a consistent, healthy sleeping schedule.

  • Talk with supportive people around you and be supportive of each other. You are not alone, and every applicant is fighting the same battle. Surround yourself with people who can help relieve your anxiety, not trigger them.

  • Workout. Participate in team sports, work on bodybuilding, take a random walk outside, etc.

  • If things go well, this will be your second last semester as an undergraduate. Since most people go to a different school for Ph.D., it will also likely be your last fall/winter in your current city. On weekends, spend some quality time with your friends here to create some enjoyable memories for future reminiscing. If you are studying at UW-Madison, here is an article I wrote on the 20 must-dos before you graduate.

After sending out applications

After sending out applications, you will likely have huge chunks of free time since the semester is over and Christmas is coming up. Although the interviews will be coming shortly, IMO you should first take a week-long mental/physical break. Congratulations on submitting all those applications!

  • Once you get back from your mental break, you should get back to studying. You likely won't have a lot of things to work on, and your motivation might be low -- after all, your application is already out, and there is not much you can do to make it drastically better. Instead of spending all your free time being anxious about the applications, try to divert your anxiety, say by developing a new hobby. Read a book or something, or learn to cook.

  • 1point3acres. zhihu.com, and The GradCafe have a lot of good information and stuff, but please consider restraining yourself from visiting these sites too often. Social media takes a toll on people.

  • Also, it might be worthwhile to turn off instant notifications for your email inbox and check it a few times a day at regular times.

  • Compare to yourself, not others. This is in general a great suggestion on how to live a happy life.

  • Spider-Man: No Way Home was in theatres during my application season, and it had a great line: "If you expect disappointment, then you can never really get disappointed". Don't get too hyped up if a POI reached out to you or if you did well in an interview. Otherwise, you will feel really bummed when you get rejected.

References

Chapter 8: Choosing a Ph.D. program (WIP)

You now have multiple offers in hand! Very nice.

By the time you sent out the applications, you should have a rough idea of your preferences for all the programs. But, it's not a good idea to rush your decision. Grad schools usually request you to make a decision by Apr 15, and you should spend at least some time making up your mind. After all, this is one of the biggest decisions in your life. That being said, if you are set to commit to a program, withdraw/decline your other offers as soon as possible so the other POI can extend the offer to other students on the waitlist.

The first thing you would want to do is to do your own research. My personal priorities are: personality/advising style match with the POI >> research interest match with the POI > department ranking in your area of studies > department overall rankings > location/weather > amount of financial support & overall quality of life > overall ranking of the university. There are also other factors to consider depending on your future plan. For example, if you are looking to go into the industry after graduating Ph.D., you might want to go to a program where doing summer internships is easy and encouraged.

Then, talk with a lot of people regarding your offers and decisions: parents, relatives who work in academia, significant others, friends, people on the internet, labmates, current advisor(s), labmates, POI, POI's students, current students in the program but not in your POI's lab, and current students at other places. You should look for a diverse set of opinions on the pros and cons of each program. Keep in mind that there is no one best choice, and you will need to make tradeoffs.

Understanding your offer

From my knowledge, using financial support as a criterion, all offers can be classified into the following:

  • Guaranteed financial support: The funding is guaranteed throughout the first five years through a combination of fellowship, research, teaching, or external awards.

    • Fellowship/external awards: Fellowships usually require faculty nominations during the admissions process. To get external awards like the NSF Graduate Research Fellowships Program, you will need to go through an application process. Note that most external awards I know of require you to be a U.S. citizen, national, or permanent resident.

    • Research/teaching assistantships: For RAs, you work with a professor on research and get paid (!!!). For TAs, you TA a class, and the time commitment varies between a few hours and 20 hours per week depending on the program/course/instructor. The monthly stipend falls somewhere between $2500 and $4000.

  • No guaranteed financial support: Finding graduate assistantships to support your studies is possible, but you will need to rely on yourself to find them and there is no guarantee. In theory, if no professors are willing to take you as an RA and you weren't matched to a class that needs a TA, you will need to pay out of your pocket for the tuition and insurance fees. Yikes

What do to on the visiting day

  • Chat with as many current students/POI as possible. The POI could very much be your future (co-)advisor/collaborator, and you will also likely share an office with the current students who work in similar research areas, so it's good to know ahead of time who they are and what they are working on. You should also use this opportunity to see if the students are happy.

  • Connect with the other prospective students. It's an excellent opportunity to build your network and meet new people even before the program starts.

  • Walk around. I didn't attend my visiting days in person, but if I had, I would have spent a lot of free time walking around both the campus and the adjacent city. You will be spending the next few years in (somewhat of) a bubble around the campus, so a vibe match is crucial.

  • Enjoy the free food and the free trip! You totally earned it.

References

Appendix I: My application timeline

Don't feel obliged to copy my timeline exactly -- this is just for your reference.

  • Mid-August: First draft of the school list and the SOP

  • Mid-September - Early-October: Confirmation of recommendation letter from 3 professors

  • Early-October - Mid-November: Send out cold emails to professors of interest. On average, I sent ~2.5 letters per week.

  • Early-November: Finalized school list

  • Early-December: Sent out all rec letter requests

  • Mid-December: Finalized SoP; Sent out all applications!

  • Late-December - Mid-February: Interviews

  • Late-January: First unofficial offer

  • Mid-February: First official offer -- the offers came in all the way to early March, although I withdrew/turned most of them down.

  • Late-March: Committed to Princeton!

Appendix II: Meta-references

For those of you who read Mandarin Chinese or don't bother to use Google Translate:

PreviousResources on Learning Academic Writing (for Computer Science)NextMachine Learning Systems - Index

Last updated