Something else to consider is, after signing any necessary non-disclosure agreements, to offer to work hourly for a minimum wage a la: http://www.codinghorror.com/blog/2012/03/how-to-hire-a-programmer.html until they see if you're a fit and if you like them. (What Jeff Atwood describes in his blog seems like a whole lotta work; I mean, given that someone within the org already knows you, I think it would make sense to contract you on probation until it looks like it'll work out.) Just a thought... > From: Robert <http://dummy.us.eu.org/robert> > Date: Sun, 19 Jan 2014 07:29:10 -0800 > > More generally, if you have time, looking at results from > > http://www.google.com/search?q=glassdoor+python+interview > > may be worthwhile. > > > From: Naren Venkataraman <http://www.gmail.com/~naren.naren> > > Date: Sun, 19 Jan 2014 05:18:31 -0500 > > > > Hope I am not replying too late. Here are somethings that come to my mind. > > I would say understanding and coding - decorators, generators, > > introspection > > http://www.slideshare.net/dabeaz/an-introduction-to-python-concurrency