My experience began with an extremely difficult online assessment, and before that I also had the usual early touchpoints—there was a recruiter call and then a LeetCode-style technical prompt. After the resume chat, the coding question was about building a binary tree with chunking to hold a massive string, and the task included handling balancing.
It felt brutally hard right from the start because the problem wasn’t just “implement a tree”—it was really about how to structure the chunking and keep the balancing behavior correct. I ended up failing that technical step, so nothing else followed.
> 1 year
Difficult Positive Palo Alto, CA
I kicked things off with a front-end tech screen where I briefly introduced myself and then jumped straight into a React coding question. The difficulty felt somewhere around mid-level, and after that the process quickly accelerated into an onsite with five back-to-back interviews that added up to about five and a half hours.
On the technical side, there were three technical conversations, one system design interview, and one cultural fit interview. The system design discussion was a little tough, but the interviewer worked with me to get through it. The coding rounds varied, with two of them feeling moderate and another landing closer to a harder range. The cultural interview was much more relaxed, mostly a “tell me about a time” style discussion.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
