Solicité el puesto a través de la escuela superior o la universidad. El proceso duró 5 días. Acudí a una entrevista en Capital One en mar 2015
Entrevista
The process itself took about a week. I had to schedule an on-site interview because the bad weather prevented the recruiters from flying to my University. The date that I picked was 3 weeks in the future. I flew to Richmond, Virginia the day before and had my interview the next day. The interview itself was not hard. There is a behavioral (tell me about a time when you...), job fit(technical questions plus work preference), and case interview (business related). I thought I did well but sadly I did not get an offer.
Preguntas de entrevista [1]
Pregunta 1
What is the difference between overloading and overriding?
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.
Preguntas de entrevista [2]
Pregunta 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