Tip 1 : Make sure to get familiar with all the parent-problems from the common DSA topics (GFG can help with that)
Tip 2 : Always ensure that your CV/Resume has some points/mentions in projects & experience sections which can provoke discussions about your problem-solving and coding skills, which shine light on your strong-suits in front of the interviewer.
Tip 3 : If the interview is virtual, MAKE SURE you have great lighting & setup behind you, which gives a professional vibe. If possible, try including any trophies/medals in the background, that you've won/have an interesting/inspiring story behind them.
Tip 4 : Try to connect with the interviewer, and don't be afraid to ask questions. That shows you're attentive, and are curious.
Tip 1 : If possible, try to use templates that are unique/memorable in some form, but still within the scope of professionalism. Don't go TOO flashy/colorful/creative, as that might come-off as naive.
Tip 2 : Have some interesting stories relevant to your projects/experiences ready with you, so that if an opportunity presents itself, you can tell the interviewers about it. This just might make you stand-out from the rest, as an experienced/responsible candidate.
It was a standard MCQ + coding test, which seemed geared mostly towards the CSE fundamentals, with special focus on networking, given cisco's background. It was also a bit more time-constrained than the usual/other tests I attended for other companies during the same time. The test happened during the evening, and was pretty intense due to the time-constraint.
This was a coding-cum-technical round, where a major part of the discussion revolved around my previous experiences, and the projects that I had listed in my resume. It was filled with technical cross-questioning around the points that I mentioned regarding my work, and also a lot of discussion regarding the technologies involved in the same. Towards the end, I was also asked to code solutions for some of the problems that interviewers asked, and also some testing around system-design principles, based on a real-world scenario. The interview happened around 9AM, and went on for around 75 minutes.



If the string is “bca”, then its permutations in lexicographically increasing order are { “abc”, “acb”, “bac”, “bca”, “cab”, “cba” }.
Given string contains unique characters.
This round was with the hiring team's manager. It happened in afternoon. The initial discussion was mostly around what cisco is all about, what its trying to do these days, and how the team hiring right now fits into that. I also used this chance to clarify a few doubts I had about the level of exposure and the tech stacks I could expect to encounter. After that, the discussion moved towards the networking basics, with a helthy amount spent around the TCP/IP suite and the IP addressing fundamentals. Finally the round concluded with a logic puzzle.
List out the various layers of the OSI model, and how are they different from TCP/IP suite layers
A pretty theoretical question, which I was able to promptly explain.
If you have two containers of 5 and 3 liters each, how can you measure a quantity of exactly 4 liters without the help of any other container, in least possible steps?
I solved this problem using empirical observations. I explained that we can start with a full 5 liter jug, and using this fill the 3 liter jug completely. This leaves a water quantity of 2 liters in the 5 liter jug. Then, we empty out the 3 liter jug, and fill it with the 2 liters present in the other jug. So, the 3 liter container now has exactly 2 liters of water. In other words, it will be completely filled by 1 liter of extra water.
So, we fill the 5 liter jug again, and pour water into the other jug, until it is completely filled. This removes 1 liter from 5 liter jug, leaving us with exactly 4 liters of water.
This was a very quick round with the HR lead of the hiring team at cisco. This interview happened after just 15 minutes of the manager round. In it, he asked me about why I'm interested to join cisco, do I know who the competitors of cisco are, etc. It was not a long round, and we wrapped-up the discussion with a salary-structure breakdown, that a candidate can expect to receive, if selected.
Who are the competitors of cisco
I didn't exactly know who to name, but from the general nature of cisco's offerings and their name popping-up in discussions about 5G, I thought Huawei could be a match. I was correct, and the interviewer also told me about the other direct competitors like juniper, Palo Alto Networks, Barracuda, etc.
Why should we hire you?
This is a pretty common question in HR rounds, and so I had key-points ready around what to highlight. I let him know about my experience so far, by virtue of various internships and start-up exposure. I also explained to him the scale and variety of the projects I had listed on my CV, and how they relate to the job-role they are hiring for. Lastly, I highlighted, by means of a few experiences/stories, my work-ethic and dedication to the task at hand.

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
To make an AI less repetitive in a long paragraph, you should increase: