Ho presentato la mia candidatura tramite l'università. Ho sostenuto un colloquio presso Capital One
Colloquio
Underwhelming and not challenging, but their are things you just have to be ready for. What I just couldn't put together and probably made me look incompetent was just knowing to say API instead of server or network to the question of how services talk to eachother, so it is just little things like that that, like in most interviews, you just have to be ready and know.
Domande di colloquio [1]
Domanda 1
How would you refactor this code? And it was literally just consolidating if statements into while loops and moving them around.
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.
Domande di colloquio [2]
Domanda 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