Me postulé a través de una facultad o universidad. El proceso tomó 1 día. Acudí a una entrevista en Capital One (Pittsburgh, PA) en feb 2016
Entrevista
I was reached out by a recruiter for an on campus interview, which turned out to be a single, final round interview. The interview itself was straightforward and consisted of a behavioral round, technical round, and finally a case study round. The recruiters were very quick and I was notified within the same day for an offer for either a Data Engineer or Software Engineer position.
I chose to decline because my ambitions for now do not lie with a large company.
Preguntas de entrevista [1]
Pregunta 1
You have two linked lists where each list represents some positive number. The ith node in the list represents the ith digit (0-9) of the number. Return a new linked list which represents the sum of the two linked lists.
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