FullStory logo

FullStory Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 93 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
58.1% Positive experience

Which role are you interviewing for?

30 roles · 93 reports

Candidate interview experiences

First-hand accounts from people who interviewed at FullStory.

Showing 4 of 93
FullStory logo
FullStory

Client Success Manager

Sales · more than a year ago

Senior Easy Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen Offer
Interview formats
Behavioral Technical

The process was pretty fluid and moved quickly. About a week after I applied, the recruiter emailed to set up a call. A week after that, I had a video chat with the hiring manager. They sent a thank you email a few days later with the final decision. Even though it wasn't in the job description, the hiring manager was looking for someone with technical knowledge in analytics and web development. If I had moved forward, the next steps would have included a presentation and 3-4 interviews with the team.

Confirmed questions4 questions
  • Can you introduce yourself and walk me through your career path?
  • What motivated you to apply for this position?
  • Describe your approach to conducting a Quarterly Business Review (QBR) meeting.
FullStory logo
FullStory

Customer Marketing Manager

Marketing · more than a year ago

Mid Average Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Take home Group Recruiter call Offer
Interview formats
Behavioral Case Presentation Group

I spoke with a recruiter in late May 2022 and they said the whole thing would take about 3 weeks. Then I had a 30-minute meeting with the hiring manager. After that, I had to do a 1-2 hour challenge where I had to create a ppt deck with a customer marketing strategy, a marketing email, and ideas for meeting revenue targets. The challenge said 3-4 hours, and it turned out to be 3-4 hours. Then, I had back-to-back team interviews with different people for over 2 hours. At the end, I met with the recruiter again and they told me that hiring for this role was delayed and it wouldn't start until August, even though it was mid-June. They also said they wouldn't have a decision until late June because of another candidate's timeline. I waited and emailed to check on the status after June 27th, and was told the recruiter I was working with was out of office and would email me when they got back. They emailed me this week, a full 3 weeks after my last interview, and said they'd get back to me with a definite answer in 48 hours. After 48 hours, I followed up and they said they assumed I wasn't interested since I hadn't replied to their email two days prior, which didn't actually ask me to do anything. I'm guessing I didn't get the job and wouldn't suggest wasting your time interviewing with a company that's so disorganized and doesn't respect candidates' time.

Confirmed questions3 questions
  • Can you share an instance where you made an error?
  • Describe the marketing programs you have managed.
  • What is your background with customer advocacy initiatives?
FullStory logo
FullStory

Software Engineer

Engineering · more than a year ago

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 logo
FullStory

Senior Product Marketing Manager

Marketing · more than a year ago

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Technical

The recruiter wasn't very enthusiastic and just read the job description verbatim without offering any extra details or asking about my preferences for the role and company environment. It seemed like they weren't very familiar with product marketing, as they questioned my skills even though they matched the job description when I recited my resume. I was directly asked why I had left previous jobs in under a year, and though my explanations (time zone issues with an international manager and career growth) made sense to them, they warned that the hiring manager would also ask. They mentioned wanting a PMM for a new mobile product line, but couldn't provide specifics, which seemed important despite not being in the job description. Even with prior mobile product experience, I wasn't advanced in the process. The only positive was being informed quickly about not moving forward, even though it was a day later than expected.

Confirmed questions5 questions
  • Can you introduce yourself and discuss your background?
  • What do you know about Full Story and what motivated your application?
  • Could you detail your experience with mobile products?

FullStory Interview Questions

Quoted word for word from FullStory interview 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

Can you encode and decode a string based on specific rules?

Read reports

Build a frontend application that takes an endpoint, triggers an API request, and then make it safe and QA it.

Read report

Can you explain the workings of session recording, detailing what information is collected, the triggers for collection, and how to verify its accuracy?

Read report

Would you be able to create a React UI that takes in input and hits an API and displays results?

Read report

How would you improve and scale a system that has several single points of failure?

Read report

Could you explain FullStory in the absolute simplest terms, as if you were telling your mom or grandma what you do?

Read report

Formats, difficulty and experience

Across all 93 FullStory interview reports.

Interview formats

Behavioral 42.5%
Technical 25.5%
Presentation 13.5%
Coding 6%
Case 5%

Interview difficulty

Easy 10.8%
Average 67.7%
Difficult 21.5%

Candidate experience

Neutral 16.1%
Positive 58.1%
Negative 25.8%

Reports by job function

Sales 32
Engineering 18
HR 14
Operations 11
Marketing 7
Finance 6