FullStory Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at FullStory.
FullStory
Software Engineer
Entry Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen
Interview formats
Behavioral Coding Technical
The interview process involved a few stages. First, I had a phone chat with the recruiter. Then, I had a webcam meeting with a team lead. After that, there was a one-hour coding exercise, followed by a four-hour coding exercise that was split into four parts: a front-end part in the language I chose, an API endpoint and access pattern part in the language I chose, a backend part in the language I chose, and finally a round of behavior questions. They didn't ask any tricky or insulting questions. They also gave me a guide beforehand with links about the company, how to answer behavior questions, how to prep for code exercises, videos of people doing coding exercises, and links to the web environments they use. It felt like they wanted me to succeed.
Confirmed questions5 questions
- Parse data from one structure to another.
- Build a frontend application that takes an endpoint, triggers an API request, and then make it safe and QA it.
- Build an endpoint, hit it, and then optimize it.
FullStory
Software Engineer Intern
Intern Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding Presentation
The recruiters were super supportive and enthusiastic about this role, just like I was! The hiring managers and engineers were also really experienced and helpful. They not only answered my technical questions and talked through my experiences, but also taught me some cool skills during the interviews. This whole process made me excited about FullStory's work and gave me a glimpse into a great work environment that really values both intellectual curiosity and empathy, which I haven't seen much before.
Confirmed questions4 questions
- Describe your experience working as a team member.
- Can you share an example of a technical bug you encountered and solved?
- Build a front-end application that uses an API.
FullStory
Software Engineer
Senior Difficult Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding
The interviewers personality was dry as sandpaper. Questions are designed to be tricky, puzzle type questions. They're contrived, pedantic, tedious and don't bare resemblance to code that people actually write day to day. Interviewer acted demeaning. Honestly the worst interview I've ever experienced. With 1 minute remaining in the interview I was asked if I had any questions for him, lol
Confirmed questions1 question
- Could you write a markdown parser in 30 minutes?
FullStory Software Engineer Interview Questions
Quoted word for word from FullStory interview reports.
“Create a markdown parser”
Read reports →“What would happen if the user hit the endpoint hundreds of times?”
Read reports →“Could you explain the common notion that SQL databases don't scale while NoSQL databases do?”
Read reports →“What are the flaws of the endpoint?”
Read reports →“Build an endpoint, hit it, and then optimize it.”
Read report →“Build a front-end application that uses an API.”
Read report →“Can you encode and decode a string based on specific rules?”
Read report →“Could you write a markdown parser in 30 minutes?”
Read report →“Build a frontend application that takes an endpoint, triggers an API request, and then make it safe and QA it.”
Read report →Formats, difficulty and experience
Across all 12 FullStory interview reports.