A renowned company.
A lot of great people work here.
There are 3 pretty big downsides to working at Capital One as a SE.
The first is that there is no DEV environment, which means backend teams are constantly pushing experimental code to QA. This frequently takes down the QA environment, which directly impacts frontend engineers like myself. As a result, most of my day is spent going through Splunk logs trying to figure out which API went down and tracking down the responsible team on Slack, leaving me with little time to do my own tickets.
The second is the unfair promotion and PIP system. Everything happens behind the scenes, and there is zero transparency as to who got promoted and why. I can't help but feel it frequently comes down to who your boss's "favorite" is, as opposed to actual performance.
The final downside is the PIP (i.e., being let go) system itself, which is based on stack ranking. Combined with the promotion system, it creates a toxic environment where no one wants to help each other due to conflict of interest (and a risk of being let go yourself).
Overall, working at Capital One is not good for your mental health, so I would recommend working no more than a couple of years, put it on your resume, and move on.
There's no point in giving advice to management, since they won't listen to you anyway.
There is one interview with three parts, each 45 minutes. The order is random. For me, I first had the technical, then behavioral, and finally the case interview. After the second interview, you have a 10 to 15-minute break.
OA first, then a virtual job tryout, followed by a Super Day that included coding and a case. Relatively simple, LeetCode Easy/Medium. They cared more about thought process and problem-solving skills.
My first interview was the online preliminary questions, so technically not the real interviews, but they used CodeSignal. The CodeSignal was pretty hard. It included string questions and dynamic programming (DP). These were not impossible, but mo
There is one interview with three parts, each 45 minutes. The order is random. For me, I first had the technical, then behavioral, and finally the case interview. After the second interview, you have a 10 to 15-minute break.
OA first, then a virtual job tryout, followed by a Super Day that included coding and a case. Relatively simple, LeetCode Easy/Medium. They cared more about thought process and problem-solving skills.
My first interview was the online preliminary questions, so technically not the real interviews, but they used CodeSignal. The CodeSignal was pretty hard. It included string questions and dynamic programming (DP). These were not impossible, but mo