Capital One Lead Software Engineer interview questions

Recruiter reached out to me via LinkedIn. Quick conversation with him over the phone and then 4 code signal question ( leetcode easy and medium) Then there comes a power day which has 4 sections: design, coding, behavioral and case Design: my interview was supposed to start at 9:00 am, the interviewer did not even show up until 9:08, then he joins over the phone, no apologies, I could not hear anything (I had tested my system over zoom and mine was working fine), he asked me to restart my system twice via chat though the issue was in his system. Then he just starts the problem statement over the phone without any introduction and apologies/introduction . Problem: design banking system with authentication and authorization and It will have 4 different account types: checking, saving, mortgage and auto loan. Have a 1. transfer feature where you can transfer from checking to saving and vice versa 2. Transfer to external like Zelle 3. Transaction history Initially he said design a component diagram in code signal (which was a bit difficult for me to find symbols) then while I was doing, he changed it to do the DB schema, while I was doing DB schema, I was running out of time so I asked him if I could jump back to components and now he changes to tech stack for each components. I was explaining but I already ran out of time and second interviewer (coding section) joined the call Coding: It was an easy problem. Find those two numbers in an array whose sum is closest to 0. I had never checked Glassdoor before the interview but looks like this was their favorite question. I gave the solution within 15 min using 2 pointer approach. Interviewer now changed it to find whose closest sum is 5. That was an easy tweak, just updated the existing logic in another 1-2 min. I had 25 m in left so discussed about their culture, expectations etc Behavioral: Easy straightforward 3 questions like tell me about a situation type Case: It was an easy release cycle related case and fix the existing code which was giving wrong output. Overall it went fine for me except design which I could have done better if I had sufficient time. Later got the email from recruiter saying I had great communication and coachable skills but lacked coding (really?) and design skills