I applied online. The process took 1+ week. I interviewed at Zocdoc (New York, NY) in Mar 2011
Interview
My interview process with the company was very smooth and an overall positive experience. I first had a call with a recruiter, followed by a phone screen with the CTO, and last came into the office to interview with several engineers and have lunch with the team. They asked a lot of the typical questions that are asked during interviews of software engineers, and were very pleasant to talk to during the process. Towards the end, the CEO popped in to say hi and after all 1:1 interviews were conducted the CTO came in and personally gave me an offer. The work culture is very fun and enjoyable (lots of drinking and socializing on weekends and regular Team Fortress 2 LAN parties after work). Looks really great for engineers but it seems like some of the non-engineers feel under-appreciated. As an engineer, if it looks like you fit well into the company culture, I would totally consider applying.
Interview questions [1]
Question 1
Why do you want to work for ZocDoc over other companies? What makes us different?
Well prepared panel with questions that aimed at testing ability to resolve technical problems in real time with a small amount of information available and with the pressure of time to deliver on a range of potential solutions
Interview questions [1]
Question 1
Technical knowledge questions and specific exercises
I applied online. I interviewed at Zocdoc (New York, NY)
Interview
I talked to the recruiter, who told me about the role and the company. The next step was to schedule a screening interview. The screening interview was with a senior engineer and it was technical and involved some coding and questions.
Interview questions [1]
Question 1
Q: Have you worked in a cross-functional environment?
I applied online. The process took 2 weeks. I interviewed at Zocdoc in Feb 2022
Interview
Pretty standard phone screen: shared my personal background, professional aspirations and then they shared background on company, the position and answered any questions.
Standard tech screen followed-- average difficulty. Anagrams. No curveballs. Friendly interviewer.
Final interview was "virtual on-site". About 5 hours total split across 5 sessions.
First was another pairing challenge that involved trees and file paths.
Then there was a standard behavioral interview.
Following that was an OOP interview-- but it was more of a conversation. The challenge was a standard OOP interview topic, so nothing crazy. Talking about design decisions and SOLID principles, etc will get you points, of course.
Then there was a systems design interview in which I had to design a popular social media site.
Last was a conversation with an engineering manager, which was a conversation about my background and experience. I also got to ask a lot of questions of my interviewer, which was nice.
Overall, I had a positive experience in the interview process. It was a simple straightforward three step process. Didn't waste my time or theirs. The folks at every stage were cool.
Unfortunately I did not prepare enough for the systems design interview and fell flat on my face which, according to the recruiter, was the only reason in the "No Offer".
Overall, still a good experience. The recruiter gave me a lot of feedback afterwards, unprompted. Always reflects well on the company/recruiting process when that happens. Much better than a generic templated rejection email.
Interview questions [1]
Question 1
Using a language of your choice, create a program that returns a boolean indicating whether two words are anagrams of each other.
