J'ai postulé via un recruteur. Le processus a pris 2 jours. J'ai passé un entretien chez Cisco (Santa Clara, CA) en mars 2008
Entretien
Questions weren't too hard, all solvable with given time. People were friendly. Study algorithms, C/C++ coding, and math proofs. Study a lot of sample interviews online, especially acetheinterview.com and careercup.com. These sites have user inputted real interview questions that can help you. Also study brain teasers.
J'ai postulé via la recommandation d'un employé. Le processus a pris 1 jour. J'ai passé un entretien chez Cisco (Bengaluru)
Entretien
I applied for the position and successfully attended the screening and coding round. The interview mainly focused on C programming and networking concepts, including IP subnetting, bitwise operations, and implementing logic to verify if an IP belongs to a subnet. There were also questions on TCP/UDP and debugging concepts. After the interview, I followed up with the recruiter, who shared that based on the feedback, my profile will not proceed further.
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Cisco (Tel Aviv-Yafo) en déc. 2025
Entretien
After applying on site I was reached by a recruiter which asked a few role specific questions and scheduled an technical interview with the recruiting manager.
First interview:
Introduction, tell me about yourself etc and the main question was "Talk about a system that you worked on end to end".
Second Interview:
System design interview. Role specific system, nothing special just a bit tricky. (not design youtube or twitter or anything like that).
Questions d'entretien [1]
Question 1
Talk about a system that you worked on end to end.
J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Cisco (Bengaluru) en oct. 2025
Entretien
I was reached out by the recruiter, and the interview was scheduled for the next week. Enough time was given to me for the preparation.
Total of 5 rounds were planned in advanced, and I was told I will proceed to the next rounds if I clear the previous rounds. (Eliminations)
First Round: General discussion on what I have worked on. No surprises.
Second Round: A practical coding questions, mix of low level and high level system design. Interviewer gave clear instructions about what is expected in each task. This round went smoothly from my point of view.
Third Round: This was the round where things went upside down. Interviewer joined 30 minutes late, and seemed uninterested. The interviewer did not follow the basic etiquettes. He spend 5-10 minutes reading my resume on spot, with no communication and awkward silence.
Next 10-15 minutes followed on general question about what I had worked on in the past.
Then I was given a puzzle question, with certain constraints (No code required, verbal solution was asked). I could not solve it optimally. Even the interviewer was confused and he couldn't solve it with the constraints given.
(After the interview, I googled the solution for the same problem, and came to know the constraints were a little different).
Got a call from the recruiter after 30 minutes that I was not selected, and need not join for the next rounds.
TLDR:
Difficulty wise I would say the interview was of medium difficulty.
DSA - Leetcode easy and easy-medium.
System Design - Practical questions, no surprises.
Low Level Design - Practical questions which most developers would have already worked on.
But a lot depends on the interviewer.
Questions d'entretien [1]
Question 1
System Design: Design a distributed message queue.
Low Level Design: Design a rate limiter.
Coding: From the two streams of very large numbers (not able to fit in int64 or float64), calculate the running sum and send the response over the third stream.
Puzzle: You have a set of 8 balls. 7 are of the same weight, and 1 is of different weight (may be lighter, may be heavier). Find the odd weight ball in minimum number of tries using a weighing scale.