I applied through college or university. The process took 2 weeks. I interviewed at Capital One in Sep 2016
Interview
Did a HackerRank coding challenge followed by an onsite interview. The on site was a "technical" interview followed by a fit/behavioural interview. The "technical" is in quotes because they just had a senior software engineer ask me to go through my HackerRank challenge code followed by ask me a question on every single bullet point on my resume. For example, on my resume I mentioned that I'd worked with SQL 2 years prior, and she asked me to write a relatively detailed SQL query. Then she asked me to reverse a string. Literally one line into the code she interrupted me and asked me another question regarding the difference between a StringBuilder and a StringBuffer. At the time of the interview, I did not know the difference, so I told her I've only ever worked with StringBuilders. After the interview, I googled it and it turns out they do the exact same thing, except one is thread safe. I asked if she wanted me to continue with the string reversal code and she said no, to just leave it. Then she went on to ask me what series of Git commands I would use to accomplish a task. I don't remember exactly what the task was, but when I said I'd use rebase command, she was extremely confused as to what it was. I had to explain to her the difference between the rebase and merge commands. All in all this was a very unorganized interview.
Flew me out to Plano, great experience. One Case, behavior, job fit (i.e. cracking the coding interview).
Pretty great interview process, highly recommend following their interview prep guideline pdf they send out.
I applied through college or university. The process took 1 week. I interviewed at Capital One (Baltimore, MD) in Oct 2016
Interview
Applied through university and did an on-campus interview consisting of 3 45-minute interviews. 1 technical, 1 case, and 1 behavioral. They all went pretty smoothly and were very nice and happy to answer any questions I had. Technical interview were textbook data structures questions involving strings and linked lists, really basic ones that you'd find in CTCI. Also had some OOP design. The case interview was a little rocky, I understood what the interviewer was saying and I could see the solution but had a slightly hard time getting the interviewer on the same page with me, but eventually got there. For the behavioral, really prepare some anecdotes in the SAR format (Situation, action, result). The interviewer literally records each part separately and explicitly told me to format my answers like that.
Interview questions [1]
Question 1
Talk about a time you explained something technical to someone non-technical.