I applied through college or university. The process took 3 weeks. I interviewed at Capital One (Richmond, VA) in Mar 2017
Interview
Met them on campus and applied online. I was contacted over email asking if I could come down to the Richmond location from Maryland. The follow up email contained a lot of prep material and details about the day. Capital One put me in a hotel and paid for my expenses for the whole trip.
After arriving at the campus, we were split into groups of ~4 and taken on a tour by current employees. Thiis part was informal and my guide was very easy going and answered a lot of our questions about the work environment and how the rotations work.
The formal part of the interview had 3 parts, behavioral (pretty standard), technical, and case. The technical part was a few coding questions on the whiteboard. While not terribly difficult, it is hard to think of all the different input cases so make sure to consider all possibilities when coding. The case interview for the technical position was not like the prep (business) video they sent. It was basically a coding problem in a business setting. The coding part was pretty easy but for this part they care more about your problem solving and analytical skills.
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.