The process was a little slow.
I applied and completed the initial assessment within 3 days. The test went well; I answered 4 questions.
I gave their interview back in 2023, but they did not get back to me even after 1 month.
Then, I suddenly received an email that I had been rejected.
The coding questions were not very hard! There were four questions with increasing difficulty, at least for me, but I was able to solve them.
A question that I remember was: A lot of non-essential info, essentially it boiled down to: I had to mimic the distribution center according to the conditions provided.
Given an array CenterCapacity that contains a center's capacity between 1 to 5, and a string array dailyLogs. It contains info in the form of strings, like "Packages" and "Closed". If it is a package, then I will keep using a center until it hits its capacity given by centerCapacity[j], and then sequentially move on to the others. If we complete a cycle, the capacity gets restored.
However, if we encounter a "Closed" entry, it means that this jth center is now closed until otherwise stated, and we cannot use it to store packages. Then we continue until all packages are processed or we reach the end of the daily logs. Finally, I had to return the index of the center that stores the most packages (in case of a tie, return the bigger index).
The following metrics were computed from 1 interview experience for the Capital One Associate Software Engineer role in New York, New York.
Capital One's interview process for their Associate Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Capital One's Associate Software Engineer interview process in New York, New York.