Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en Capital One
Sin oferta
Experiencia positiva
Entrevista difícil
Solicitud
Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Capital One (Washington, DC) en jun 2025
Entrevista
There was an initial recruiter call, an OA, then the onsite which covered coding, behavioral, system design, and a case study. The onsite is called the power day. Overall a good process.
The first stage is the recruiter call which was really impersonal and is just someone reading from a list of basically 5 questions who isn't interested in hearing about your experience or trying to explain the role or company at all. They probably don't even really know what you do.
The second stage is a virtual algorithm coding test with screen and video recording which I'm not sure if is better or worse than coding for an interviewer. You are to complete 4 leetcode style questions in 70 min. I would say 1 easy, 1 easy/medium, 1 medium, 1 hard. The questions were worded way more confusing than what you'd see on leetcode and I spent a lot of time just trying to figure out what they were saying. I solved 2 out of 4 but brute forced. The competition for these roles must be high because this is an interview I'd expect at a big tech company, difficultywise
Either way the interview process was overall a negative, dystopian experience and will likely just be replaced by AI soon. If you are very well honed on leetcode and want to feel like a cog even while interviewing, this is your company.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Capital One en may 2024
Entrevista
Initial CodeSignal assessment, then a "Power Day" which consisted of 4 1hr interviews:
- general coding interview
- domain (ios) specific interview
- behavioral (STAR method) interview
- case interview
You'll get a 1 hour break in the middle of the day, so the entire power day is about 5 hours.
The power day interview was a bit easier than expected, especially for a senior level position. They claim that for legal reasons, they cannot give you feedback on your interviews.
Preguntas de entrevista [1]
Pregunta 1
- For the general coding assessment, they asked an easy/medium level data structures and algorithms question
- For the domain interview, it was questions about how I would design an ios app given certain requirements. I remember they asked me about what kind of storage solutions I would use for an iOS application give certain criteria. After explaining my answers, they would then add different requirements and I would have to update my answers based on that.
- For the behavioral interview, they asked questions like "tell me about a time you disagreed with a coworker". They specifically tell you to use the STAR method. This interview only lasted about 15 minutes
- For the case interview, they showed me some code, asked me to explain what it was doing, and asked me to change the code to do some additional things as required. This one was probably the most difficult, although from their description of it in the interview prep, it wasn't what I expected. They said you would be given a business problem and have to describe your solution for it. This interview was nothing like that at all. It was just another coding interview.