Summary
I recently interviewed with Cisco for an Analyst role and was impressed by their unbiased evaluation process. Although I received an offer, I ultimately decided to pursue another opportunity at Apple.
Full Experience
I recently had the opportunity to interview with Cisco for the Analyst role. What made this entire process stand out was how Cisco prioritized fairness and unbiased evaluation right from the beginning.
Before I could even submit my resume, Cisco asked all candidates to remove any personal identifiers, such as name, contact details, CGPA, college name, or even references to specific clubs or events in order to eliminate any form of conscious or unconscious bias. It was the first time I had come across such a transparent and structured approach, and it already reflected a lot about their culture. The entire process consisted of four stages (all eliminatory): Group Discussion (GD), Technical Interview, Managerial Interview, and HR/ETR Round, each testing different aspects, from communication and analytical thinking to cultural fit and problem-solving mindset.
Round 1: Group Discussion
Duration: ~90 seconds per participant
Focus Areas: Communication clarity, confidence, and structure of thought
This was the first screening stage, where around 75 candidates were divided into 6 groups of 12–13 members each. Every participant was given a random topic and had to speak for about 90 seconds. My topic was News Channel vs Newspaper.
I focused my speech on the importance of authenticity over medium, emphasizing that credibility of information matters more than the format it’s delivered in. I also discussed how rural vs urban access shapes our preference for digital or print media. The panel appreciated how I balanced both perspectives and kept my response structured and time-bound.
After this round, around 50 candidates were shortlisted for the next stage.
Round 2: Technical Round
Duration: ~55 minutes
Focus Areas: Analytical thinking, Technical Problem-Solving, and Core Computer Science Fundamentals
The interview began with a quick introduction, followed by a discussion on my project. The interviewer wanted to understand my contribution, technical design decisions, and how I handled challenges.
I explained how I developed a full-stack web application using Node.js, Express, and MongoDB, emphasizing route structuring, query optimization, and overall scalability. The interviewer asked follow-up questions about authentication strategies, handling concurrent requests, and optimizing database performance through indexing.
In another backend-focused project, I discussed implementing a microservices architecture, where the conversation centered on my decision to decouple modules, the inter-service communication methods used, and the fault tolerance mechanisms designed to enhance reliability and resilience.
Then we switched to problem-solving. I was asked two analytical coding questions:
- Find the smallest subarray with sum greater than X (I implemented a sliding window approach and derived an optimal solution).
- Minimum number of platforms required for trains (I started with a brute-force solution, then moved toward an optimized two-pointer approach).
About 19 candidates advanced to the next round.
Round 3: Managerial Round
Duration: ~45 minutes
Focus Areas: Decision-making, communication, and handling ambiguity
This round was conducted by a senior manager who seemed very focused on understanding how I think and operate within a team. She began by asking about my motivations, how I balance multiple responsibilities, and what kind of work excites me the most.
Then came situational questions like:
- Tell me about a time when things didn’t go as planned in a project.
- How do you handle it when you don’t know something but are expected to deliver?
- What’s the biggest challenge you’ve faced while leading a team?
This round ended with a short but interesting discussion about data-backed decision-making. She wanted to know how I’d use data to identify trends or drive improvements in a business process. I explained how, in one of my projects, I explored feature correlations and interpreted them beyond just the numbers, connecting them to real-world behaviour.
After this, 8 candidates were selected for the final round.
Round 4: HR/ETR Round
Duration: ~30 minutes
Focus Areas: Fitment, logistics, and expectations
This was the most conversational round. The HR began with her introduction, followed by:
- Tell me about yourself.
- What is Cisco known for?
- Who are Cisco’s main competitors?
- What are your future aspirations?
- Why do you want to take up a role immediately after graduation?
Then she discussed compensation details, internship duration (January–July), work location, and asked if my college would provide an NOC (No Objection Certificate). I told her that I was open to relocation and that my college supported long-term internships for final-year students.
We ended with me asking, What does Cisco expect from me as an intern?, to which she replied, Just come with an open mind and willingness to learn. It was a calm, engaging end to what had been an extremely thorough process.
Verdict: Selected✅ (but went with Apple)
I was thrilled to learn I’d been selected, but I ultimately decided to pursue another opportunity at Apple, which I’ve discussed in my previous post.
Still, Cisco’s process remains one of the most unique and thoughtfully designed experiences I’ve been through. Every interviewer genuinely tried to understand how I think, not just what I know, and that made it feel more like a professional dialogue than a test.
Interview Questions (12)
Participants were given a random topic and had to speak for about 90 seconds. My topic was 'News Channel vs Newspaper'. I focused my speech on the importance of authenticity over medium, emphasizing that credibility of information matters more than the format it’s delivered in. I also discussed how rural vs urban access shapes our preference for digital or print media.
Find the smallest subarray with sum greater than X.
Determine the minimum number of platforms required for trains.
Tell me about a time when things didn’t go as planned in a project.
How do you handle it when you don’t know something but are expected to deliver?
What’s the biggest challenge you’ve faced while leading a team?
How would you use data to identify trends or drive improvements in a business process?
Tell me about yourself.
What is Cisco known for?
Who are Cisco’s main competitors?
What are your future aspirations?
Why do you want to take up a role immediately after graduation?
Preparation Tips
Preparation Tips
- Be confident and concise during the GD, clarity matters more than complexity
- Brush up on problem-solving patterns (Sliding Window, Two-Pointer, Greedy, Sorting)
- Review CN, DBMS, SQL joins, and API fundamentals
- Understand your projects inside out, architecture, trade-offs, and real challenges
- Be clear and structured in communication (Cisco values clarity over perfection)
The wait may test your patience, but it’s often the test that shapes your success.
Summary
I applied for a position at Cisco and underwent an Online Assessment followed by two technical rounds. Despite receiving positive feedback, I was ultimately ghosted by the recruiter.
Full Experience
YOE: 4.5
Applied via careers portal.
Got an OA with 5 questions:
2 Easy
2 Medium
1 Hard
Solved: 2 Easy, 1 Medium (partially), 1 Hard.
Got a call from recruiter:
Recruiter mentioned 2 technical rounds followed by a HM round based on performance. Both technical rounds were held on the same day.
Round 1 (1 hour):
- Next Greater Element to Right
- Group Anagrams
Wrapped up in ~40 mins with working code & testcases.
Round 2 (1 hour):
- Reverse Linked List II
Resume & past project discussion.
Again wrapped up in less than 40 mins.
Surprisingly, no system design in either round.
Got positive feedback for both rounds.
After this, recruiter said HM was busy due to year end, so they'll “take it slow” and contact me in 2 weeks. As expected, after 2 weeks: no updates, stopped replying and answering calls.
Interview Questions (3)
I was asked to find the next greater element to the right for each element in an array.
I was asked to group anagrams together from a given list of strings.
I was asked to reverse a linked list from position m to n.
Summary
I recently completed an interview process for an SDE position at Cisco. Despite positive feedback from the hiring manager and clearing initial technical rounds, I was ultimately not extended an offer as they opted for a candidate with more direct experience relevant to their tech stack.
Full Experience
I was shortlisted for an SDE position at Cisco. My interview journey began with a phone screen with the hiring manager, which was a deep dive into my resume. I elaborated on the products I'd worked on, their tech stacks, and discussed my familiarity with the job requirements, the team's culture, and the product itself.
Subsequently, I proceeded to the coding rounds. The first coding round started with a discussion about my resume and further deep-dives into my projects and the technologies I used. I was also asked some theoretical questions, including:
- What is the difference between SSH and TLS?
- Inner join vs Outer join in databases?
- Transactions and its uses in databases (where I explained ACID properties).
For the coding part, I was given a LeetCode medium difficulty question, which was Maximum Subarray.
I moved on to the second coding round, which focused more on Golang, given it was a Go development role. This round tested my knowledge of Go syntax, goroutines, unbuffered and buffered channels, mutexes, and waitgroups. Specifically, I was asked to write a Fibonacci program in Go using channels and goroutines. There were also a few more resume-based questions.
Finally, I had a managerial round where we discussed my projects, tech stack, daily requirements for the role, and expectations. Although the hiring manager provided positive feedback after this round, they ultimately decided to move forward with a more experienced candidate who had direct experience with their specific tech stack. Unfortunately, I was not offered the job.
Interview Questions (5)
I was asked to write a Fibonacci program in Go using channels and goroutines, demonstrating understanding of Go's concurrency primitives like unbuffered and buffered channels, mutexes, and waitgroups.
I was asked to explain the difference between SSH and TLS.
I was asked to explain the difference between Inner Join and Outer Join in databases.
I was asked about transactions and their uses in databases, which led to explaining ACID properties.
Summary
I went through a multi-stage interview process for a Cisco 2026 Summer Software Engineer Internship, which included an online assessment and three interview rounds. Despite successfully clearing all technical rounds and reaching the final HR interview, I ultimately did not receive an offer.
Full Experience
My Cisco Internship Interview Experience
I participated in the selection process for the 2026 Summer Internship at Cisco. The process began with an eligibility form distributed through our placement cell.
Initial Process & Online Assessment
The first step was an Online Assessment on September 3, 2024. It comprised around 40 MCQs focusing on CS fundamentals and a significant emphasis on networking concepts, given Cisco's core business. Following the MCQs, there were two coding questions: one was a DP-based problem, and the other a Graph BFS-based problem, both of medium-hard difficulty.
Role Deep Dive Session
On September 9, 2024, I attended a session that provided insights into the Software Engineer roles at Cisco, covering Application, Embedded, and Networking domains. Early-in-career employees shared their experiences with the company and the interview process.
Post-Assessment Results & Interview Selection
After the assessments, I received an update from the placement cell. Most candidates were rejected, but I was fortunate to be among the 6 selected from my campus for the next rounds.
Interview Process - Eliminatory Rounds via Webex
Round 1 (13th September 2024)
I was quite anxious and prepared early that morning by reviewing CS fundamentals, networking concepts, and my resume. The interviewer was friendly and we started with a deep dive into my resume, asking detailed questions about my projects. She also probed into CS fundamentals, Networks, and DBMS. For the coding question, I was given a problem related to Linked Lists, specifically requiring operations for deleting and reversing nodes. I solved it and clearly explained my approach, and the interviewer seemed satisfied. Towards the end, I asked questions about the role, location, stipend, and a typical day at Cisco. I was confident I would proceed, and soon received an email confirming my selection for Round 2.
Round 2 (Senior Engineer Panel)
Initially nervous, I gained confidence as the conversation progressed with the senior engineer. We discussed my favorite project (I chose one I was very confident explaining). I also answered technical questions related to that project. We then moved on to conceptual questions spanning OOPs, Networks, and DBMS. For the coding segment, I faced questions involving strings and modulo operations. I explained my approach, and the interviewer was satisfied without requiring me to code it out. There was also an aptitude-based puzzle, which I partially solved but managed to explain my reasoning. Finally, I answered some behavioral questions about teamwork and challenges. I felt confident after this round and was later informed of my selection for the final HR round.
Round 3 (HR Round)
This round was conducted by a senior HR personnel and lasted about 5 minutes. The questions were standard HR inquiries: "Where do you see yourself in 5 years?", "What do you know about Cisco?", and "What are your thoughts on the offered stipend and location?". There was also a question about my father's education, which was a bit unusual. I had prepared answers for most of these and responded confidently. I was overjoyed as I believed I had cleared the final round and was the only candidate from my university to reach this stage.
Post-Interview Outcome & Reflections
I eagerly waited for two weeks for the final offer but received no updates. Upon reaching out to HR, I was informed that I had not made it through. This was my first experience with rejection despite performing well. It was disappointing, but I took it as a valuable learning experience to better prepare for future opportunities.
Interview Questions (1)
During my first technical round, I was presented with a coding challenge focused on Linked Lists. The problem required me to implement operations for both deleting specific nodes and reversing the entire linked list efficiently. I had to demonstrate my understanding of linked list manipulations.
Preparation Tips
My preparation for Cisco focused heavily on strengthening my understanding of CS fundamentals, Networks, and DBMS. I also dedicated time to thoroughly review my resume and projects, ensuring I could discuss them in detail and answer any related technical questions. For coding rounds, I practiced articulating my approach clearly and concisely, which proved beneficial during the interviews.
Summary
I interviewed for a Software Engineer Summer Internship at Cisco, successfully navigating through multiple technical rounds focused on CS fundamentals, networking, DBMS, and coding, but ultimately received a rejection after the HR round.
Full Experience
My Cisco Internship Interview Experience
I went through the Cisco selection process for the 2026 Summer Internship. The initial process involved an online assessment with 40 MCQs on CS fundamentals and networking, along with two coding questions (a DP-based and a Graph BFS-based problem). After this, I was one of only 6 candidates selected from my campus for the next rounds.
Round 1
This round was conducted via Webex. I was anxious but prepared by revisiting CS fundamentals, networking concepts, and my resume. The interviewer delved deep into my projects and asked questions spanning CS fundamentals, Networks, and DBMS. For the coding question, I was given a problem related to Linked Lists: Deleting and Reversing. I solved it and clearly explained my approach, which the interviewer seemed satisfied with. I felt confident about moving to the next round, and indeed, I received an email confirming my selection for Round 2.
Round 2 (Senior Engineer Panel)
I started nervous but gained confidence as the conversation progressed. The interviewer asked about my favorite project, and I chose one I was confident explaining, along with technical questions related to it. Conceptual questions covered OOPs, Networks, and DBMS. For the coding question, it involved strings and modulo operations; I explained my approach, and the interviewer was satisfied without me needing to code it. I also faced an aptitude-based puzzle, which I solved partially, explaining my reasoning. Behavioral questions focused on teamwork and challenges. I felt confident again and was selected for the final HR round.
Round 3 (HR Round)
This was a short round conducted by a senior HR personnel, lasting about 5 minutes. The questions included, 'Where do you see yourself in 5 years?', 'What do you know about Cisco?', 'Tell me about your father’s education?', and 'What are your thoughts on the offered stipend and location?'. I had prepared answers and responded confidently. I was overjoyed as I cleared this round, becoming the only candidate from my university to make it this far.
Post-Interview Outcome
Despite clearing all rounds, I waited two weeks for the final offer without updates. Upon reaching out to HR, I was informed that I had not made it through. This was my first experience with rejection after performing well, but I took it as a valuable learning experience.
Interview Questions (5)
In the first technical round, I was given a coding problem related to Linked Lists. The interviewer asked me to implement operations for deleting nodes and reversing a Linked List.
In the HR round, I was asked, 'Where do you see yourself in 5 years?'
The HR interviewer asked, 'What do you know about Cisco?'
The HR interviewer asked, 'Tell me about your father’s education.'
The HR interviewer asked, 'What are your thoughts on the offered stipend and location?'
Preparation Tips
Key Takeaways and Preparation Tips
Based on my experience, I've gathered some crucial preparation tips:
- Preparation Tips:
- Focus heavily on CS fundamentals, Networks, and DBMS, especially for companies like Cisco.
- Be thorough with your resume and be ready to discuss all your projects in detail.
- Always be prepared to explain your approach clearly and concisely during coding rounds.
- Interview Strategy:
- Stay calm and composed throughout the interview.
- Engage actively with the interviewer and remember to ask thoughtful questions about the role, team, or company.
- Post-Interview:
- Understand that rejection is a part of the journey. It's important to learn and grow from every experience, whether positive or negative.
Summary
I underwent the Cisco selection process for a 2026 Summer Software Engineer Internship. The process included an online assessment with CS fundamentals, networking MCQs, and two coding problems. I then progressed through three interview rounds covering projects, CS fundamentals, DSA (specifically Linked List deletion/reversal), and behavioral questions. Despite successfully clearing all rounds, I ultimately received a rejection after a two-week wait for the final offer.
Full Experience
My journey for the Cisco 2026 Summer Internship began with an eligibility form through my placement cell. The first hurdle was an online assessment on September 3, 2024, which featured about 40 MCQs on CS fundamentals and networking, alongside two coding questions – one DP-based and another Graph BFS-based, both rated Medium-Hard.
After the assessment, there was a role deep dive session on September 9, 2024, providing insights into Software Engineer roles. Following this, I was among the only 6 candidates from my campus selected for the interview rounds, which were eliminatory and conducted via Webex.
Round 1 (September 13, 2024, 10:00 AM): I was quite anxious, so I spent the morning refreshing my CS fundamentals, networking concepts, and resume. The interviewer was friendly and we immediately dived deep into my resume, discussing my projects in detail. Questions also spanned across CS fundamentals, Networks, and DBMS. For the coding segment, I was given a problem related to Linked Lists, specifically involving deletion and reversal. I solved it and clearly explained my approach, which seemed to satisfy the interviewer. Towards the end, I asked about the role, location, stipend, and a typical day at Cisco. I felt confident about this round and soon received an email confirming my selection for Round 2.
Round 2 (Senior Engineer Panel): This round started with the interviewer's introduction. Though I was nervous initially, I gained confidence as we conversed. We discussed my favorite project – I made sure to pick one I was completely confident about. Technical questions related to my project explanation followed. We then covered conceptual questions on OOPs, Networks, and DBMS. For coding, I faced a problem involving strings and modulo operations. I explained my approach, and the interviewer was satisfied without me needing to code it out. There was also an aptitude-based puzzle, which I partially solved but could explain my reasoning. Finally, some behavioral questions focused on teamwork and challenges. I felt positive but remained nervous while awaiting the results. Eventually, I was informed that I was selected for the final round.
Round 3 (HR Round): This was a short round, lasting about 5 minutes, conducted by a senior HR personnel. The questions were straightforward: "Where do you see yourself in 5 years?", "What do you know about Cisco?", "Tell me about your father’s education," and "What are your thoughts on the offered stipend and location?" I had prepared my answers, so I responded confidently.
Post-Interview Outcome: I was overjoyed, believing I had cleared the final round, being the only candidate from my university to get this far. I eagerly waited for two weeks for the final offer, but received no updates. Upon reaching out to HR, I was informed that I had not made it through. This was my first experience with rejection despite performing well, and while disappointing, I took it as a valuable learning experience to prepare even better for future opportunities.
Interview Questions (5)
The problem involved operations on a Linked List, specifically deletion and reversal of elements.
The HR personnel asked, "Where do you see yourself in 5 years?"
The HR personnel asked, "What do you know about Cisco?"
The HR personnel asked, "Tell me about your father’s education."
The HR personnel asked, "What are your thoughts on the offered stipend and location?"
Preparation Tips
My preparation focused heavily on fundamental subjects like CS fundamentals, Networks, and DBMS, which I knew were crucial for a company like Cisco. I meticulously reviewed my resume and projects, ensuring I could articulate every detail and my approach to coding problems. For the behavioral and HR rounds, I prepared answers in advance to common questions, which helped me respond confidently.
Summary
I interviewed with Cisco for my first professional experience during my third year of engineering. Despite clearing multiple rigorous technical rounds and a managerial round, and ultimately making it to the HR round, I received a rejection email after a hopeful waiting period.
Full Experience
Online Assessment
In 2022, during my third year of engineering, Cisco visited our campus for a pooled drive. I participated in an Online Assessment where two problems were presented: one focused on bit manipulation, and the other centered around the application of Floyd-Warshall algorithms. Following this, 20-25 students from my batch, including myself, were shortlisted.
Round 1 - OOPS & DSA
My first interview call arrived on March 9, 2022. The initial round, lasting approximately 45 minutes, delved into OOPS, strings, and linked list problems. This round went smoothly for me, and I earned a ticket to the next phase, though more than 60% of my batchmates were rejected.
Round 2 - Managerial Round
The managerial round, a mix of good and not-so-good moments, proved to be a 50-50 experience. Fortunately, luck favored me, and I moved forward along with only one other batchmate. This round took around 30-35 minutes.
Round 3 - System Design, Networking & DSA Round
In the third round, I met the exceptional Ravi Kiran. I swiftly handled a binary search problem before the discussion shifted to networking concepts, including TCP/UDP, three-way handshaking, and the distinctions between routers and switches. Ravi then explored Netflix's design, where I candidly confessed my knowledge gap. Nevertheless, it became one of the best interviews I've ever faced, thanks to Ravi's guidance. Following this comprehensive 50-minute session, I was the sole candidate from my batch to secure an HR round call after a brief 2-3 hour wait.
Round 4 - HR Round
In the HR round with Shruthi N, she inquired about my personal strengths and weaknesses, followed by salary discussions and internship location preferences. This was a concise yet meaningful conversation lasting around 10 minutes.
The Outcome
Post HR round, optimism filled the air, and my family anticipated positive news. However, reality struck on March 21 with a rejection email. I felt a similar emotion to when India lost the World Cup on November 19.
Interview Questions (6)
A problem requiring the application of the Floyd-Warshall algorithm.
A problem that could be solved using binary search.
Discussion on networking concepts including TCP/UDP, three-way handshaking, and the distinctions between routers and switches.
Design a system similar to Netflix. I confessed my knowledge gap on this topic.
What are your personal strengths and weaknesses?
Discussion regarding salary expectations and internship location preferences.
Preparation Tips
My preparation for this and future interviews began during my third year of engineering when I started my LeetCode problem-solving journey.
Summary
I successfully interviewed for the Technical Consulting Engineer role at Cisco in Bengaluru in July 2023 and received an offer. The interview process spanned multiple rounds, including an online assessment, a PPT presentation, a technical interview focusing on computer networks and resume projects, a managerial round, and a final HR discussion.
Full Experience
I completed my Bachelor of Engineering in Computer Engineering and interviewed for Cisco's Technical Consulting Engineer role in Bengaluru in July 2023. This role is offered to new graduates through the annual Cisco Ideathon, which recruits for Intern+FTE positions. The compensation included a stipend of 98k per month during the internship and an estimated CTC of 17-25 LPA for the full-time role. All rounds were elimination rounds, except for the PPT submission.
Round 0 (Quiz Round)
This was an Online Assessment where I had to choose between "Advanced Software" and "Advanced Networks" for the final two questions. I opted for "Advanced Software," which included DSA-based questions. Performance in this round influenced the role offered, so preparation was crucial.
Round 1 (PPT Round)
I was given three problem statements and tasked with developing a solution, including the approach, research, and limitations. Simply submitting the PPT qualified me for the next round. However, it's important to be thoroughly prepared, as interviewers extensively cross-questioned for about 30 minutes on my solution.
Round 2 (Interview Round)
This was the most critical round, where many candidates were eliminated. My interviewer had 4-5 years of experience at Cisco. After introductions, we discussed my PPT solution, approach, and research. There was cross-questioning, and flaws in my solution were highlighted, prompting me to explain how I would address them. Basic questions on technologies relevant to my solution were also asked, though implementation wasn't strictly required. Before moving on, the interviewer asked me to rate my skills honestly. Subsequently, I faced questions on fundamental Computer Networks topics like the OSI Model, network Ports, and TCP connection. We also delved into my resume, discussing my internship experience, skills, and projects.
Round 3 (Managerial Round)
I was interviewed by a manager with over 20 years of experience. This round involved discussions about my PPT, projects, past interview experiences, and hypothetical situational questions to assess my behavior and communication skills. We also talked about the role itself.
Round 4 (HR Round)
Reaching this round was a strong indicator of selection, with a 99% chance of receiving an offer unless I declined to come onsite. The HR representative asked about my knowledge of Cisco, its competitors, and the company's current focus areas. She provided details on the internship duration, location, and estimated salary. The entire interview process was completed in a single day, with results declared a week later. I was successfully selected for the Intern + Full-time (Technical Consulting Engineer) role.
Interview Questions (3)
I was asked questions related to the OSI Model, a fundamental concept in computer networks.
Questions were posed regarding network ports, their function, and common uses.
I faced questions about the TCP connection process, likely covering topics such as the three-way handshake and connection states.
Preparation Tips
Based on my experience and observations, here are my tips for preparing:
- Prepare your introduction thoroughly, as it's the interviewer's first impression of your skills.
- Be extremely thorough with your problem statement and the solution you propose for the PPT round.
- Communicate actively with the interviewer; if you don't know an answer, don't guess, and avoid silence.
- Research common questions asked for your specific role to tailor your preparation.
- Always ask questions to the interviewer at the end of each round when given the opportunity, as this demonstrates your interest.
Summary
I interviewed for a Software Engineer Intern position at Cisco India, which included an online assessment, a technical round, and a managerial round. Despite performing well in the technical interview, I was rejected after the managerial round due to unexpected system design questions.
Full Experience
My journey to the Cisco India Software Engineer Intern 2024 role began after participating in 'Code with Cisco', though I didn't qualify through that. Surprisingly, I later received an email with an OA link for the summer internship.
Online Assessment:
The online assessment consisted of two coding questions and about 15-20 MCQs on Computer Fundamentals. Being in my 5th semester and having only studied OS till then, my knowledge of Computer Fundamentals was limited, so I answered only about 70-80% of the MCQs. For coding, I fully solved one question and passed 30% of test cases for the other. I didn't expect to clear this round.
However, a few days later, I received an email for further procedures, including submitting an inclusive resume. While I appreciate the concept of an inclusive resume, I was directly asked my college name in the managerial round, which I found perplexing, especially since I was rejected after that round.
Technical Round:
The day before my interview, I received a WebEx space link and a personalized meeting link for my scheduled interview from 8:30 to 9:15 a.m. I started my interview around 8:40 a.m. The interview began with a standard introduction, followed by a detailed discussion about my Android projects, which the interviewer seemed very interested in. Afterward, he transitioned to Computer Fundamentals, asking about the subjects I had studied. Based on my response, he asked many questions on Operating Systems. I hadn't revised much, so I couldn't answer them comprehensively.
Next, he moved on to problem-solving and data structures, which is my strong suit. I was asked three easy to medium-level questions. For each, I first discussed my solution and then quickly coded it on Notepad while sharing my screen, taking about a minute per question. The interviewer was very pleased. He then asked one more question in the last two minutes, confident I could solve it quickly, which I did. The interview concluded shortly after.
A few hours later, a list of rejected candidates was posted, and thankfully, my name wasn't on it! The next day, we were informed about the managerial round.
Managerial Round:
Similar to the technical round, I received a WebEx schedule and a personalized link for my interview from 9:30 to 10:15 a.m., which I started promptly. After a brief introduction, the interviewer immediately launched into discussing the design of an 'X Application' (the name wasn't revealed). He asked how it works, how it uses AI/ML, how the inventory system functions, how delivery boys are assigned using AI, and how products are delivered in minutes. He also posed a scenario: how would I handle slow responses during peak traffic, touching upon cloud, load balancers, and clustering. I was completely shocked, as I didn't anticipate such a system design question for an intern-level position. As a 3rd-year student, I was largely unfamiliar with these topics, but I tried my best to articulate any ideas I had. He then explained everything to me and wrapped up with some basic HR-level questions. I knew then that it hadn't gone well and expected rejection.
While some candidates proceeded to the ETR (HR) round, I kept checking for my name on the list, hoping to see it. However, after a few hours, the list of rejected candidates was shared, and my name was on it. Everything was finished.
Thanks, everyone.
Interview Questions (1)
Design an 'X Application' (name not revealed) considering its functionality and how it leverages AI/ML. Specifically, elaborate on:
- How the inventory system operates.
- How delivery personnel are assigned using AI.
- Strategies to ensure product delivery within a few minutes.
- How to manage slow application responses during peak traffic, including discussions on cloud infrastructure, load balancers, and clustering mechanisms.
Summary
I interviewed for a Software Engineering Intern position at Cisco for 2024, which included multiple coding rounds, a technical interview focusing on a project, and a managerial discussion. Despite clearing most stages, I was ultimately rejected after the final managerial round.
Full Experience
About Myself:
I am a dedicated B.Tech student majoring in Information Technology at Madan Mohan Malaviya University of Technology, Gorakhpur, currently in my third year. I am passionate about using my technical skills to drive innovation in the IT industry. I'm currently a Problem Setter Coding Intern at iMochaWorks and have experience as a Doubt Solver in CodeChef for competitive programming. My specialization lies in C++ and Java, and I am also exploring Full-Stack Development. I have achieved notable ranks in various competitive programming contests.
My Interview Journey at Cisco:
I had the opportunity to interview for the Software Engineering Intern position at Cisco for the year 2024. I would like to share my experience with you all.
Stage 1: Code with Cisco Online Coding Round
In the initial "Code with Cisco" coding round, my teammates and I successfully solved all three dynamic programming questions. However, despite our efforts, we did not make it to the next round because our completion time was 40 minutes, while the selected candidates completed the questions in 30 minutes. Nevertheless, due to our strong performance, we all received individual coding round links from Cisco.
Stage 2: Individual Coding Round
In the individual coding round, there were 30 aptitude questions and 2 coding questions. I managed to solve only one of the coding questions, but this was enough to help me clear this round.
Subsequently, I received an interview invitation. This technical interview round began with the interviewer asking me to showcase a project I had recently worked on—a to-do list application. I was tasked with implementing additional functionalities in the project, and I successfully completed all the assigned tasks.
Stage 3: Technical Interview Round
The interviewer then shifted the focus to computer network and operating system questions, to which I provided answers for about half of them. Following that, I was presented with some basic data structure and algorithms questions, which I managed to solve without any issues.
Stage 4: Managerial Round
After a few hours, I received an invitation for the managerial round, which was the final stage of the interview process. During this round, the interviewer again inquired about my project and was satisfied with my responses. We discussed computer network concepts once more, and I managed to answer about half of the questions correctly. The interviewer also asked me some managerial questions to assess my soft skills and decision-making abilities.
However, after waiting for two hours, I received the message that I did not clear the managerial round. While I'm not entirely sure about the selection criteria, I view this experience as a valuable learning opportunity and a chance to improve.
Interview Questions (1)
During my technical interview, I was asked to showcase a To-Do List application I had recently worked on. The interviewer then tasked me with implementing additional functionalities within this existing project.
Preparation Tips
Tips for Clearing the Interviews:
To succeed in interviews, I recommend:
- Preparation: Thoroughly prepare for technical rounds. Brush up on data structures, algorithms, computer networks, and operating systems. Practice coding problems regularly to improve your problem-solving skills.
- Project Showcase: Be ready to showcase your projects and explain your role and contributions clearly and concisely.
- Soft Skills: Work on your soft skills and be prepared to answer managerial and behavioral questions, which often assess your ability to work in a team, handle challenges, and make decisions.
- Time Management: Pay attention to time management, especially in coding rounds. Try to optimize your problem-solving speed while maintaining accuracy.
- Learn from Rejections: If you face rejection, view it as a learning opportunity. Understand your weaknesses and work on improving them for future interviews.
- Stay Positive: Stay motivated and remain positive throughout the interview process. Confidence and a positive attitude can make a significant difference.
Remember that interviews are not just about proving your technical skills but also about demonstrating your ability to work in a professional setting. Keep honing your skills, and you'll have a better chance of success in future interviews.
Summary
I interviewed for a Software Engineer - New Grad position at Cisco in Bengaluru and received an offer. The process involved an online assessment, two technical rounds, a technical + managerial round, and an HR interview, covering projects, CS fundamentals, various coding problems, and real-life system design scenarios.
Full Experience
I applied for the Software Engineer position at Cisco through a referral, as a 2023 New Grad passout with a Bachelor of Engineering in Computers from a Tier 3 college.
Online Assessment
I received a Hackerrank test link that included an easy coding problem, a couple of MCQs covering CS fundamental topics, and a medium-level dynamic programming problem similar to Burst Balloons on LeetCode. After successfully completing this, I was shortlisted for interviews.A notable aspect of the interview process was its emphasis on anonymity. I had to submit a redacted resume, and during the interviews, I was only allowed to mention a candidate code, not my name, college, or any other personal information. I really appreciated this bias-free approach.
Technical Interview 1
The first technical interviewer, an experienced Software Engineer, reviewed my resume and inquired about my projects, skills, and internships. We then delved deeply into my first project, discussing its architecture, potential flaws, performance, testing methodologies, and areas for improvement. Following this, we engaged in technical discussions on concepts from Computer Networks and Security (CNS), Operating Systems (OS), and Data Structures and Algorithms. I was also given a very easy coding problem, which I believe was primarily to assess my implementation skills. The feedback I received for this round was positive.Technical Interview 2
My second interviewer was also an experienced Software Engineer. Similar to the first round, he reviewed my resume and asked about my projects and internships. After explaining my project, we had a detailed technical discussion about it. This round featured a coding problem that evolved case by case, feeling like an open-ended challenge. We then discussed various OS concepts, specifically real-life applications on MacOS. I requested feedback at the end of the round, which was favorable.Technical + Managerial Round
This was the most intensive round, conducted by a panel of three highly experienced Software Engineers. After a brief introduction, they presented an open-ended, real-life problem with multiple facets. This problem rigorously tested my skills in DBMS, CN, Graph Algorithms, and several other concepts. The discussions were very low-level and lasted for about an hour, truly making me sweat. Following this, I was presented with a medium-level bit manipulation coding problem; I first outlined my approach and then wrote the code. The round concluded with a discussion about life and work at Cisco.HR Interview
The HR interview was a short round, lasting about 15 minutes. It began with a brief introduction and some casual conversation about my hobbies and interests. I was asked about my willingness to relocate to Bengaluru if selected, and whether I had any other job offers (I mentioned an existing offer from an MNC custodian bank for a Software Engineer position). We then had a discussion about Cisco and its operations.Later that same day, I received a Letter of Intent via email, along with the compensation details. I hope this experience proves helpful to others.
Interview Questions (1)
During the online assessment, I encountered a medium-level dynamic programming problem. It was described as being similar to LeetCode's Burst Balloons problem, which involves maximizing the coins collected by bursting balloons. While the exact problem statement was not provided, the difficulty and concept were explicitly linked to this well-known LeetCode problem.
Summary
I successfully interviewed for an SDE2 position at Cisco after five rounds, securing an offer. The interview process covered technical, coding, and behavioral aspects, with a focus on distributed systems and Java.
Full Experience
I applied for an SDE2 position at Cisco through a referral from a friend. My background includes 5 years of experience from India and Abu Dhabi, with a Master's in Software Engineering from ASU. I have a good amount of experience in distributed services, Kafka, Zookeeper, and feel confident with leadership principle questions, as well as SQL and NoSQL databases.
I received an interview request via an automated bot system, which I found to be quite inefficient.
Cisco Round 1: Technical Screen
This round primarily focused on my distributed systems background. I was asked questions related to Kafka, Zookeeper, microservices, and general distributed system concepts. There was also a detailed discussion on NoSQL vs SQL databases, specifically regarding sharding and distribution. Multithreading in Java, particularly in the context of distributed technologies, was also covered.For the coding part, I was given a problem to clone a linked list with a random pointer. The interviewer was very friendly, and I was able to solve it with some assistance, which allowed me to proceed to the next round.
Cisco Round 2: Coding Challenge
This round was a dedicated coding challenge, featuring the standard LeetCode Three Sum problem. It was recommended to check all variations of this problem.Cisco Round 3: Generic Java & Behavioral
This round involved generic Java-related questions covering topics like memory leakage, inheritance, and abstraction. Additionally, I was asked a few leadership and team-based questions.Cisco Round 4: Partial Technical
The interviewer was from the networking team and initially intended to ask networking-related questions. While I didn't have extensive knowledge in networking, I was fortunate as he didn't delve deeply into it. He was appreciative and motivating, acknowledging my new graduate status and quick learning ability.Cisco Round 5: Hiring Manager Final Round
In the final round with the Hiring Manager, I faced a few generic questions, including how I would approach debugging microservices. We also discussed my work experience in detail.Ultimately, I received an offer from Cisco for the SDE2 role.
Interview Questions (5)
A linked list of length n is given such that each node contains an additional random pointer, which could point to any node in the list, or null.
// For example:
// 1(4)->2(null)->3(2)->4(null)
/*
// Definition for a Node.
class Node {
int val;
Node next;
Node random;
public Node(int val) {
this.val = val;
this.next = null;
this.random = null;
}
}
Standard LeetCode Three Sum question. It is recommended to check all variations of this problem.
Discussion on the differences between NoSQL and SQL databases, including concepts like sharding and distribution.
Generic questions about memory leakage in Java.
Questions on how I would approach debugging microservices.
Summary
I recently completed an interview process for a Software Engineer role at Cisco in Bangalore, which comprised an online assessment, a pre-assessment, and multiple interview rounds including technical, managerial, and HR discussions. I am pleased to share that I successfully received and accepted an offer for the position.
Full Experience
About the Offer
- Location: Bangalore
- Stipend: INR 65,000
- Total Compensation (TC): 24,73,633 (base + bonus + other benefits)
Online Assessment (October 2021)
I started with an online assessment on HackerRank, which lasted 1 hour. It consisted of 15 MCQs covering Computer Networks, Databases, and Embedded Systems. Additionally, there were two coding questions, both of medium difficulty.
Pre-Assessment Round (December 2021)
Following the initial assessment, I had a pre-assessment round, also on HackerRank, lasting 30 minutes. This round featured one coding question of easy to medium difficulty.
Technical Round (December 2021)
The technical round was conducted via Cisco WebEx and lasted 1 hour. It began with my self-introduction and a detailed discussion of my resume, where questions were asked about the topics I had mentioned. We delved into Networking concepts like TCP/UDP, tracert, and ping, and I was asked to explain the process of opening www.cisco.com on a browser. There were other easy to moderate level network questions as well.
I also faced a design-based question where I had to design a vending machine and list down its test cases, focusing on user interaction, payment, and inventory control. Another task involved designing an API framework for logging using Linux commands. My knowledge of Linux, terminal commands, and DevOps was also tested. I also encountered an easy-level coding question based on frequency maps, with extensions discussed.
Managerial Round (December 2021)
This round, also on Cisco WebEx, lasted 45 minutes. It involved general discussions about my interests outside of technology and typical HR questions such as how I would solve a conflict. We also talked about my knowledge of Cisco and lighter topics like iPhone vs Android or CSK vs RCB.
HR Discussion (December 2021)
The final HR discussion, lasting 15 minutes on Cisco WebEx, included a self-introduction, discussions around package expectations, preferred location, my greatest accomplishments, why I was interested in Cisco, Cisco's competitors, any plans for higher studies, and my current offers.
Verdict
I am happy to report that I received an acceptance for the role.
Interview Questions (5)
I was tasked with designing a vending machine system, considering aspects like user interaction points, payment processing, and inventory management. Additionally, I had to outline a comprehensive set of test cases for the design.
I needed to design an API framework for logging, specifically leveraging Linux commands for its implementation.
I was asked to describe the sequence of events and underlying protocols involved when a user types "www.cisco.com" into a web browser and hits enter.
I was asked to describe my approach to solving a conflict, likely in a team or work environment.
I discussed my greatest accomplishments, my motivations for wanting to join Cisco, my knowledge of Cisco's competitors, future plans for higher studies, and any current job offers.
Summary
I successfully navigated three rounds of interviews at Cisco for an internship position, ultimately receiving an offer despite some challenges, particularly in the managerial round where I was grilled on my AI/ML interest not aligning with the department's work.
Full Experience
I recently interviewed for an internship at Cisco, which involved three distinct rounds: two technical and one managerial. The overall experience was insightful, and I eventually received an offer.
Round 1 (Technical)
This round began with an introduction where I candidly shared my passion for Machine Learning, Python, and Deep Learning, mentioning my basic knowledge of C and lack of extensive competitive programming experience. The interviewer acknowledged my programming fundamentals and then posed two coding challenges. First, I was asked to write a C function to determine if a given number is a power of two, which I easily explained and coded. The second question involved searching for a number in a sorted and rotated array efficiently. My solution utilized binary search, and I was subsequently asked to implement binary search in my preferred language. We also discussed complexity theory, and I was asked to code Quick Sort. I initially struggled with Quick Sort, but the interviewer was incredibly helpful, even explaining the concept with an example. This round lasted about 25-30 minutes, with a significant portion dedicated to my ML projects and their underlying algorithms.
Round 2 (Managerial)
This round proved to be quite challenging. The manager reviewed my resume and immediately expressed concern, stating that his department was not involved in AI/ML/DL, fields prominently featured on my resume. He directly questioned why he should hire me, suggesting it would be a waste of both my time and Cisco's resources. While I initially perceived this as a test of patience, my passion for AI led me to counter his argument. I pointed out that Cisco's earlier presentation highlighted their involvement in AI/ML/DL, questioning why his department specifically wasn't. He clarified that while Cisco as a whole works in AI, his specific department did not. I then argued that given another year before joining Cisco, I could learn new areas, much like how I had learned AI/ML/DL from scratch in the past year, completing two internships. He appreciated my response but remained somewhat unconvinced. He then asked if I had interviewed elsewhere, which I, regrettably, falsely denied, claiming Cisco was my first choice. This led to a follow-up about my long-standing interest in Cisco, which I also falsely affirmed. When asked for the CEO's name, I couldn't recall it. The manager advised me to be more careful with my answers, but ultimately, he seemed satisfied with the interview's outcome, asking me to wait for further rounds. Despite my blunders, I was eventually selected.
Round 3 (Technical)
Two interviewers conducted this final technical round. After my introduction, a power outage occurred due to heavy rain, which I used as an opportunity to elaborate on my projects. Once the power returned, they transitioned to DSA and puzzle questions. We briefly discussed my favorite cricketer (MS Dhoni) and my role in cricket, given my mention of it. Then, they presented three main questions. The first coding question asked me to write code to swap adjacent nibbles in a number. My initial solution was unoptimized, and they hinted at using bitwise operators, which I later realized was given earlier when they asked if I knew operators. I successfully optimized it using 'or' and 'xor', significantly reducing space complexity. We also discussed the time and space complexity of my algorithms. The second question was a puzzle: calculating the maximum distance a car can run with four new wheels and one new spare, where each wheel lasts 20,000 km. I was close but made a calculation error and couldn't find the exact answer before they moved on. The final coding question involved writing efficient code to count the frequency of each character in a string. I explained an initial method and was able to further optimize it as requested. They seemed satisfied with my solutions throughout this round.
Interview Questions (8)
Given an integer, write a function to determine if it is a power of two. Implement the code in C.
Given a sorted array that has been rotated some number of times, and a target number, write an efficient code to determine if the target number is present in the array.
Implement the Quick Sort algorithm. I struggled with this initially, but the interviewer was very helpful and explained the concept with an example.
The manager challenged me on why I should be hired given that my primary interest (AI/ML/DL) does not align with their department's current work.
I was asked to name the CEO of Cisco.
Given a number, write efficient code in your favorite language to swap adjacent nibbles (four bits consecutively). Initially, I came up with an unoptimized solution and was prompted to optimize it, with a hint about using bitwise operators.
A car has four new wheels and one new spare wheel (Stepney). Each wheel can run for a maximum of 20,000 km. Calculate the maximum distance the car can run.
Given a string, write efficient code to count the frequency of each character in that string. I initially explained one method and was then asked to optimize it further.
Summary
I interviewed for a Software Engineer 1 role at Cisco in Bangalore, which involved three rounds covering data structures, algorithms, OS, C concepts, and behavioral questions. I found the technical rounds challenging but manageable.
Full Experience
My Interview Experience at Cisco for Software Engineer 1
I applied for the Software Engineer 1 position at Cisco through their company portal. Shortly after, I received a call from HR to schedule interviews. I requested a few days to prepare, and the interviews were set for about 4-5 days later.
Round 1: Technical (1 hour)
This round focused primarily on data structures and algorithms, along with core computer science fundamentals. I was asked to:
- Count the total number of nodes in a binary tree.
- Find the number of leaf nodes in a binary tree.
Additionally, the interviewer posed questions on OS internals, covering topics like mutexes, semaphores, threads, heap, and stack. There were also questions on bit manipulation, networking concepts (routers, packets, switches), and endianness (big and little).
Round 2: Technical (1 hour)
The second technical round delved deeper into C programming and problem-solving. Key questions included:
- How to find the middle element in a Linked List.
- How I would design a generic structure in C that could hold any data type.
This round also featured several questions on C covering memory allocations, static and global variables, structure padding, and macros. Tricky bit manipulation problems were discussed, emphasizing the importance of strong basics. Further theoretical questions on mutexes, semaphores, and Inter Process Communication were also part of this round.
Round 3: Hiring Manager (30 minutes)
This was a standard hiring manager discussion. I was asked typical behavioral questions such as my motivations for wanting to switch companies, specifically why I was interested in Cisco, and how I envisioned myself fitting into the Software Engineer 1 role.
Interview Questions (5)
Write a function to count the total number of nodes in a given binary tree.
Write a function to find the number of leaf nodes in a binary tree.
Given a singly linked list, find its middle element.
How would you design a generic structure in C that can hold any type of data?
I was asked several standard behavioral questions, including my motivation for switching companies, why I was interested in Cisco, and how I envisioned myself fitting into the specific role.
Preparation Tips
I requested a few days from HR to prepare for the interviews before they were officially scheduled.