TPS. Solved the problem in probably 20-25 mins. Rest of the time was spent "optimizing" the solution to cater really smart, rude and naive interviewer. Instead of focusing on how to improve space complexity or algorithm itself, I think they are focusing on how good artsy data structure(s) you can come up with. (Interviewer hints to use a hashmap of lambda functions is easier to use over plain simple pattern matching). This is is termed as "collaborative" engineering culture I guess. Be aware!

Recruiter Screen asked typical intake questions. They were friendly and generally easy to speak with. However, they constantly deflected and refused to answer questions regarding budgeted salary ranges for the role, which is required in WA state. The Job description did not include these ranges either. A few hours later received the standard rejection email.