I received a call from a recruiter and immediately scheduled the tech screen. It consisted of 4 CoderPad questions in 70 minutes: 2 easy, 1 medium, and 1 hard.
When I passed, we scheduled the "Power Day." In the meantime, I spoke with a Tech Ambassador about company culture.
A few days prior to Power Day, the recruiter sent me very detailed instructions about what to expect, including what to study and how to prepare; everything but the questions themselves. A day prior, I received the schedule, though I didn't know which type of tech interview to expect for each hour.
The 4.5-hour (with a half-hour break) Power Day was remote but relatively grueling for me.
I found the coding and architecture questions to be relatively straightforward, even fun. The last two got harder. The final question was not explained well and had typos in the code that were not the bugs being sought.
I have to say, the recruitment process was all but perfect. The recruiter went well out of his way to keep me as informed as possible, even apologizing for not having an answer less than a day after Power Day ended. He also called me with the rejection.
If every recruiter were as good as he is, the tech world would be a better place.
Solve some basic, industry-appropriate test cases in code.
Design the architecture for requests real-world clients might make, on a whiteboard.
Typical "tell me about a time when..." behavioral questions.
Take this business case, complete some calculations, and fix some bugs.
The following metrics were computed from 201 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.