I applied online for a position in Seattle and received a response from a recruiter stating that a hiring manager would be calling for a 30-minute technical interview related to my professional experience. I had been following the DevExchange engineering blog by Capital One developers and was excited to discuss some of the challenging problems I had solved within their domain. I researched the hiring manager's profile and noted his extensive experience in technology, including a prior role as a tech lead at a major software company before joining Capital One. Naturally, I had high expectations for the depth of problems we would discuss.
Here's how the call went:
"Hello, I have X number of questions that I'm just going to read," he stated, proceeding to do so without any introductions or information about the opportunity or team. The questions were very basic, covering topics like class vs. interface, JavaScript, AWS, and SQL. I believe I answered about 90% of them correctly and attempted to explain why I might not recall certain answers offhand. It seemed he was expecting 100% precise answers.
I had hoped he would at least exhibit professional courtesy by leaving time for me to ask questions about the product, company, technology, etc. However, he simply said goodbye and hung up. I'm unsure how he became a manager, and perhaps I'm missing something, but I am glad I was not selected for the next rounds, which would have been a waste of both our time.
Very basic object-oriented programming, SQL, and JavaScript.
The following metrics were computed from 1 interview experience for the Capital One Senior Software Engineer role in Seattle, Washington.
Capital One's interview process for their Senior Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Capital One's Senior Software Engineer interview process in Seattle, Washington.