Brief call with a technical recruiter and moved to the next round which was a technical screening. The question was straightforward and simple compared to some other interviews that I've had. I recommend an approach that used simple iteration to update state in order to solve the problem. However, the interviewer said that wouldn't work so I struggled to extract his implementation. Afterward, I went back and verified that my original solution did, in fact, solve the same problem and was less verbose. I'm not sure how to offer advice to other candidates as it seems thinking out loud may cost you.

Fairly standard interview process: call with recruiter, phone tech screen, in person interview. All technical questions were completely algorithmic; things you would find on leetcode. Considering this was a frontend interview, I find this tactic pretty silly. There wasn't a single question that involved anything frontend. Everyone was nice and the process went smoothly so can't complain about that.