Me postulé a través de un reclutador. Acudí a una entrevista en Capital One en mar 2024
Entrevista
It's a long 4 hours "power" interview as they call it. It has architectural part, coding part, some kind of "business question" part (where a software engineer could be asked mostly irrelevant mind boggling questions about calculating profit, making marketing suggestion etc) and behavioral part. I felt like I fell short on first 3 parts. I am not good at quickly-code-me-solution-while-i-watch type thing or "find the bug in 20 20-liners given 1 minute for each". Architectural interviews are always open ended meaning they are not about coming up with a good architectural solution but rather meeting your interviewer's version of truth. So you have to use your divination and interrogation skills to figure it from your interviewer. Needless to say I was exhausted from the tension and incessant 4 hour speaking. They throw you a 30 minutes bathroom break as a bonus, but it's not felt much like a break. This was my second attempt with CapitalOne and I don't think there will be the third one.
Preguntas de entrevista [1]
Pregunta 1
There were many questions. I vaguely remember one about a cost of software upgrade based on some periodicity: year vs 6 months. It had to be calculated.
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