RSUs and salary: The salary is just barely on par (and even a bit lower) with competitors', but the RSUs are what really get you.
Since Fortinet is such a large company with a generally good public impression, you will encounter some skilled engineers. If you are lucky and make the initiative, you may get to work and learn from them.
Some people are nice.
I worked at Fortinet for over 4 years. I wish I had better things to say, but I do not.
I generally agree with the points made by other reviewers about the language biases, archaic methods, and mismanagement.
If you are reading this and wondering whether you should accept an offer from Fortinet, my suggestion is: Don't (especially if you are entry-level or junior).
With the exception of very (and I stress very) few teams, Fortinet does not provide good mentorship nor teach you industry practices that will develop your engineering skills. On the contrary, it may even hinder your development as an engineer.
Upper management sees you as numbers that fill spots. They will reorg you with very little notice (less than a week) and provide no reason for it. If you want to move laterally, animosity among teams and general disapproval from upper management will often result in a rejected request.
Product management is a mess: there is little cohesion between product management and the engineering departments.
Team management is unprofessional. I have seen the extremes of micromanagement to no management at all. Managers may neglect communication with their own team members, from a month all the way to six months (!?) without a word.
From all the teams I have been in and interacted with, I would say 95% of them do not follow most engineering best practices:
Please take it with a grain of salt, as all this above was either my own experience or of those that I witnessed while at this company.
Live by your values if you are going to set them as company values.
Invest in your employees and software practices. Train managers and team leads properly.
The HR representative initially contacted me by phone and explained the interview process. I was then given four coding questions, which were similar to a HackerRank-based test but slightly modified. Unfortunately, I didn’t pass that stage, so I don’
Behavioral Interview with HR The first stage involves a conversation with HR to assess cultural fit, communication skills, and alignment with the company’s values and expectations. Technical Take-Home Assessment Candidates are then given a technical
First round: 2 coding questions using C. You need to have knowledge of basic data structures. Also, you need basic knowledge of computer networks and operating systems, especially regarding TCP and inter-process communication.
The HR representative initially contacted me by phone and explained the interview process. I was then given four coding questions, which were similar to a HackerRank-based test but slightly modified. Unfortunately, I didn’t pass that stage, so I don’
Behavioral Interview with HR The first stage involves a conversation with HR to assess cultural fit, communication skills, and alignment with the company’s values and expectations. Technical Take-Home Assessment Candidates are then given a technical
First round: 2 coding questions using C. You need to have knowledge of basic data structures. Also, you need basic knowledge of computer networks and operating systems, especially regarding TCP and inter-process communication.