Real, anonymous reports from people who interviewed for Software Engineer at Fortinet, newest first and distilled into what to expect across the loop.
After I got referred, I heard back from HR and the process quickly became very structured. I went through an online assessment first, then five separate technical rounds, and finally an HR round. It felt like a fairly direct pipeline: referral led to the HR call, which then led straight into the technical sequence.
I started with a recruiter call to cover general background details, and then the process moved to a 75-minute online test. After that, I went into a face-to-face interview. The role itself was hybrid, so I had the expectation of going into the office about two times a week.
The interview process is typically structured with an initial HR call followed by an online assessment, multiple technical interviews, and sometimes a final HR or executive round. The overall timeline from application to offer can range from a few weeks to a couple of months, and candidates noted that the process felt organized and responsive.
Candidates reported a strong emphasis on software engineering fundamentals during technical interviews, including programming tasks, system design, and architecture discussions. The assessments often included coding challenges on platforms like HackerRank, with a mix of LeetCode-style problems and domain-specific questions related to networking or security.
Behavioral interviews were a common component, focusing on candidates' past experiences, project discussions, and alignment with the company's values. Candidates often felt that these rounds were conversational and aimed at understanding their fit within the team and company culture.
Candidates appreciated the clarity and organization of communication throughout the process, although some experienced delays in feedback or closure after interviews. Constructive feedback was noted as a positive aspect, while a lack of follow-up left some feeling uncertain about their performance.
The interview panels included a mix of technical engineers and management, with some candidates experiencing a more intense evaluation from technical interviewers compared to HR or managerial rounds. The diversity in interviewers contributed to varying levels of pressure and expectations during the interviews.
While many candidates did not receive offers, reflections highlighted the thoroughness of the process and the importance of preparation for both technical and behavioral aspects. Some candidates felt blindsided by decisions that did not align with their interview experiences, indicating a potential disconnect between interview performance and hiring outcomes.
