It's a long 4-hour "power" interview, as they call it. It has an architectural part, a coding part, some kind of "business question" part (where a software engineer might be asked mostly irrelevant, mind-boggling questions about calculating profit, making marketing suggestions, etc.), and a behavioral part.

I felt like I fell short on the first three parts. I am not good at the "quickly-code-me-a-solution-while-I-watch" type of thing or "find the bug in 20 lines given 1 minute for each."

Architectural interviews are always open-ended, meaning they are not about coming up with a good architectural solution but rather meeting your interviewer's version of truth. So, you have to use your divination and interrogation skills to figure that out from your interviewer.

Needless to say, I was exhausted from the tension and the incessant 4 hours of speaking. They throw you a 30-minute bathroom break as a bonus, but it doesn't feel much like a break.

This was my second attempt with Capital One, and I don't think there will be a third one.

There were many questions. I vaguely remember one about the cost of a software upgrade based on periodicity: yearly versus every six months. This required calculation.