Real, anonymous reports from people who interviewed for Software Engineer at Gigamon, newest first and distilled into what to expect across the loop.
I started with a written test that felt like the first real filter. It was a mix of multiple-choice questions, including aptitude and cloud-related topics, plus two coding questions. After that, about a week later I went into a technical interview focused on networking fundamentals—DNS and the application layer, DHCP, and SMTP came up.
A lot of my frustration came from communication, not the interviews themselves. After an initial HR interaction went “well,” I was told the next steps would be scheduled and then the calendar just never moved. I followed up, but there was no response—eventually I got a rejection email with no meaningful explanation. The delay and silence felt unprofessional, especially after HR had sounded confident about scheduling.
Candidates typically start with a written test that includes multiple-choice questions on aptitude and cloud topics, along with coding challenges that serve as a preliminary filter.
The technical interviews focus heavily on fundamental programming concepts, including data structures, algorithms, and language-specific knowledge, particularly in Java and C, with practical coding tasks.
Candidates will engage in a managerial-style discussion where they walk through their project experiences, emphasizing problem-solving approaches rather than on-the-spot coding.
The HR round covers background checks and compensation discussions, but candidates have reported mixed experiences regarding communication and follow-up throughout the process.
The overall interview experience is described as moderately challenging and structured, with candidates noting that while they did not receive offers, the process felt organized and respectful.
Candidates have expressed frustration with the lack of timely feedback and follow-up from HR, which can leave them feeling unappreciated despite the interview experience itself being positive.
