Capital One Lead Software Engineer interview questions

I was cold called via an old resume. Rather than go into the resume the recruiter very apologetically told me that the first step was a code test. I normally don't accept those anymore at this point in my career, but she said it was 70min, but recommended I read the questions first and just skip it if I didn't like it. Lot of red flags when the recruiter seems to think the process is rubbish. First question was word salad that took five minutes to read, but relatively easy. However, a bunch of tests failed requiring re-reading for a bunch of nuance. 20min gone. Second question was simply gibberish. Third was the most concise, but would also have taken twenty minutes to write. The fourth was mostly useless narrative and I didn't bother tying to figure out what the problem itself was. It definitely seemed like a random grab bag of two-hour questions jammed into 70min. Any company that gates their senior positions like this deserves what they get (cheaters).

Efficient but longer interview process. Leetcode-type code screen before talking to the recruiter. First 2 questions were softballs but the last two were pretty gnarly. Recruiter interview was straight forward. He shopped my resume around and I had one hiring manager very interested. Interviewed with the hiring manager which was a typical introduction interview. Went over experience and resume. Very casual and interesting. I got to learn about the potential role and team. Power day involves interviewing with 4 people over several hours. First interview was an OOP design kind of question. You got to choose your language and you used an online IDE. I'd say easy for a anyone who has built their own stuff. It needs to run and compile and you have the opportunity to go back if you get stuck on something and move ahead to the other requirements. Second interview involved systems design and was a bit tougher. You can get lost in the weeds if you don't manage your time well. Expand as much as you can and talk over what your system can cover such as performance and other scaling considerations or limitations. Third interview is a "Case Study" which I had no idea what it meant but mine involved walking through some business rules with a director and just working through some problems. Almost like a word problem but no math. Just ingesting requirements and walking through things. Final interview is one that involves HR type questions such as how to handle conflict resolution and things you've done in your career. Probably my least favorite as it requires you to have things happen in your career that just may not have happened or you have to fabricate a story.