Taro Logo

Software Engineer Interview Experience - United States

July 30, 2014
Neutral ExperienceNo Offer

Process

Contacted by an external recruiter and given a phone screen on Skype a few days later. The phone screen was highly technical and I was asked to write code in a shared document. The questions were of average difficulty. I thought I did okay, not great, just okay.

I got an in person interview for the following week. Their office is straight out of a children's fantasy book. Once you walk through that door, you're through the looking-glass. Very colorful, lots of stuff everywhere. Honestly, it made me uncomfortable.

The office is two floors and massive, though it has unique ways of feeling small. Tiny offices in some spaces, tons of people, small small bathrooms. There was a "play room" which is a creepy thing to call it when the place feels a bit like a child's dream to begin with, but anyway it was a poor excuse for a break room. It's like they just had a couch and a TV and an arcade machine because it's the startup thing to do.

I was brought into a (very) tiny room for my interview. There were probably half a dozen around it, just like it. The first question asked was essentially asking for a recursive algorithm. Basically assuming you have nodes which point to and from different nodes (multiples, sometimes), retrieve all the nodes within x steps. This is a frustrating question unless you're comfortable and in a good environment. On my own, I'll solve this problem just fine.

I was given a few sharpies which had frayed tips and low ink. The whiteboard was an abrasive wall painted white, so writing on it was awkward. It resulted in very very messy writing. That combined with my imperfect performance...it was all pretty hideous and horrible to me. It worked, but it was just brutal.

They asked running time, which was so hard to calculate when I could hardly even read my own code.

For what it's worth, the gentleman who interviewed me seemed SUPER high on ZocDoc, like indoctrination scary... be careful what you say, you might get someone who really only wants to hire a "Zoc Star".

The next gentleman was a bit better and he asked me design questions. Way friendlier, way more reassuring. Still this all felt like a waste of time, trivial simple design stuff. I mostly went through the motions.

The whole process took about two hours. They told me to set aside 4 hours, but reassured me that the interview was not ending early, that it was just extra time set aside incase it was needed. Which sounds like a really really nice way of saying, we're ending the interview early.

Questions

We have individual nodes connecting to and from other nodes. Each node could point to multiple nodes, or from multiple nodes. Generate the data structure to store it all and the function to retrieve a list of all the nodes within x hops from a particular node.

Was this helpful?

Interview Statistics

The following metrics were computed from 59 interview experiences for the Zocdoc Software Engineer role in United States.

Success Rate

17%
Pass Rate

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

Experience Rating

Positive46%
Neutral24%
Negative31%

Candidates reported having good feelings for Zocdoc's Software Engineer interview process in United States.

Zocdoc Work Experiences