I'm hoping to have a on-site job interview coming up, and since I am number of years removed from grad school I am faced with a dilemma. I will need to present something technical, but I'm really not sure what would make sense. My graduate work is getting a bit stale at this point, and since it was what I worked on [a number of] years ago I don't know if its an appropriate topic. I am employed at the moment, and have plenty I could present about from my current work, but I know there is a confidentiality line in the sand that I don't want to cross.I didn't know how to answer this, but I kept remembering this old Derek Lowe post and I finally found it. From 12 years ago, a great set of answers from the Blogfather himself:
There was a good question asked in the comments to the previous post on first job interviews: what do you talk about when you work at one company and you’re interviewing at another?
Well, I’ve done that myself, more than once (note to my current co-workers: not in the last few years, folks.) And it can be tricky. But there are some rules that people follow, and if you stay within their bounds you won’t cause any trouble. That’s not to say that my managers wouldn’t have had a cow if they’d seen my old interview slides at the time, but I was at least in the clear legally.He starts with work that was published, material that is in patent applications and worst of all, material from previous academic work. Read the whole thing.
I think that about sums it up, although I will make a note that this is why it's probably good practice to routinely be working on side projects that are both publishable and not immediately, directly work-related (not that it is easy to find time for such endeavors, nor are they encouraged by management.) Readers, how have you threaded this particular needle?