
FireEye Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 41 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at FireEye.
Software Engineer
Got a call from an in-house recruiter who set up a call with a director, but instead an engineer called about 40 minutes late and asked some easy questions for about half an hour. The next day, the director called unscheduled, spent half an hour selling the company, and set up an in-house interview for the day after. The in-house interview included a multiple-choice skills test, some of which had no correct answers, followed by 1:1s with four or five people, including programmers and another director, lasting about three hours. After that, I left with no further communication, and even after a follow-up email, there was silence.
- Could you tell me the number of optimization levels in GCC?
- What signal is thrown and what are the different signals, and when do they occur?
- How many different types of sockets exist?
Software Engineer
The interview process involved an initial online HackerRank coding challenge, followed by a face-to-face technical interview, and then a managerial interview. I attended the second round, the technical interview, and felt it went well. I was able to explain the design questions and correctly implement the programming. However, despite positive feedback expectations, I received no response from HR, even after sending two emails. The process felt unprofessional, and the interviewer seemed confused or uninterested, experiencing connection issues and taking breaks during the hour-long session.
- Could you discuss tree search algorithms?
- How would you design a system incorporating a database and an LRU cache?
- Please provide code to implement an LRU cache.
Software Developer
The hiring process went pretty smoothly, I went through 3 rounds total. It started with a call from HR, which was pretty standard. Then I had two more interviews. Both the second and third interviews were very focused on my resume. They dug deep into projects they thought were relevant to the role, and basically asked about what I would be doing on the job. I got a call from HR within a week saying I got the job, and then they sent over the offer letter.
- Can you walk me through the projects on your resume?
FireEye Software Engineer Interview Questions
Quoted word for word from FireEye interview reports.
“Implement a regex matcher with '?' and '*' support.”
Read reports →“Can you swap letters between numbers in a string?”
Read reports →“Could you tell me the number of optimization levels in GCC?”
Read reports →“There was a question about reversing digits of a number: A is formed by reversing the digits of B. B is 45 less than A. The sum of the digits of B is 9. What is A?”
Read reports →“Could you explain what it means for HTTP to be stateless?”
Read report →“Explain the difference between TCP and UDP and their use cases.”
Read report →“Could you explain this code snippet (Merge Sort)?”
Read report →“Can you parse a CSV file to extract elements from the nth column?”
Read report →“Can you design a data structure where read, write, delete, and random read operations are all O(1)?”
Read report →Formats, difficulty and experience
Across all 41 FireEye interview reports.