I applied through a recruiter. The process took 4 weeks. I interviewed at Capital One (San Francisco, CA) in May 2016
Interview
1) 2 hr hackerrank challenge.
2) 1 hr technical phone interview.
3) 1 hr coding session.
4) 4 onsite video calls. 2 f2f. This involves what would you do in a situation sort of questions.
Dealing with a manipulative recruiter was the major part who bravely and cunningly tried to confuse me with my salary expectation i expressed in an earlier call by asking to re-confirm it, like "What did u said last time, its (originally stated by me - 10k), right?". When i was rejected by someone in 4th round because my approach towards "what do i do in a situation like" did not matched with what he would do in same situation, this recruiter did not even cared to inform me even after i followed it up via 2 emails. Dont waste your time if you are genuine enough not to spice up, glorify situational, attitude related, behavioral questions and try to misguide someone about yourself.
I applied through an employee referral. The process took 1+ week. I interviewed at Capital One (Chicago, IL) in Jun 2016
Interview
It took around 2 weeks for 3 round of interview online test, telephone interview and onsite interview. I cleared both online test ( on hacker rank site ) and then 30 minutes telephone interview. At onsite there were 4 interviews of 45 minutes, 2 technical and 2 behavioural interviews. It was nice experience with the interviewers at onsite.
Interview questions [1]
Question 1
Difference between rest and soap.
Design patterns
Rest api code to read, update and delete employee data.
Oops concepts
I applied in-person. The process took 2 weeks. I interviewed at Capital One (London, England) in Jun 2016
Interview
The interview process had a telephone phase, followed by a code assignment on HackerRank and the last phase that was a full day of interviews.
The HackerRank challenge was deplorably unsuited for the role offered. I'm told they are trying to improve though. It was of average complexity, consisted of 3 increasingly more difficult tasks and lasted 90 minutes.
The face to face interview was composed of a pair programming challenge, a behavioural interview, CV-based questioning and an architectural interview (whiteboarding).
The pair programming challenge was quite easy. The CV-based questioning was intense in that it was an honest effort to find the edge of my knowledge based on the experience stated in the resume.
The architecture part is easy to fail if the candidate doesn't have enough experience in conceptualizing a system.
What got me burned was the behavioural part. Google for it to see what I mean. It's all sorts of situational questions which will either leave you scrambling to remember such a situation in your experience or thinking of whether or not to make something up. I found that part stressful.
However the most disturbing part for me was what the recruiter told me afterwards when delivering the "it was a tough decision but we have to say no" speech. It was a hypocrite talk with phrases like "everyone who met you liked you very much, but we don't think you'll fit in the team", "we don't think you're right for the position now but we definitely want to keep you on file for the future", "we thank you for the time you took to interview with us and to make it not be a waste of time for you we'll shortly send you detailed feedback about the interview", "we don't think we'll be able to quench your thirst for learning new tech" even though on the phone they stated that there are many interesting avenues and technologies pursued at the moment in my engineering field.
A few weeks later and after a few emails that never got answered I realize that their promise of detailed feedback was empty words.