So, I have a phone interview for this week for an R1 school. I've never heard of this happening before…I've done phone interviews for SLACs, but any advice on a phone interview at an R1? What can I expect?
Date: 19 Nov 2013 01:18
Number of posts: 3
RSS: New posts
I've had a couple phone interviews with R1s this year and they were primarily interested in why I was interested in the position and their school/dept, my current and future research, and teaching (they asked about what I could teach, what I'd like to teach, and some about teaching philosophy). One place asked about external funding plans. Another asked about start-up needs (including cost), which seemed an odd thing to ask during a phone interview, but I already had that information prepped so it wasn't a problem. One of the interviews was with the entire search committee, which was a bit more pressure (it was more business-like and they were flying through the questions, going around the search committee and taking turns asking), while the others were only with a single person (those were just like having a friendly conversation). Just make sure you do your homework on the department and school. Don't ask questions that you should obviously know the answers to. Prepare some questions for them so your answer isn't "no" when they inevitably ask if you have questions for them. I don't know how they compare to SLAC interviews as I only applied to R1/R2, but I don't imagine they'd be much different.
I concur with annonn's comments and though that the SLAC vs R1 phone interview won't likely be too different. The R1 position will likely involve more questions about research with the SC trying to gauge that you have independent ideas, theories, and a clear sense of a research program. While the R1 may ask about student engagement in research, this will likely be less emphasized than a SLAC. With the likelihood that the R1 will have stronger resources for research, having some general estimates about research start-up costs and equipment needed makes sense. Don't forget software. It's easy to assume some of this will be readily available, but that's not always the case.