Where do I begin? The process started simple enough with HR screen and then the HM screen a day later. A few days later was the technical assessment but I don't think they realized what role they were interviewing for. The interviewer had no idea whether I was signing up for a Full-Stack or Front-end role. Sadly, and unfortunately, I was asked a leetcode problem which I had not studied. Naturally, I did not pass and didn't make it to the next round. I will say that the interviewer really did feel like he was reading from a script. Anytime I said something, he'd longingly pause and then say "...right" like he'd just dismiss everything I said prior. It's a shame that FullStory believes that gaming a system and "studying" the right answer is a way to achieve success as a software engineer because these types of "leetcode" interviews can sometimes feel "silly" because they often present overly contrived scenarios that will most likely not directly translate to real-world coding situations at FullStory, with some people criticizing the focus on memorizing specific problem patterns rather than developing a deep understanding of core programming concepts; essentially, they can seem artificial and not representative of actual development work. And if you get past the "memorize-and-pass" round, you have two more live-coding technical interviews. If a company needs multiple technical interviews to figure out whether you're a good fit -- look inward. Please. In the end, it really just proves that using Leetcode to select future employees at FullStory is about as useful as rearranging the deck chairs on the titanic. This type of work is not that difficult. The interview itself should be the hardest part of the job and should not be forced to "remember answers."

Pretty standard process. Starting with a Recruiter Call then Hiring Manager Call then Technical Phone Screen and finally Virtual On-Site with five interviews (1 System Design, 2 Coding, 1 Product, 1 Values).