Graduate school (PhD in particular)
Do you need a graduate degree?
Last updated
Do you need a graduate degree?
Last updated
Create a new theory or methodology (e.g., the development of the alternating current (AC) electrical system by Nikola Tesla) ;
Improve existing theory or methodology and apply them in a unique way to address a significant gap that otherwise cannot be filled (e.g., Tesla company innovatively integrates existing technologies to create unique battery electric vehicles (BEVs), which proves that electrification of on-road transportation is a viable strategy to decarbonize our economy)
People are curious, so you can grab their attention by showing some tangible items in your resume and during an interview (see a list of examples below):
Code repositories to show your programming skills
Videos to show your presentation skills
Tools and apps
A personal website to list them all. There are many free online platforms (e.g., GitHub pages, Gitbook, Notion)
Read their publications (esp. recent ones), this helps to understand what new skills you may learn and what future research directs they may want to pursue
Investigate the resources available to the group you are interested in (e.g., what type of computational resources do they have, how well-connected is their research network)
Do the same for the broader environment (e.g., does the department have other professors you may be able to work with)
Address the professor appropriately (nothing special, just like you email anybody for the first time): get their name right (you will be surprised how many times people send inquiry emails with a wrong recipient name, or no name at all).
Do not send a group email to multiple professors...
Make your message clear: why you send this email (don't forget to mention the position you are applying for), why you should be considered for this position (skills + experience + passion), request an interview
Do not repeat the facts (e.g., GPA, standard test scores) in your resume
present them as a holistic story (i.e., why these facts reflect the unique qualifications of you for this position)
Be enthusiastic about your work
Highlight your relevant skills and experiences.
ready to explain the details (e.g., walk through your GitHub repo, explain your role in a publication)
Slides are helpful, but only use them as anchor points (i.e., succinct visuals, bullet points) for your talk
Monitor the audience: if you notice that the listener's attention starts to drift (e.g., you are giving a way too long backstory), pivot your talk (e.g., you can jump a few slides to the next anchor point)
"tell me the time, don't build me the clock"
Ask at least one question at the end (typically, there should be time for applicants to ask questions)
to show that you care about this position
do your homework first (don't ask questions such as "How many students do you currently have?" or "Which department is your group situated in?")
Additional resources
Send a thankyou email (this is also an excellent opportunity to include the things you missed during the interview)
[] How to Pick a PhD Advisor: Everything Explained (by Andrew Akbashev)
[] PhD Interview: Questions, Answers & Explanation (by Andrew Akbashev)