I applied through a recruiter. I interviewed at Capital One
Interview
Recruiter reached out after I interviewed. We scheduled a call and I received Coder Signal. I think it was proctored, but I don't remember clearly. 90 mins and 4 qs, 2 of which were regular algos. Another one was a very long system design question. I think it was to implement a cloud system storage. Recruiter forgot our scheduled call afterwards and I didn't bother reminding her.
Other Software Engineer Interview Reviews for Capital One
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.
Interview questions [1]
Question 1
Design a rate limiter using a token bucket algorithm and discuss how it would handle bursty traffic and distributed deployments.