The process isn't too onerous, starts with a recruiter screening and then a technical screening. The technical screening entails some basic JavaScript problem solving and some technical questions about React and JavaScript. Felt more about the conversation than the technical skills. Following this is a three-hour onsite with two technicals and a behavioral chat with the hiring manager/director. The technicals are with two engineers each so you meet four engineers in total. I found the engineers to be incredibly awkward and made the process feel thoroughly uncomfortable. I'm not sure if they just don't have much experience interviewing or the company's engineering culture is just like this, but this was the worst part of the whole process for me and it has nothing to do with the technicals' difficulty. The first technical is to create a skeleton surveymonkey page from scratch interacting with a mock API. You will have a design to work off of. This is where I felt the process let me down as the engineers informed me that CSS and styling did not matter, and that solving the technical problem was the core focus. Well do not listen to them, as this was not true. In their rejection feedback they stated the main reason was that my CSS knowledge was weak. Perhaps it was another reason but it's incredibly frustrating if that was their actual reason after explicitly telling me that styling doesn't matter. Time is already tight in this technical challenge but make sure to allocate some time at the end to style things or else you too will get rejected for not adding borders to a card. The second technical is a systems design challenge using a virtual whiteboard. This was excruciating and incredibly vague, but not difficult. You will spend most of your time asking questions and clarifications because the 'system' in question is so loosely described. The engineers at this point were also very awkward and stilted, making the process much more painful than it needs to be. Again though, it was not very difficult and after wrestling with the interviewers it seemed to mostly be about data structures. The behavioral interview was positive though and gave me some hope. It was a one hour chat with the hiring manager and director, comprising pretty standard questions but in a free flow and casual conversation. I really enjoyed this part so I would have some hope for the leadership in any case. Summary: technical challenges are not hard but poorly explained. make sure to cover all your bases in the coding challenge and ignore any directions from the engineers as they are setting you up to fail for some reason. in the systems design make sure to ask as many questions as you can at the beginning before diving in as you will start and stop constantly due to poorly communicated problems. just be yourself in the behavioral and treat it like a normal conversation. Side-note: they mentioned during the interviews that the company had gone through multiple rounds of layoffs after being purchased by private equity, and they were not 100% sure the layoffs were over. if your aim is job security this may be too much of a risk for you.