Good question 
We tend to start with a 30-minute “getting to know you video call”. We’ll talk about your experiences, answer any initial questions you have, and start with a small coding question (i.e. not “re-derive some crazy-complicated graph traversal algorithm we’d expect you to be able to Google if you needed it”).
From there we’ll follow-up with a longer interview, usually about an hour or so long, where we’ll work through a more complicated problem. The problem is usually something we’ve had to solve in the past, and we’re mostly looking to see how we work together and what your thought process is like. There’s no correct answer, and we want it to be more collaborative than anything.
After that, our CEO just likes to hop on one final call, to get a better feel for what you’re looking for out of a job, and to make sure any final questions or concerns you have are addressed.
We’re happy to work through the process as quickly or slowly as you’re comfortable with, keeping in mind that we’re hoping to have the position filled by mid-to-late January of 2017.
This will be our first time hiring a full-time engineer in a while, so I don’t know whether we’re planning to change things up a little bit, but that’s what the process looked like when I joined about two years ago. I do suspect that at some point we’ll want to fly you down to the office to meet the whole team.
