Capital One Software Developer interview questions

I applied for the position online and contacted by the recruiter a couple days later. He sent me an assessment, I completed it and he then forward my application to the Hiring Manager. They schedule a 4-hour long back-to-back interview including 2 technical, a behavior and a case (tech) interview. The first technical interview was about designing an application that involve a smart meter that send data every minute, tenant can view their OWN usage, and manager can only view usage on building basis. The second technical interview was a coding challenge. Find least amount of change for the sum. I had a hard time solving this problem to be honest. I prefer to solve it iteratively, but the interviewer insist on solving it recursively. At the end, I couldn't solve it. So I ask if he can provide some pseudo code on how he would've solve it. He refused saying that he's not allowing to????? Ffter I did some googling, I found the answer. Apparently, this is a very common problem and yet he can't allow to share his answer. Whenever an interviewer asked me to solve a problem, I always asked them to solve it afterward. 80% of the time, they can't or they can't walk me through their logics. This is the exact reason why I'm always against whiteboard interview. You do not ask question that you can't solve in the same amount of time under pressure. So I asked him if he can solve the problem iteratively rather than recursive and why recursively when you can solve it iteratively since the input array can be large. He failed to give proper answer since he probably just memorizing the answer instead of understanding it. Note to interviewer, if you ask whiteboard question, make sure you can solve it in the same amount of time and pressure. Don't pull question out of thin air or I'll embarrass you. The interviewer clearly have no skills in solving the problem since he can't even explain his solution. The last two were behavior and case study. Pretty common questions. Overall, the experience was bad. You are interviewed by the people you'll never see again if you get an offer there. What make it worse is the guy who ask technical question were probably pull questions out of leetcode or hackerrank, look at the solution and thought "Yea, the solution is easy enough" without attempting himself. The solution can be simple, but to get to that solution isn't easy. The technical interviewers were shock when I interviewed them back, I guess they're not used to getting asked during an interview. Remember, interview is two way. I don't like to work people who think they're better because they know the answer beforehand. My interviewers were all Indian, my experience interviewing with Indian interviewers is that some of them can make you sound like an idiot if you can't find the answer within minutes. However, when I interview them back, they failed to show me that they can do better.