The interview process consists of at least two parts, an initial coding test and an on-site interview. They expect the initial test to take less than an hour, so that can be a litmus test for what the rest of the experience may be like. I did well enough on the coding exam to get an on-site interview a couple days later.

On site, they had me do another coding exam. There are four reasonably trivial warm up coding questions and then a longer problem that you aren't necessarily expected to finish. A couple years ago I implemented Othello/Reversi, this interview I implemented 2048. I didn't quite finish the implementation in the time they gave me.

After that, there's a round of algorithm implementation, where they asked me to create an algorithm to solve a problem on the white board and then evaluate its time and space complexity. Then another group of people came in and had me set up the object structure of a page to keep track of front end entities on a screen. The final round was more behavioral and background oriented, where we talked about my experience, previous projects, etc. It was kind of long, but fortunately they let me have some of the pizza they ordered for the office that day.

Given a rather odd recursive pattern, create an algorithm that can efficiently calculate the value at a given stage in the pattern (no recursion or memoization).