Taro Logo

Software Engineer Interview Experience - New York, New York

September 1, 2014
Positive ExperienceGot Offer

Process

I was actively looking for jobs in New York City with a few pending onsite interviews, so the interview process in ZocDoc was very fast. Since I was not based in New York, the interview process was a bit different.

Summary: First round: two rounds of Skype interviews(back to back, 45 minutes each) Second round: two rounds of Skype interviews(back to back, 60 minutes each) Final round: two round of onsite interviews(back to bck, 60 minutes each)

Keyword: frontend, undergraduate, entry/junior, online shared coding, Skype with webcam

Overall, all the interviewer are nice and easy going. Questions are average difficulty, so most of them you can start with brute force and work upon it from there.

!!!!!!Try to give the time complicity and space complexity in each of your solutions.!!!!

These are the steps you may expected from the interview:

  1. All interviews started with a introduction to the company and the interviewer.
  2. The common question after is tell me about yourself (keep it 99% technical is my advice).
  3. A easy tech question following just to get your feet wet.
  4. Some follow up to test you understand of basic ds/algorithm knowledge.
  5. A link of online coding web app will be send over Skype.
  6. Coding time. (please express you thinking process along the way. After finishing the code, demonstrate one more time from the beginning and eye-ball your bugs.)

Detail: First Round: Questions are related to algorithm/data structure. For a company like ZocDoc, you should have a deep understanding of the BASIC ds/algo. Study hash table and understand what is happening behind. Tips: try to sneak in some ds/algo comparison while you are making choices between them to show off you understanding of the basics). In the first interview, I was honest to tell the interviewer I have done a similar question the others day. He appreciated my honesty and gave me another coding question.

Second Round: I got the email to move toward soon after. Both interviews started with questions related to very basic OOP JavaScript(you better know it if you are interviewing a frontend developer position). I had a onsite training in my current company using online course-ware. All concepts behind the questions are covered in the training. ds/algo concepts were tested along the way. The first interview ended with coding a algorithm question. A terribly hard question was asked at the very end, but it turned out that the interviewer just wanted to discuss the problem with me.(Prob I had finished all the questions).

The second interview ended with a little OOP design in JavaScript. I was not familiar with the concept(not a tricky one/I should have known it), so it took a looooooog time for the interview to explained. The explanation took about like 20 minutes, while the coding took about 5 minutes. After the basic design was done, he asked me what features might be added? I gave him two answers using the concepts of MV* and RESTFUL. I did not think I could move on, since I thought i kinda failed the very hard question at the end of the first interview. And it took too much time for the second interviewer to explain the concept to me at the second interview.

Third Round: I was quite surprised when I got the onsite interview soon after the second one. Everything are paid by ZocDoc(flight, taxi, meal...). The first interview was meant to be a design round. But after I demonstrated all the needed classes/properties/methods, the question came to a ds/algo related validation question involved in the design problem. I wrote limited lines of code on the write board, but the interviewer said expressing my thinking process clearly was much more important. Second interview was with CTO. Start with common introduction of the company and himself, followed with "tell me a bit about yourself". A easy math question was ask to get the coding started. The actually coding question are related to probability/ds/algo.

I started with a brute force solution. He asked me is there is any better one. The interview ended with a fairly general discussion. Why you are looking for a new job. Why ZocDoc? After the interview, he asked me if anyone had shown me the dev part of the company. I said I had a generally tour. Then he got someone along the way to give a me a tour of the dev part.

Sooner after I got the offer.

At the very end, I want to express my BIG thank you for GlassDoor for helping me along the way. All the reviews have been really helpful.

Questions

We had a deep discussion of hash table optimization.

Was this helpful?

Interview Statistics

The following metrics were computed from 42 interview experiences for the Zocdoc Software Engineer role in New York, New York.

Success Rate

21%
Pass Rate

Zocdoc's interview process for their Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.

Experience Rating

Positive60%
Neutral14%
Negative26%

Candidates reported having very good feelings for Zocdoc's Software Engineer interview process in New York, New York.

Zocdoc Work Experiences