J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 1 jour. J'ai passé un entretien chez Capital One (Columbus, OH) en oct. 2015
Entretien
This interview was for the Technical Development Program, so YMMV for other software engineering roles. The interview process as a whole was a very enjoyable process, with three interviews back to back to back. The first interview was a behavioral one (talk about a time you worked in a group, one time you had a disagreement, etc.). The second interview was a technical one, and the third was a case study.
The technical interview wasn't very challenging but I could see how it could be used to weed out candidates that basically knew nothing. The first question was just a "talk about how you would implement a few classes" given a certain business requirement. The second question was a very simple string manipulation problem, and finally the last question basically asked to see how comfortable you were with objects and linked lists. While my questions were easy, I had heard that there were other more difficult questions as well.
The case interview was also very straightforward. The main purpose is basically to see how you talk through a problem and how you reason through it. You're given a business problem (non technical) and you're asked to analyze the benefits/cons of certain actions that you can take. As a person applying to the software engineering role, I did receive a lot of guidance on the problem since it was *kind of* outside my domain. Nevertheless, if you're able to do simple multiplication and algebra, it should be a breeze. I received an offer within 8 hours and was an all in all very pleasant experience
Questions d'entretien [1]
Question 1
Talk about a time you explained something technical to a non-technical person?
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