J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Capital One en avr. 2019
Entretien
The hiring process was pretty straight forward. I applied online through a link we all got in college for the TDP program and then a few days later, a recruiter talked to me to schedule an on-site interview. So this was my first interview (in life) and it had 3 parts- Technical, behavioral and case. I was asked an OOP question (pretty straightforward) and a binary tree pruning problem in my technical round. I freaked out but the interviewer still helped me out. The behavioral is pretty standard and the case isn’t too bad either. Overall I didn’t get an offer but I am planning on applying again in 6 months, great interview experience.
Questions d'entretien [1]
Question 1
Binary tree pruning
Design a credit card system (OOP)
Explain sth technical to a nontechnical person.
Tel me about a project you’re most proud of.
J'ai passé un entretien chez Capital One (McLean, VA)
Entretien
Interviewed for an engineer position, the interview was a joke. Asked basic OOP question with a few follow ups - no system design portion. Interviewer was very laid back and chill, didn't take it to seriously.
Was not too difficult. three total interviews all on the same day back to back. technical one, behavioral one and a case which was more of just a debugging question
Expecting a challenging experience, I found the interview at Capital One to be intense, particularly during the system design section. The question on designing a rate limiter with a token bucket algorithm took me by surprise; mid-way through the problem, I realized it was very similar to a drill I’d practiced on prachub.com just days earlier. The technical rounds included several DSA questions, and the interviewers were thorough but supportive. Ultimately, I received an offer and happily accepted, feeling well-prepared despite the pressure.
Questions d'entretien [1]
Question 1
Design a rate limiter using a token bucket algorithm and discuss how it would handle bursty traffic and distributed deployments.