J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Capital One (Arlington, VA) en févr. 2014
Entretien
The interview process was very informal, despite a few questions read from a very HR-sounding document. I met with three people. I wore a suit, but now I know that was definitely not required given the laid-back, startup-like atmosphere. I had two or three phone screenings prior to the in-person interviews.
Questions d'entretien [1]
Question 1
There are 100 people standing near the beginning of a row of 100 closed doors. The first person goes down the row and opens every door. The second person closes every 2nd door. The third person changes the state of every 3rd door, and so on. Write a routine to find the state of door X after person Y passes by.
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.
Questions d'entretien [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