Solicité el puesto a través de la recomendación de un empleado. El proceso duró 2 meses. Acudí a una entrevista en Capital One (Ithaca, NY) en oct 2016
Entrevista
3 rounds, One round was a case study, the second round was a personal interview, the last round was a technical interview. The first round was based on how to deal with the allocation of pricing on marginal phone calls to use in comparison to a system they already were using. The Personal interview was along the lines of your standard why do you want to work here. The tech interview were basic java recursion questions along with brain teasers from the coding interview book.
Preguntas de entrevista [1]
Pregunta 1
How to calculate marginal cost of using a phone service.
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.
Preguntas de entrevista [1]
Pregunta 1
Design a rate limiter using a token bucket algorithm and discuss how it would handle bursty traffic and distributed deployments.
Recruiter screening to begin with. Then, technical discussion about java, spring boot, design pattern, small coding tasks and followed by design assessment for distributed systems. Finally, managerial round for the team fit