Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
PFFS Presentations at Idea Institute

PFFS Presentations at Idea Institute

|Views: 34|Likes:
Published by Elena Godin
Aaron Liepman – Assistant Professor, Biology Department Eastern Michigan University.
UM Preparing Future Faculty in the Sciences seminar series
Aaron Liepman – Assistant Professor, Biology Department Eastern Michigan University.
UM Preparing Future Faculty in the Sciences seminar series

More info:

Published by: Elena Godin on Apr 06, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





January 21, 2009
 a Lp
– Assistant Proessor, Biology Department Eastern Michigan UniversityUM Preparing Future Faculty in the Sciences seminar series
“PreParation and guidance for an academic interview” // ten tiPs for an academic Job interview:
Relax - while an interview can be an intense, nerve-wracking experience, try not to let your nerves get the1.best o you. It is oten very obvious when someone is nervous, and this can negatively aect perceptions o you. Remember that you have been invited to visit campus because the aculty/committee is excited aboutyou – usually people are very riendly! Note that the rst interview is likely to be the most dicult since it willpresent many new situations (e.g., meeting with a member o the upper administration), uture interviewswill be easier. Treat each interview like you would an important experiment – just as you take careul notes about your2.experiments and research, take a ew minutes at the end o the day to refect on the interview, noting whatworked well and any rough spots you may have encountered. Try to come up with ways to avoid suchtrouble spots in the uture. O course, an interview presents many more variables than a well-designedexperiment, but this practice will enable you to minimize the likelihood o repeat problems.Be yoursel – i you take the job, you’ll likely be interacting with most o the people you meet or many years.3.It is important to make sure that you will be able to get along well with your uture colleagues.Make sure your presentation(s) is/are clear, concise, and audience appropriate – a lot is likely to ride on this4.portion o the interview – in lieu o teaching a class the job talk may be used as a proxy to judge teachingability, and it will certainly be used as a measure o research skills/potential. Be sure to discuss with yourhost about the composition o the audience. Also, make sure to include sucient background inorma-tion to enable people who may not be experts in your area to ollow along and understand the gist o yourpresentation. Remember, a little too much background inormation is typically ar less problematic than notenough. Practice your presentation in ront o an audience (time it!) at least once. While your lab mates andclose colleagues will likely provide helpul comments, I also recommend including someone less amiliarwith your work in the audience. For example, I presented my seminar to my dad (psychiatrist, not a plantcellular & molecular biologist), and as awkward as this seemed at rst, it was a very helpul experience toget questions/comments rom an interested non-expert in my eld. One other tip, keep track o time duringthe seminar, adjust timing accordingly and do not run over time. Turn the interview around – Use probing (but tactul) questions to get the inside scoop about this depart-5.ment where you may end up working or many years. You’ll likely interact with junior and senior acultymembers as well as students, and each will have valuable perspectives about lie at University X. Askingquestions is benecial or a number o reasons:

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->