I got an internal referral, so I think that helped cut down the interview process.

After talking with people on the phone twice, they had me take a long (2-3 hrs), proctored exam.

They do this through a service that allows someone to watch you through your webcam for the duration of the exam. It's rather weird.

There were math, logic, and programming questions, broken up into sections.

The math section was pretty easy math, but there was time pressure.

The logic questions were kind of weird and for some it seemed like you'd do well to have seen it before. There were a fair number of puzzles like "A frog is at the bottom of a 10 ft. well and wants to get out. Each jump, he jumps up 2 feet and slides back down 1. How many jumps does it take to get out?" (The answer is 9 - once he's at the top of the well, he doesn't slide back down 1 ft.).

There were also questions like:

You see a test question, but the question has been smudged and all you can read are the possible answers. Which is the correct answer?

• A: all of the below
• B: none of the below
• C: all of the above
• D: one of the above
• E: none of the above
• F: none of the above

The programming section does not test your knowledge of languages, just of basic ideas and developing solutions. I don't remember the questions I was asked, but you should be able to sort and search through lists, and know about some basic data structures like maps. I wrote all of mine in pseudocode and that was apparently fine.

If you pass the exam, they take you to campus, where at least 2 people interview you.

One asks you to talk about a large project you have worked on, what challenges you ran into, and how you solved them.

The 2nd one they give you a problem and have you discuss it for them so that they can see how you think.

I was asked the following: "Sometimes doctors will run into a patient with something that they can't diagnose because it's rare or they haven't seen it before. We have a database of all of the problems patients have and what diagnosis their doctor associated with it. What would we need to do to be able to put this doctor in touch with another doctor who has worked with patients who likely have the same root cause?"

They want you to keep in mind things like how to get user input, how to deal with not everyone having exactly the same problems, how to search for matches, and everything else you could possibly think of. They don't expect a complete solution.

Following this, they'll let you meet some people from the company and go on a tour of the campus. The campus is beautiful.

Keep in mind that the people you talk to may not reflect everyone's experience at the company - I asked someone about how many hours a week they worked and was told that people rarely work more than 40, but since being here, I don't think I have ever worked fewer than 45.

They also have you do some sort of personality test. I'm not sure how relevant this is to the hiring process as opposed to placing you after you've been hired.

Sometimes doctors will run into a patient with something that they can't diagnose because it's rare or they haven't seen it before.

We have a database of all of the problems patients have and what diagnosis their doctor associated with it.

What would we need to do to be able to put this doctor in touch with another doctor who has worked with patients who likely have the same root cause?