Taro Logo

Staff Software Engineer Interview Experience - United States

May 1, 2026
Negative ExperienceNo Offer

Process

Process was really sloppy and confusing. I don't think the interviewers had a tight process, they were disorganized and it was unclear what data points they were looking for.

Recruiter - Before the onsite interviews were scheduled, she mentioned there wouldn't be any coding in the rounds. This was later found to be untrue. She also linked me to the wrong role (upleveled by one) which might have been the reason why the subsequent rounds were really sloppy and weird.

Round 1 - Talk with the lead engineering architect: Informal talk about past experiences and technologies, architectures, etc. The interviewer didn't really talk about the job role, sounded conceited from the get-go and only had interest in critiquing my past work. As the conversation with past experience got deeper and deeper, he then realized he got carried away with chatter for 50 minutes and only realizing there was 10 minutes left, so he had to cram in a whiteboard design session in that brink of time which could not be completed.

Round 2 - Coding. It consisted of a LeetCode Medium problem and a separate AI coding session. The biggest problem here was that the interviewers were not very interactive in conversations at all. For the LC problem, I gave a sub-optimal solution as a first pitch but explained my thought process, and they sat in silence with a puzzled face as if they were only expecting to see one exact output based on the LeetCode Solutions. There wasn't any nudging towards the right path by them and it ultimately felt like I was talking to a wall for majority of the interview until we had realized too much time was spent on this half of the segment and it was better use of time to move on to the AI section.

For the AI round, it was also apparently the interviewer's first time asking an AI coding question, and to this day I still don't understand what the purpose of it was. The AI question was structured such that the candidate is expected to create a new codebase from scratch using AI. The README provided all the instructions on what the application needs to accomplish. The AI agent was able to solve the problem within 3 minutes via a simple prompt, taking in the README instructions that was provided. Due to how trivial the problem was and how powerful Claude models are, there weren't any opportunities to showcase problem solving, fixing bugs, or design tradeoffs.

Other companies approach this by simply providing

  1. An incomplete codebase with bugs and insufficient test cases and/or
  2. Making the AI model "dumber" to test how the candidate utilizes AI when it makes mistakes. This problem had neither of that - it was as if the candidates did not expect the AI models to complete the problem so quickly, and were scrambling for follow-up questions that they didn't think of beforehand. My last frustration with this round was that they decided to bundle these two confusing sessions in one hour, with an awkward context switch of borrowing an employee's laptop and their unfamiliar dev environment just to start the AI coding segment. The process was sloppy

Round 3 - Informal talk with manager. Conversations felt very casual, with only one critical behavioral question about "How you resolve disagreements". Didn't really talk about the job role I was applying for, but briefly mentioned some of the challenges in their product/team.

After the interview day, there was no response from the recruiter. Not even a rejection notice. All in all, very lackluster interview experience from start to finish. Getting a rejection notice knowing that you were able to showcase some or all your skillsets is still a good feeling in my opinion, but in this interview I felt confused throughout the whole process not knowing what they want, and I don't think they knew what they wanted either.

Questions

How do you resolve disagreements with a coworker?

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the Fortinet Staff Software Engineer role in United States.

Success Rate

0%
Pass Rate

Fortinet's interview process for their Staff Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive50%
Neutral0%
Negative50%

Candidates reported having mixed feelings for Fortinet's Staff Software Engineer interview process in United States.

Fortinet Work Experiences