There was a screening code test on HackerRank, which failed to work multiple times, but I was progressed to the next stage anyway. So I can't say much about that; from what I could see, it looked like basic array manipulation.
Phone interview with the hiring manager, with general questions about experience and more detail about the job and job fit.
Then a face-to-face interview, which contained four parts:
All of which were in a somewhat relaxed atmosphere.
Feedback I received was interesting: apparently, they felt I was somewhat "bluffing," which was slightly offensive. I'm not sure how this was founded, as any question they asked to dig deeper was answered. They were critical of having to probe for more information, despite my following the suggested STAR method and not knowing what was on their structured answer sheet.
I felt like HackerRank failing to work worked against me, as the exposure they had to my development skills was limited to one hour of paired programming. I had offered up code from some published apps I had written, which would have shown hundreds/thousands of hours of my coding effort instead, but they didn't really seem interested, which I found weird.
In the end, there was a stronger candidate, so although I had "passed the interviews," the position was taken.
Everyone I met through the day was super nice and welcoming, making it a somewhat enjoyable day. It's just a shame they felt like I was bluffing.
Why do you want to work at Capital One?
The following metrics were computed from 3 interview experiences for the Capital One Software Engineer role in Nottingham, United Kingdom.
Capital One's interview process for their Software Engineer roles in Nottingham, the United Kingdom is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Capital One's Software Engineer interview process in Nottingham, United Kingdom.