(Sorry in advance, English is my second language so please excuse any mistakes in grammar) The interview process was pretty standard...phone screen with algorithm/coding exercises, then an onsite set of interviews with several algorithm/coding exercises and one design (class design) interview. The last interview was with the CTO, and his behavior is one of the reasons why I decided not to take this job. He just seemed extremely cold and uninterested. But, I guess I did ok, because I ended up getting an offer. It was a weird vibe, though.
In general, I felt throughout the process that this was a company trying so hard to be hip and "start-up like" but really really corporate feeling. It doesn't help matters that they do .NET dev (ew), but I just felt very odd about this interview process. I ended up accepting a better offer at a major tech company in the Silicon Valley...which, though being a big-name (starts with a G hehe) felt much more transparent and less like an old corporation trying to be hip.
I don't remember the exact questions (and probably shouldn't disclose them even if I did), but these are easy, standard algorithm/whiteboard coding questions.
If you are nervous, study up on graph traversing, OOP design, and some (very) basic probability theory.
But really, this was one of the easiest technical interviews I've been through.
The following metrics were computed from 42 interview experiences for the Zocdoc Software Engineer role in New York, New York.
Zocdoc's interview process for their Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Zocdoc's Software Engineer interview process in New York, New York.