Le processus a pris 2 semaines. J'ai passé un entretien chez Capital One (Fairfax, VA) en mars 2021
Entretien
Online Coding Test then four round powerday
Case Study and Debugging
Architecture and System Design
Behavioral
LeetCode Algorithms
Felt pretty well about everything apart from the algorithm problems as I didn’t run any code in the hankerrank coding pair. It also couldn’t use my preference of language as it wasn’t supported. It could have easily been solved with regex but you can’t look anything up. Also a very bad interviewer for that round, they were silent the entire time and not interactive. Didn’t seem like they wanted to be there. You have to be lucky on the interviewers.
It’s also very exhausting. Please change it to be split over days. Not everyone can take the time out of work for 4-5 hours of straight interviews
Questions d'entretien [6]
Question 1
Design an application that handles smart meter readings for an apartment building, with the users being tenants and managers
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.