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.
Normal powerday interview. It was pretty easy. Normal OOP technical with a banking question. The case interview was a little harder. Behavioral was normal. Focus on OOP concepts. All interviewers were really nice and helpful.
Easy, one case, one behavioral, one technical interview. By far the easiest interview I ever had. Normal behavioral questions, and for the case, just think from a business standpoint. Prep LeetCode Easy for the technical.
Easy. Four rounds. 1. Behavioral. 2. Coding. 3. A “technical business” discussion. 4. A system design round based on resume and experience. Interviewers were nice and fair. The recruiter was very pushy and didn’t give me time to decide on the offer
Normal powerday interview. It was pretty easy. Normal OOP technical with a banking question. The case interview was a little harder. Behavioral was normal. Focus on OOP concepts. All interviewers were really nice and helpful.
Easy, one case, one behavioral, one technical interview. By far the easiest interview I ever had. Normal behavioral questions, and for the case, just think from a business standpoint. Prep LeetCode Easy for the technical.
Easy. Four rounds. 1. Behavioral. 2. Coding. 3. A “technical business” discussion. 4. A system design round based on resume and experience. Interviewers were nice and fair. The recruiter was very pushy and didn’t give me time to decide on the offer