I applied through a recruiter. The process took 1 day. I interviewed at Capital One (Tysons Corner, VA) in May 2016
Interview
There interview involved speaking with project manager and team lead. It was very relaxed and natural conversation with the interviewers. I wouldn't say it was the hardest interview ever but they asked me some technical questions that brought me back to my computer science under graduate days. Other than that, I felt that it went very well.
It was a very fast turn around. They got my resume and wanted to bring me in for a face to face interview the next day. I heard some informal feedback from my recruiter almost immediately.
Interview questions [1]
Question 1
Why do we keep variables on the heap in Javascript?
Interviewed for an engineer position, the interview was a joke. Asked basic OOP question with a few follow ups - no system design portion. Interviewer was very laid back and chill, didn't take it to seriously.
Was not too difficult. three total interviews all on the same day back to back. technical one, behavioral one and a case which was more of just a debugging question
Expecting a challenging experience, I found the interview at Capital One to be intense, particularly during the system design section. The question on designing a rate limiter with a token bucket algorithm took me by surprise; mid-way through the problem, I realized it was very similar to a drill I’d practiced on prachub.com just days earlier. The technical rounds included several DSA questions, and the interviewers were thorough but supportive. Ultimately, I received an offer and happily accepted, feeling well-prepared despite the pressure.
Interview questions [1]
Question 1
Design a rate limiter using a token bucket algorithm and discuss how it would handle bursty traffic and distributed deployments.