El proceso tomó 3 semanas. Acudí a una entrevista en Capital One
Entrevista
Do not interview here. It is a waste of time. Process was unorganized as well. Interviewers had given me the same systems design question when one was supposed to be coding - took them a while to sort it out. Systems design question guy had huge Indian accent and when I asked to clarify/repeat things he felt hugely offended. I did really well on all interviews (asked for feedback from interviewers which were positive) except that one because he felt offended. When asked for feedback from hr they were not able to give feedback (even though the individual interviewers gave me positive feedback) which leads me to believe the one guy must've persuaded them I was incapable otherwise. The rest of the other interviewers were professional.
13
Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer en Capital One
Me postulé en línea. Acudí a una entrevista en Capital One
Entrevista
Scheduled a call with recruiter. Recruiter didnt show up for the screening call and cancelled it 5 mins after the scheduled time. Dropped a follow up email and got no response. After a week, I got an email from the recruiter stating I am selected for the next round i.e Assessment. Sent me an email with the assessment description but no link. When I sent a follow up email asking for the link, I got ghosted again. It was a bad experience. Felt like she is toying with me. Why ghost an applicant repetitively? Unprofessional recruiter who doesn't respect an applicant's time or efforts!
4 rounds of interview including coding , design , case study, behavioral after clearing the code signal assesment. Coding was medium hard of 2 questions each. case study and system design was difficult.
This took a bit longer than expected, stretching over several weeks. The technical rounds were intense, featuring an LRU cache implementation and a problem on detecting duplicate transactions within a 60-second window. I was nervous at first, but it clicked for me when I realized I had practiced a similar approach on PracHub just days before. Unfortunately, I didn’t receive an offer in the end, but the experience was a solid learning opportunity. The behavioral questions felt straightforward, so I wish I had made a stronger impression in the technical segments.
Preguntas de entrevista [2]
Pregunta 1
Implement an LRU cache with get and put operating in O(1)