Pleasant and straightforward, even though I was nervous as hell. The phone interview was a series of basic technical questions. If you know more or less how a computer works "under the hood" and decent knowledge of algorithms/data structures, you should be fine. There were some pop science questions; I think they were looking for the ability to explain things clearly to a layman. My code interview - the second step in the interview process - was a little messy, partly because my Python was a little rusty and partly because it was done using a Google doc (Enthought doesn't use Google docs for this anymore). But the tasks were neither trivial nor too difficult to finish. The onsite interview panels were actually kind of fun. They put you in front of a whiteboard and ask you to solve some technical problems. This interview was focused more on the problem-solving process than on specific knowledge.

The first part is a scientific computing knowledge check. They ask questions that probe the breadth and depth of your computer science knowledge. Live coding exercises in python. Something simple and then a leetcode question. Peer and leadership interviews with some problem solving at a whiteboard.