I applied through an employee referral. The process took 3 weeks. I interviewed at Capital One (McLean, VA) in Apr 2015
Interview
I've done my fair share of interviews and this was easily one of the best managed interviews I've ever done. The entire process is very well thought out and is focused on helping both the candidate and the hiring team gain a good understanding of each other. Everyone I met or spoke to were extremely professional and smart.
The entire process took about 3 weeks. A company recruiter contacted me and set up the initial phone screen.
I was given a coding task to complete before being invited for an in-person interview. I had to take an online HackerRank skills test as well. I did get some questions wrong on the online test but was still asked to come in for an in-person interview.
The in-person interview consisted of 2 rounds of behavioral interviews and 2 rounds of technical interviews. The behavioral interviews were by far the most challenging part of the interview for me. In each round I was asked 3 situation based questions. I had to give very detailed answers in a situation-solution-result format and the interviewers took very detailed notes of my answers. The technical rounds were discussions about the job profile, my work experiences and processes.
Interview questions [1]
Question 1
They will give you plenty of opportunities to ask questions. So prepare to ask lots of good questions by going through their website with an eye on the UI and checking the various platforms they support etc...
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.