I applied through a recruiter. The process took 2 weeks. I interviewed at Yahoo (Carlsbad, CA) in May 2013
Interview
There are two phone interviews before the onsite interviews. I made to the second phone interview. The goal of the first interview seemed to mainly be about getting a good feel for the candidate. The interviewer asked me about past projects I had worked on and any problems that I had to overcome. The second phone interview was a technical test. He asked me technical questions, many of which I had found online from past candidates. The twist was how well you knew the subject, and not necessarily whether or not you got the correct answer. This interviewer's tactic was to continuously ask me "how can you make that solution better" after each question. He told me I got most answers correct, yet I stumbled each time he asked me to find a better solution. The stumbling, I feel, kept me from the onsite interviews.
Interview questions [1]
Question 1
How can you tell if a linked list is circular (goes on forever because it connects to a previous node)?
The overall interview process was positive and well-structured. It consisted of five rounds in total:
Round 1: Initial recruiter screening call.
Round 2: Hiring manager interview.
Round 3: Frontend technical problem via CoderPad.
Round 4: Final loop (3 rounds).
I applied through a recruiter. The process took 4 weeks. I interviewed at Yahoo
Interview
Started with a phone screen round, then 5 virtual onsite rounds consisting of two System Designs, two Behavioural rounds and a DSA round was taken. All of the interviewers came well prepared and conducted the interviews smoothly.
Intro call
System design
Technical discussion
Product collaboration
Technical screening
No dsa and leetcode, no take home assignment which is nice. Hard to prep for either you will pass or fail nothing to really practice
Interview questions [1]
Question 1
Describe a time when, what was your role in xyz project
