Enthought Interview Questions
& Process

I went through a phone interview with two people. They seemed friendly and asked questions. About 20% of the questions were obscure, like Python Metaprogramming or floating point considerations, which I haven't dealt with in my 20 years of programming. The rest were standard computer science and data structures questions. They also asked about my willingness to travel and teach, and when I could start. Three days later, I got a rejection email. I was confused because I have a Ph.D. and 20 years of experience in scientific computations. I think the interviewer had less experience than me, which might explain the rejection. I recommend checking out interviewers beforehand and withdrawing if their background doesn't seem comparable.

I applied online and then connected with an employee at a career fair. This led to a phone interview with someone in Austin. The call was about 1.5 hours and focused on computer science topics. While the questions were basic for a CS major, they were challenging for me as a mechanical engineer. A few simple math questions were included at the end. I thought the interview went well and was tough, but I didn't advance to the on-site stage.

First, there was a phone interview to check my background knowledge on Python. Then, a coding interview over the phone. The third interview was in person at their head quarter. The in person interview included a mock planning session for training, a presentation of my instructional materials, a panel of developers, and a panel of executives. It was intense and stressful.

The interview process has 3 steps. First, a 45 minute technical phone screening where we introduced ourselves and you did too. We discussed your SWE experiences in your projects and your PhD research. There was no live coding or offer stage mentioned.