Candidatei-me por meio de recrutador(a). O processo levou 2 meses. Fui entrevistado pela Capital One em jun. de 2019
Entrevista
Don't trust the recruiters. If they reach out to you, don't. They will jeopardize any of your opportunities in applying at Capital One again, regardless of the city. They will lie to you about the coding challenges only taking about 30 minutes to complete. It takes much longer than that. They will lie to you about wanting to keep your information on file for other opportunities if they don't proceed further. Apply on your own, don't use them if they reach out. It's just a trap to fill their quota, so they can get paid. They are not looking for the best. They are looking for anyone to exploit to meet their quota and hinder any future potential opportunities.
Perguntas de entrevista [1]
Pergunta 1
What is your agile methodology like at your current position
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.
Perguntas de entrevista [2]
Pergunta 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