I applied through college or university. The process took 1 week. I interviewed at Capital One (Baltimore, MD) in Oct 2016
Interview
Applied through university and did an on-campus interview consisting of 3 45-minute interviews. 1 technical, 1 case, and 1 behavioral. They all went pretty smoothly and were very nice and happy to answer any questions I had. Technical interview were textbook data structures questions involving strings and linked lists, really basic ones that you'd find in CTCI. Also had some OOP design. The case interview was a little rocky, I understood what the interviewer was saying and I could see the solution but had a slightly hard time getting the interviewer on the same page with me, but eventually got there. For the behavioral, really prepare some anecdotes in the SAR format (Situation, action, result). The interviewer literally records each part separately and explicitly told me to format my answers like that.
Interview questions [1]
Question 1
Talk about a time you explained something technical to someone non-technical.
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.