Real, anonymous reports from people who interviewed for Software Engineer at Netsuite, newest first and distilled into what to expect across the loop.
My process started with HR, then I met two tech managers. In those conversations I learned the project had a monolithic setup and was so big they couldn’t realistically run everything locally, so I’d be working with remote VMs. I also picked up that the work wasn’t really split into independently deployable modules, which implied CI/CD would be slow and releases would likely land only weekly or monthly.
After applying, I went through a fairly structured, four-round flow that started with an online assessment on HackerRank. A lot of people showed up, and only a smaller group got shortlisted after that first round. The next step was a coding-focused round where I worked through questions covering things like arrays, linked lists, and strings.
The interview process typically consists of multiple rounds, starting with HR screenings, followed by technical assessments, coding exercises, and often concluding with managerial interviews. Candidates should expect a mix of online tests and in-person coding sessions, with some reports indicating a structured flow that can span several weeks.
Candidates will face a variety of technical challenges, including algorithmic problems, data structures, and sometimes SQL queries. The coding rounds often emphasize speed and correctness, with interviewers observing how candidates approach problems rather than just the final solutions.
Communication throughout the process can be inconsistent, with some candidates experiencing delays in feedback and follow-up. While initial HR interactions may be prompt, the overall timeline can stretch, leading to uncertainty about progress and outcomes.
The interview environment is generally described as professional and respectful, with interviewers aiming to assess fit and technical skills in a supportive manner. However, some candidates noted instances of impatience or rudeness from specific interviewers, which can impact the overall experience.
Candidates can expect a mix of assessment types, including take-home assignments, live coding sessions, and group exercises. The assessments often focus on practical coding skills and problem-solving abilities, with some reports highlighting the use of pseudo code and algorithm design.
Many candidates report not receiving offers despite positive experiences, often reflecting on the demanding nature of the technical evaluations. The overall impression tends to be that the process is rigorous, with a focus on technical depth and problem-solving rather than just theoretical knowledge.
