Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Capital One en ago 2022
Entrevista
Went pretty smooth overall.
Technical interview: messed it up although it was not difficult. LC Easy/Medium.
System design: was asked to design an online banking system.
Behavioral: this is easy based on STAR approach.
Case: two sections, one analytical and the other is to find issues in the given code. Messed the 2nd section.
Preguntas de entrevista [1]
Pregunta 1
Given a string, check there are exactly 3 question marks b/w the digits and the 2 digits always add up to to 10 else return false.
It was a standard interview process. Your technical interview which included multiple different rounds all in one day. It included a coding question, systems design question, business use case question, behavioral interview.
Acudí a una entrevista en Capital One (Toronto, ON)
Entrevista
30 min quick call
Technical round of leetcode type questions
Unfortunately ended there as i didn't pass the that round.
Presumably it was going to be system design after this online leetcode question and then onsite.
Preguntas de entrevista [1]
Pregunta 1
Standard Leetcode questions, asked a 1 easy, 2 medium/hard questions
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Capital One (Toronto, ON) en dic 2024
Entrevista
Applied on their career site and was reached out to by the recruiter over email and phone. First round was a 70-minute proctored CodeSignal assessment.
The last round consisted of two parts, spread across two days – the first part was a 1-hour behavioral round with a tech lead, and the second part was a 1.5-hour pair programming session with two staff-level engineers and a shadow interviewer.
Preguntas de entrevista [3]
Pregunta 1
CodeSignal Assessment consisted of two easy, one medium and one hard coding questions. Expectation was to be able to solve at least two completely, with a partial third for extra points.
The 1.5-hour pair programming question was not like your typical LeetCode question. It simulated a type of problem that you would solve at a bank/credit card company. The focus was algorithmic implementation; not so much OOP concepts.