I applied for an Android developer position and overall found the interview to be one of the best I’ve gone through.
I was contacted by a recruiter on LinkedIn. He asked me to submit my resume, and a few days later, I participated in a phone screen with him. He sent my resume to the hiring manager, and the next day, I was told they wanted to set up a technical interview.
I had the technical interview a week later. Their technical interview was a combination of rounds 2 (coding challenge) and 3 (technical conversation). I was told I did well in their technical interview, and an in-person interview was set up two weeks later.
The in-person interview was in between easy and medium difficulty and had four rounds:
The pair-programming was a bit challenging because you had to learn their software on the fly, but the interviewer I worked with was very informative, and I was able to produce the desired result. I was asked a lot of questions during the Q&A session.
I left the interview confident and was surprised to hear they were going to pass on my candidacy. They provided feedback for why they were passing, and I appreciate that they left feedback.
The technical interview involved writing code in Java to determine if a word was a palindrome and then if parentheses were balanced.
The pair-programming question focused on taking provided data, displaying it on the emulator, and then filtering that data.
The following metrics were computed from 179 interview experiences for the Capital One Senior Software Engineer role in United States.
Capital One's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Capital One's Senior Software Engineer interview process in United States.