J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Capital One (Mc Arthur, ID) en sept. 2020
Entretien
Had the 3 part interview as described by other candidates. However, mine was conducted over zoom due to coronavirus. I got invited to this by applying very early online.
Instead of white boarding problems, coding questions were on CodePair (a HackerRank environment). They did not give a set of test cases though. Instead I manually tested with a few examples and explained my solution’s runtimes. I struggled a bit but was always talking through my attempts.
I received an offer a few days later. I greatly enjoyed everyone I interviewed with and the offer details were excellent. Overall, could not have asked for a better process.
Questions d'entretien [1]
Question 1
Study common data structures, strings, linked lists, trees, stacks, queues, hash
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.