Getting an Interview
Getting an Interview
Interviews for Top Jobs at ZocDoc
- Operations Associate (59)
- Software Engineer (30)
- Sales Executive (22)
- Inside Sales Executive (21)
- Business Origination Associate (17)
- OUTSIDE SALES (11)
- Sales Origination Associate (11)
- Sales (8)
- Account Executive (7)
- SOA (6)
- Recruiting Coordinator (4)
- Recruiter (3)
- Senior Software Engineer (3)
- Software Engineer Intern (3)
- Principal Software Engineer (3)
- Director of Engineering (3)
- Technical Lead (3)
- Technical Operations Associate (2)
- Customer Service (2)
- Executive Assistant (2)
- Operations Manager (2)
- BOA (2)
- Outside Sales Executive (2)
- Finance & Strategy Associate (2)
- Practice Success Associate (2)
- Part-Time Operations Associate (2)
- Intern (2)
- Inside Sales (2)
- Patient Operations Associate (2)
- Senior Level Leadership (1)
Software Engineer Interview
I applied online. The process took a week – interviewed at ZocDoc in June 2015.
I applied via the ZocDoc website. I received an email back from a recruiter a few days later letting me know that my skill set was typically what they were looking for and that we should schedule some time to talk. The recruiter was fairly inflexible with her available hours. When I finally did get her on the phone, I thought things were going well until she kind of blind-sided me by saying she was going to ask me a technical question (before I even spoke to any engineers). The problem, of course, is that you cannot really pose any questions to the recruiter since she was quick to remind me she isn't an engineer. The entire experience lacked the conversational aspect that technical interviews often have since I was just required to immediately provide an answer to her without any real time to think about it. Anyway, I provided an inefficient answer quickly since I was apparently under the gun. She said they would get back to me by the next day. The next day I received a generic rejection email rather than a phone call or even a personal email from the recruiter I spoke to. I thought the entire experience was very unprofessional, since I had actually talked to her on the phone. Plus, having a technical recruiter ask a technical question seems wrong to me.
- Remove duplicate integers from very large array. Answer Question
Other Interview Reviews for ZocDoc
Software Engineer InterviewNo OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 2 weeks – interviewed at ZocDoc (New York, NY) in December 2014.
Contacted by a recruiter. First round skype tech interview - my interviewer was super nice and seemed really smart. After normal self introduction of myself, he gave me a fairly simple code problem to solve (string validation related). I come up with stack based solution and solved it quickly. He made a slightly more complex case and I also solved that. Soon I got onsite interview. First round is basic introduction, experience, skills etc. Then some whiteboard coding and the interviewer kept asking "what if you cannot use this feature" which was really inspiring. It went well. Second round was object oriented design for a real-world problem. This was heavily based on discussion. The interviewer was very "cool" and made me a little nervous. That went just OK. Then a principle engineer came in with another problem. After design I was asked to code it while we discussed it. I did OK. Then I got an skype interview with CTO. A interesting probability related question was asked and I quickly solved that. Then he changed to another scenario to make the case more generic. I stopped for a little while and coded a solution. He asked about big O and I got that. He asked me whether it can be improved and I quickly mentioned some way to reduce a couple of loops. He also hinted that the search can be improved and I quickly grasped the idea. He then said OK that's the basically the correct answer. When can you start etc. He seemed busy and didn't leave me any chance to ask him questions. I was then contacted my recruiter again and I learnt that they typically leave you a 24-hour window to accept their offer. I thought I was getting an offer soon, but after 1 week I was told that their hiring period was "just over" so that couldn't hire me. Which I don't quite understand. But I don't care because I got a way better offer soon after that. Overall very positive feeling for the whole process. I don't see much of a "startup ego" like others mentioned. Their floor make noise when waking on it. And they seriously lack restrooms and the meeting rooms are super small.
- Design a file system Answer Question
Software Engineer InterviewNo OfferNegative ExperienceAverage Interview
I applied online – interviewed at ZocDoc.
Contacted by recruiter. Nice guy. Asks me some questions about my background, we chat for a bit. Told I would be contacted via email to set up a Skype interview. Skype interview is scheduled for 1.5 hours, interviewer shows up late, seems disinterested the whole time as we talk. Asks one question, stops interview after 40 mins. Never gives any feedback. About a week later I get an email saying I would not be moving forward with the process. Essentially, it seemed as though the person I interviewed with had already decided before the interview started that I would not be getting the position.
- Create a hash table out of a list of names. Answer Question
Software Engineering InterviewNo Offer
Approached the tech recruiters at a tech recruitment event. Was given two technical questions on the spot. The questions were regard algorithms and data structures. I was given about 10 minutes for both questions.
- Was asked to remember an algorithm that was not quite popular. Answer Question
Software Engineer InterviewNo OfferNeutral ExperienceEasy Interview
I contacted a recruiter on linkedin (I actually came to know about him via a friend) and they quickly scheduled a skype interview. They told me that the interview will be for 2 hrs, but they can be flexible in scheduling the interview after regular business hours (like around 5:30). So I scheduled and interview with them. I haven't heard back from them, so I don't know if they're going to call me for further rounds or not.
- They asked me just one question during the interview which was as follows: Given an array such as [6, 2, 3, 6, 3, 7] return the output as [6, 2, 3, 7] (essentially preserve the order and duplicate elements should not be repeated). After several question ans the interviewer told me what exactly he's looking for in the output. It was a straight forward question which i was able to sold under an hour and then the interview was completed. I was hoping that someone else might call me for the next hour (since I was told 2 hour skype rounds), but nothing. 2 Answers
Software Engineer InterviewNo OfferPositive ExperienceDifficult Interview
I applied online – interviewed at ZocDoc (New York, NY) in October 2014.
I applied online. They got back to me the same day to schedule a phone interview. I had one Skype interview followed by an on-site visit which consisted of four different interviews. Then I had one more Skype interview because the CTO wasn't in the office on the day of my visit.
- This wasn't incredibly difficult, but one guy asked me to design Facebook (at a high level) and another asked me to design Twitter. I thought these were really cool questions because they tested overall design smarts instead of obscure algorithmic stuff. 4 Answers
Software Engineer InterviewNo OfferNeutral ExperienceAverage Interview
I applied online. The process took 5 days – interviewed at ZocDoc.
I applied online via their website. A recruiter emailed me a few days later and we set up a phone interview for the next day. It was a short (probably 10-15 minutes) interview where he asked me a few questions about my background and then spent the rest of the call talking about how much he loves ZocDoc. It felt like he was trying to sell the company to me. We set up a Skype interview for the next week. A software engineer ended up calling me and said that their Skype account was not working. He asked me some personal questions and then he shared a document with me and asked me to write a program to detect a palindrome. He was very nice but seemed to mumble a bit - it was hard to hear him. 45 minutes later, he left the phone and another person came to interview me (I believe he was some sort of manager). He was very nice again but asked a trickier question about detecting subsequences with the largest sum. I stumbled a bit (I'd like to chalk it up to it being my first interview, but who knows?) and he started to seem a bit disinterested. All in all it was an okay process. I wasn't expecting a call back and got an email a few days later saying they would not like to pursue anything.
Software Engineer InterviewAccepted OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 3 weeks – interviewed at ZocDoc (New York, NY) in September 2014.
- a deep discussion of hash table optimazation 1 Answer
The offer was decent, so I did not try to negotiate. Plus my base salary with my current employee was fair low. So i was happy with the package.
Software Engineer InterviewNo OfferNeutral ExperienceDifficult Interview
I applied through a recruiter. The process took 2 weeks – interviewed at ZocDoc.
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.
- 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. 1 Answer
Software Engineer InterviewNo OfferNeutral ExperienceAverage Interview
Had a skype interview with a very nice software engineer. The interview lasted about 45 minutes and most of the questions were focused on OOP concepts and data structures. I felt like I did very well answering the questions, and the interviewer said at the end that he would be scheduling another interview for me. About 2 days later, I received a rejection letter without any explanation.
- Big O analysis for different Data Structures Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review