I applied through university. The process took 3 weeks. I interviewed at Capital One (Richmond, VA)
Interview
I stopped by the Capital One booth at my schools Career fair. Shortly after I was contacted by a recruiter to set up an on campus first round interview. The interview was purely behavioral, consisting of questions to the tune of "How did you overcome X." I was told in my interview that I had preformed well that that I would be advancing to the next round (My interviewer must have had a long day of duds).
Final rounds consisted of three interviews, lunch, and a tour of the Richmond Capital One office. At final rounds there was a group of ~15 candidates who, I assume, all went through the same process.
The three interviews consisted of a case interview, a technical interview, and a behavioral interview. The interviewers were all kind and gave me feedback at the conclusion of each interview. The interviewers were a mix of management staff and software engineers. After the interviews one candidate was asked to stay for further questions (I assumed this meant he was receiving an offer), while the rest of the candidates were shown out of the office. Much to my surprise I received a phone call not two hours later, while I was still driving home, congratulating me on the interviews and giving me an offer.
After interviewing I got the impression that while I was applying for a software development position the focus of the interviews personality and critical thinking. This was a little off-putting because it makes me believe that it is possible to be hired at Capital One as a Software Engineer without being a great coder. For technical preparation I would recommend purchasing or downloading a copy of Cracking The Coding Interview 5th edition. All of the technical questions I was asked came directly, WORD FOR WORD, from this book. Proper preparation, along with good communication skills is a recipe to preform well and get a great offer.
Interview questions [1]
Question 1
The case question was about mortgage securities, a topic I am not particularly familiar with. Luckily after some question asking and thinking aloud I was able to work my way through the case.
4 rounds of interview including coding , design , case study, behavioral after clearing the code signal assesment. Coding was medium hard of 2 questions each. case study and system design was difficult.
This took a bit longer than expected, stretching over several weeks. The technical rounds were intense, featuring an LRU cache implementation and a problem on detecting duplicate transactions within a 60-second window. I was nervous at first, but it clicked for me when I realized I had practiced a similar approach on PracHub just days before. Unfortunately, I didn’t receive an offer in the end, but the experience was a solid learning opportunity. The behavioral questions felt straightforward, so I wish I had made a stronger impression in the technical segments.
Interview questions [2]
Question 1
Implement an LRU cache with get and put operating in O(1)
Un proceso largo, pero sin mucha complicación en el proceso. Empresa atenta en todo momento a dudas y disponibilidad de tiempo para las entrevistas. Exámenes con temas sencillos y complejos. Variedad en los ejercicios
Bowls
Get actionable career advice tailored to you by joining more bowls.
Want the inside scoop on your own company?
Check out your Company Bowl for anonymous work chats.