Software Engineer applicants have rated the interview process at FullStory with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 71% positive. To compare, the company-average is 54.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 14 days to get hired, when considering 7 user submitted interviews for this role. To compare, the hiring process at FullStory overall takes an average of 21 days.
Common stages of the interview process at FullStory as a Software Engineer according to 7 Glassdoor interviews include:
Phone interview: 26%
Presentation: 21%
One on one interview: 21%
Drug test: 11%
Skills test: 11%
Group panel interview: 5%
Background check: 5%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1 week. I interviewed at FullStory in Nov 2019
Interview
Was contacted by a recruiter on LinkedIn. Had an informal call over the phone to discuss the position and was scheduled a phone-video coding interview through coderpad. After coming up with the solution and showing the interviewer my code, He just said.. Oh.. I don't know Java... I'm a Javascript guy...Then you shuldn't state I can solve the problem in any coding language I like.... BTW I'm pretty sure that I solved the problem correctly and got the output that was expected. Still got a rejection email without any feedback, just that they won't be able to proceed further. No reason, No feedback, no nothing!!! Are you kidding me?
I applied through a recruiter. The process took 2 weeks. I interviewed at FullStory in Mar 2022
Interview
1: Phone interview with the recruiter.
2: Webcam meeting with a team lead.
3: one-hour-long coding exercise.
4: four-hour-long coding exercise broken into four different exercises.
a: one front-end exercise in the language of your choice.
b: One API endpoint & access pattern in the language of your choice.
c: One backend exercise in a language of your choice.
d: lastly a round of behavior questions.
All & all I didn't get any gotcha questions or questions that felt insulting like "What is Object-oriented programming" or "What version is the IDE that you use is on?" (Yes I have been asked that in an interview)
They also provide a guide ahead of time with links about their company, how to answer behavior questions, how to prep for code exercises, links to videos of people taking coding exercises, and links to what web environments they use to conduct the interview. All of these made me feel like they were trying their best to set me up for success instead of ween me out.
Interview questions [1]
Question 1
QT: Parse parse data from one structure to another.
QT: Build a frontend application that accepts an endpoint and triggers an API request. Now make it safe and QA it.
QT: Build and endpoint. Hit endpoint. Optimize it, what are its flaws? What would happen if the user hit the endpoint hundreds of times.
I applied through an employee referral. The process took 4 weeks. I interviewed at FullStory in Sep 2021
Interview
Recruiting Process:
Initial recruiter call -> chat with team manager -> 1 hour technical interview -> 4 hour (4 - 1 hour sessions) technical interview session.
The recruiter and the team I was interviewing with were very responsive and I felt like the whole process was very fair. Everyone I met was nice and every technical interview question was challenging but more in a satisfying real world problem kind of way versus a difficult puzzle-y leetcode typpe of way.
Interview questions [1]
Question 1
Questions were based on real life problems versus the tricky leetcode problems you might see on online practice sites.
I applied through a recruiter. The process took 2 weeks. I interviewed at FullStory (Atlanta, GA) in Jul 2021
Interview
Started with a conversation with a recruiter. After that had ~6 interviews all ranging from technical, behavioral, and conversations with hiring managers all geared towards finding the right fit for the candidate.
The technical interviews consisted of some algorithmic and some practical. The great thing is that they are not trying to get you to regurgitate any specific algorithms, but rather gauge your critical thinking and problem solving skills.
Overall, it was a fun experience where I felt I could properly showcase my abilities and not like other technical screens which tend to try and break the candidate down.
Interview questions [1]
Question 1
A mixture of practical and algorithmic but not regurgitation.