TL;DR: Rollercoaster interview that took place over about a month. Employees seemed happy and were friendly. Don't be nervous, and do take things with a grain of salt from everyone but the final decision-maker. Would I apply there again? Almost certainly.

Based upon questions asked, I do not believe this is a company that pigeonholes or sticks you in positions without figuring out where you'd be most gifted. This was a Front End (Entry) Software Eng. position, and I was asked all sorts of backend, comp sci, data science, and UX/UI questions.

Applied online and got a call almost immediately from the recruiter, who said they thought I'd be an amazing fit. Ended up doing the behavioral interview/screening right then. The recruiter was bubbly and candid and said they'd fast-track my application because of how great I fit into the position. I think there was an online technical screening test before this stage.

Onto the technical interview with the person who'd be my engineering manager. For perspective, this was my dream company for many reasons and my first technical interview via video. I had a nearly debilitating mixture of imposter syndrome and hope/wishful thinking. The questions asked were not immensely difficult, but they threw me off because they were not what I was expecting. I didn't do great, but I did ask if I could redo them afterwards because I knew I could at least get 90% of every question right. I got reconsidered and was sent a timed "take-home assignment" that was more rigorous than expected for an entry-level position (later confirmed that suspicion with senior-level engineers). I learned everything I could about it then absolutely nailed it.

Got flown out for an onsite. Four or five interviews with pretty average difficulty, and I got the impression that I'd nailed all but one. Left feeling very confident and was told I'd have an offer letter within the week.

Nearly two weeks later, I got a call saying I had all but one yes (unanimous vote to hire). Apparently, there was "too much discrepancy" between the first technical interview and the take-home assessment.

Best and worst case O(n) for search for a linked list, hash table, balanced binary tree, etc?

Flatten an array with the array as argument, returning the flattened version. No global variables, and will be tested on deeply nested arrays (that's the part I messed up).

Recreate an entire filesystem (deeply nested, of course) using React that is searchable and collapsible.

Static typechecking, Flux, MVC, database schemas, mapping objects, etc.