Real, anonymous reports from people who interviewed for Software Engineer at Extreme Networks, newest first and distilled into what to expect across the loop.
I went through a campus-style process where the questions felt very core-CS and fundamentals-heavy rather than anything tied to a specific product. The format was mostly a test-style flow before any deeper interviewing: I got hit with OSI layers and basics like bubble sort, binary search, and linked-list insertion patterns, plus bitwise operators.
My interview process ran over about three weeks, with five rounds total. It started with a phone screening, and then the remaining four rounds happened onsite in person. Each round lasted roughly an hour to an hour and a half, and the structure stayed pretty consistent: a coding question each round (mostly in the “NC150” style range), plus backend-focused questions and some theoretical system-design concepts alongside things from my resume.
The interview process typically consists of multiple rounds, often including a phone screening followed by several onsite technical interviews that can last from three to five hours in total. Candidates should be prepared for a structured flow that includes coding challenges and discussions around their resume and project experience.
Interviews heavily emphasize core computer science fundamentals, including data structures, algorithms, operating systems, and networking concepts. Candidates should be ready to tackle coding questions and theoretical discussions that assess their breadth of knowledge in these areas.
Candidates can expect to face coding challenges that test their problem-solving abilities, often involving debugging and real-time coding tasks. It's important to demonstrate clarity in thought and approach, as interviewers focus on how candidates tackle problems rather than just the final answer.
The communication style throughout the process can vary, with some candidates experiencing a lack of feedback and abrupt endings that leave them feeling confused or frustrated. It's advisable to seek clarity on performance and next steps after each round to mitigate uncertainty.
The timeline for the interview process can be lengthy and inconsistent, with some candidates reporting delays and a lack of professionalism in communication. Candidates should be prepared for potential waiting periods and follow up proactively to stay informed about their status.
While many candidates report a structured and organized interview experience, the final outcomes can vary significantly, with some feeling misled about their performance or the hiring decision. It's important to maintain realistic expectations and be prepared for any outcome.
