I applied through college or university. The process took 1 day. I interviewed at Capital One (Columbus, OH) in Oct 2015
Interview
This interview was for the Technical Development Program, so YMMV for other software engineering roles. The interview process as a whole was a very enjoyable process, with three interviews back to back to back. The first interview was a behavioral one (talk about a time you worked in a group, one time you had a disagreement, etc.). The second interview was a technical one, and the third was a case study.
The technical interview wasn't very challenging but I could see how it could be used to weed out candidates that basically knew nothing. The first question was just a "talk about how you would implement a few classes" given a certain business requirement. The second question was a very simple string manipulation problem, and finally the last question basically asked to see how comfortable you were with objects and linked lists. While my questions were easy, I had heard that there were other more difficult questions as well.
The case interview was also very straightforward. The main purpose is basically to see how you talk through a problem and how you reason through it. You're given a business problem (non technical) and you're asked to analyze the benefits/cons of certain actions that you can take. As a person applying to the software engineering role, I did receive a lot of guidance on the problem since it was *kind of* outside my domain. Nevertheless, if you're able to do simple multiplication and algebra, it should be a breeze. I received an offer within 8 hours and was an all in all very pleasant experience
Interview questions [1]
Question 1
Talk about a time you explained something technical to a non-technical person?
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.