I applied through college or university. I interviewed at Capital One
Interview
Underwhelming and not challenging, but their are things you just have to be ready for. What I just couldn't put together and probably made me look incompetent was just knowing to say API instead of server or network to the question of how services talk to eachother, so it is just little things like that that, like in most interviews, you just have to be ready and know.
Interview questions [1]
Question 1
How would you refactor this code? And it was literally just consolidating if statements into while loops and moving them around.
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.