I was fortunate enough to get an offer from an I/O program last week. My training is in cognitive, some of the work I do is applicable to I/O (which is what I said in my research statement) but other work is not. I am curious to know from others who are working in a department outside of their training area, what kinds of pros and cons to think about before accepting this job. One issue is that I have never taught or taken an I/O class but I would be expected to teach 3/3 teaching load in an I/O program. In terms of research, I plan to publish in some I/O journals, but some of my work is strictly cognitive and wouldn't apply. What kind of an experience have others gone through when you work in a department outside of your training area?
Date: 24 Mar 2012 02:25
Number of posts: 3
RSS: New posts
I don't have any of these answers, but I would consider straight up asking them about it. At least, ask how publishing in cognitive journals would look for tenure. Also, find out exactly what your typical load would be like. It might be one I/O course per term, plus general courses like research methods & intro. So, it might not involve delving into a new area for all of your courses or anything. And ask yourself before accepting whether you want to do so much teaching outside of your field. If you really like I/O but just don't feel expert in it, then I think you will be fine doing that much teaching in the area because you will become expert. But if you're not that keen on I/O as compared to cognitive, consider holding out for another offer / trying on next year's market.
You can earn a lot more money in an I/O program if you play your cards right - and outside consulting jobs.
That said, if you are dying to do cognitive research, then perhaps this isn't the job for you. 3/3 is intense. Not colonoscopy intense, but intense nonetheless.