Understanding how professors evaluate PhD applications through five faculty voices
by Starc Institute, follow us at X (Twitter) @Starc_institute
Understanding how professors evaluate PhD applications through five faculty voices
by Starc Institute, follow us at X (Twitter) @Starc_institute
This guide synthesizes advice from five computer science faculty members across top universities, revealing both consensus and nuanced differences in how professors evaluate PhD applications.
All five faculty members emphasize that PhD admissions fundamentally assess one question: How likely are you to become a great researcher?
Dettmers ranks the factors in clear order: (1) Recommendations from respected professors with personal connections, (2) Research experience measured by publications and first-authorship.
Andersen explicitly states admissions committees try to "look for signals of research success, which are somewhat different from the signals of academic success."
Harchol-Balter emphasizes that a PhD is about depth, not breadth: "By the last couple years of your Ph.D., you will typically be working on only one narrow problem."
There is unanimous agreement that strong letters are the most important part of an application, but faculty offer specific guidance on what makes letters effective.
Dettmers provides detailed categories: strong letters include anecdotes demonstrating creativity and persistence, come from writers personally known by potential advisors, and discuss research done outside the writer's own lab.
Andersen introduces the term "DWIC" (Did Well In Class) for letters from professors who only taught the applicant in class, calling pure-DWIC letters "almost fatal." He emphasizes: "I'd take a passionate letter of rec from someone I don't know over a 'DWIC' from MIT any day."
Antoniak connects this to personal experience: "Getting to know a professor through a class or through independent research can be really important for getting strong letters of reference."
Smith is blunt: "generic letters do not help your case. Please try to get letters from people who can give specific examples of what makes you a promising researcher."
Faculty universally prioritize demonstrated research ability over potential based on coursework alone.
Harchol-Balter describes what research experience proves: "You've tried research and you liked it" and "you have experienced the roller-coaster of research."
Dettmers is explicit about publications: "First author papers in the top conferences in your area are the most prestigious type of papers that you can get and they have immense value in the application process."
Antoniak notes: "Having some kind of documented research experience is very important for getting into a CS PhD program." She clarifies this could be research internships, capstones, or honors theses – formal publications aren't strictly necessary but helpful.
Dettmers provides specific numbers: "If you have a GPA above 3.5 or a GRE quantitative score above 162, then nobody will care about them anymore. If your GPA is below 3.3, then you might want to explain it in your statement of purpose."
Andersen emphasizes context: "The importance of a student's GPA is modulated by the caliber of the university where they did their undergrad."
Smith (writing in 2007 when GRE was more emphasized) noted: "There are two reasons why we require the GRE: many applicants come from universities we don't know very well" and "international students need to take the TOEFL."
Antoniak offers the clearest contemporary perspective: "I think they matter much less than other parts of your application... Put the most effort into your statement of purpose, letters of reference, and research experience, and not worry as much about GPA, GRE, CV, and other details."
Dettmers provides a structured approach: explain your motivation ("why PhD?"), detail research experience with concrete examples, describe why this specific university and professors align with your interests.
Smith emphasizes substance over style: "Please don't repeat details from your CV" and instead "explain why the project was significant, what your contribution was, and how it informs your plans."
Harchol-Balter warns about common mistakes: "I see lots of students whose statement of purpose is all about how much they love Stanford and Berkeley, but they never really say what area interests them."
Antoniak offers structural advice: "You should ask a faculty mentor or friends who've already gotten into PhD programs to look over your statement and give feedback."
Andersen provides the institutional reality: "I'm sure that a committee would prefer—all else being equal—a really enthusiastic letter from a prominent, recognized person with a strong reputation for accurate letter writing."
Smith (from 2007): "The most important part of the decision, in my opinion, is: who will be your advisor? Your advisor is the person who will guide your research and give you career advice."
Dettmers: "Pick universities mainly according to possible advisors. Make sure each university has more than one advisor you would like to work with."
Harchol-Balter provides a systematic evaluation framework: count faculty in your area, subtract those not actually present, assess atmosphere (competitive vs. collaborative), examine how grad students are treated, and investigate funding structures.
Dettmers: "You should apply for about 10-15 universities. If you apply for more, you run in the danger that you will not have enough time to really polish your applications."
Antoniak: "Apply widely (I think I applied to about 7-10 programs) and keep your mind open at this stage."
Both emphasize having backup options where admission is likely (>75%) and targeting schools where you have realistic chances (25-33%) through recommender connections.
Antoniak: "I personally recommend working in industry... This gives you some extra life experience and maturity, and maybe most importantly, it reinforces that there is a whole world outside of academia that you can always return to."
Smith: "There are pros and cons, and it's a personal choice." He notes that working students "are a bit more balanced and confident about what they want" but cautions that "for some people, working in industry is a drag."
Dettmers shares: "I, for example, extended my master by a year to squeeze in a year of research internships. Without this, I would never have made it into these schools."
All agree that research internships specifically are valuable, with Dettmers noting they provide: improved skills, testing whether PhD life suits you, strong recommendation letters, and possible publications.
Antoniak is remarkably candid: "Your mental health will very, very likely take a hit... in academia, you are constantly competing and being judged, with infrequent and irregular positive feedback." She emphasizes that "a much higher than average percentage of PhD students report mental health problems."
Harchol-Balter describes the reality: "Research can be very rewarding and very frustrating. Most students describe graduate school as a roller-coaster with tremendous highs and tremendous lows." She shares a typical story of a top student realizing "maybe he's not the best" and the growth that follows.
Smith looks for "drive" in applications: "There are a lot of people who're smart. But succeeding in a top Ph.D. program requires also a high degree of self motivation, and dogged determination to get you through the inevitable setbacks."
Harchol-Balter details the key differences:
She notes: "Many students never make the transition between taking classes and doing research – in fact, at most schools only 1/2 of the students who enter the Ph.D. program leave with a Ph.D."
Dettmers provides a detailed two-email strategy:
Harchol-Balter adds specific guidance on whom to ask: "Ideally, your only responsibility will be research" under an RAship, and your advisor relationships during this work become your letter sources.
Antoniak emphasizes: "Since I'm not a professor, I don't have as much experience reading and writing these. However, my impression is that these letters are very important."
Dettmers: Don't "tune" your CV by phrasing things nicely or making it look creative – "this is a waste of time. Just list what you have done."
Smith: "Please don't repeat details from your CV" in your statement. Focus on "why the project was significant, what your contribution was, and how it informs your plans."
Antoniak: "Put the most effort into" statement of purpose, letters of reference, and research experience, and "not worry as much about GPA, GRE, CV, and other details."
Despite differences in emphasis and context, all five faculty members converge on core principles:
Andersen perhaps summarizes it best: "Ph.D. admissions is all about finding students who have the necessary intellectual ability, background skills, and disposition to excel in that specific environment."
The blog is published by Starc Institute. For latest research discussions, follow our X (twitter) at @Starc_institute
This synthesis was created to help prospective PhD applicants understand the nuances and commonalities in how faculty evaluate applications. Remember that individual programs and faculty may have different priorities – use this as a general guide, not a rigid formula.
Starc Institute
Last updated: November 2025