I applied through a recruiter. The process took 2 weeks. I interviewed at Capital One (McLean, VA) in May 2019
Interview
5 - 1 on 1 interviews after they flew me out to interview. I was strongly recruited over my own objections that my experience wasn't the exact right match and that the cost of living was too high. This lead me to believe that this was some unicorn company that understood that developers can and do learn new programming languages (all the time)..they are not. So after wasting 2 days of my time flying out there they told me they decided they didn't need my skill set. Ummm, what? You aggressively pursued me. Also, my background is nearly the same as 2 of the interviewers before they came to work here. Capital One doesn't value the candidate's time at all. They claim to be a tech company first and bank 2nd (heard this 5 times ) but they don't know how to do a skype interview? 2 of the interviews were 'company fit', which to me is code for age/race discrimination. I don't think the hiring managers even read my resume before I came on site. Huge disconnect between their corporate recruiter and hiring managers. Not surprising that their recruiter worked in a different state than the hiring manager and their team. I sat in a tiny room for 6 hours while they paraded 5 people in to interview me. They took my lunch order by email before I got there. The secretary handed it to me to eat by myself in that same tiny room by myself during a 15 minute gap between interview 3 and 4. Red flags - no testing team, no BA's and developers must give 24 tech support to all of the code was sold as positive. Full stack developer apparently still means: we are too cheap to hire supporting roles so developers do everything.
Interview questions [1]
Question 1
Tell me a time you had a difficult time with another employee. Tell me a time you saw a role that needed to be filled and filled it. Why do you want to leave your current job? Case interview was simple and partly irrelevant. Do you need to ask a software developer what the business needs are met by acquiring another company? I don't think so. The coding part was simple and I got to do it on paper instead of a white board, but I don't think it demonstrated any sort of ability or lack thereof.
Surprisingly manageable — the interview felt more like a conversation than an interrogation. It began with a sequence of coding questions, including one on merging overlapping intervals. The real challenge came during system design, where I had to outline a URL shortener service that could scale impressively. Interestingly, I had just looked at a similar architecture on PracHub, which helped me articulate my thoughts clearly. The technical questions wrapped up with validating a binary search tree, and I ended with a positive vibe. I received an offer, but ultimately chose to decline it.
Interview questions [3]
Question 1
Merge overlapping intervals from a list of time ranges
Interviewed for an engineer position, the interview was a joke. Asked basic OOP question with a few follow ups - no system design portion. Interviewer was very laid back and chill, didn't take it to seriously.
Was not too difficult. three total interviews all on the same day back to back. technical one, behavioral one and a case which was more of just a debugging question