The first step was a coding challenge conducted on CodeSignal. I received the challenge fairly quickly after applying.
I completed three-quarters of the problems correctly and submitted some code for the fourth problem, which I did not finish.
I then moved on to the next phase, which consisted of a set of three interviews, each one hour long and with separate goals.
One interview was purely behavioral, asking about several items on my resume.
Another was purely technical, involving narrating my thought process while solving a coding challenge on linked lists and some simple object-oriented problems. The linked list coding challenge was more difficult than I expected; I spent 45 minutes on the problem.
The last interview was a technical case study where I was asked generic product management-type questions about how to make a chatbot service more impactful. This case interview also included some simple coding and an assessment of how to improve it.
The interviewers were all very professional, personable, and welcoming, as was my recruiter. I had a great experience overall.
A few days after my last interview, I received an offer.
For reference, I am a white male UT Computer Engineering student with a fairly strong resume and a previous tech internship at P&G.
Behavioral interview questions were fairly generic. Technical interview and coding challenge questions were comparable to the easier LeetCode Mediums or easys. I would recommend practicing talking through your reasoning out loud on a coding challenge to prepare for the technical interview.
The following metrics were computed from 7 interview experiences for the Capital One SWE Intern role in McLean, Virginia.
Capital One's interview process for their SWE Intern roles in McLean, Virginia is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Capital One's SWE Intern interview process in McLean, Virginia.