Emerald Cloud Lab interview questions

Started with a phone screen. The recruiter I had as my POC was amazing. She was super kind and always great at answering any questions I had. Next there was a take home exam, to sort a JSON formatted file with large amounts of data. Then if they liked your answer, you would go on to a round with two engineers who would do code review. Go through your thought process and mention where you could add optimizations, also what the space complexity is. Although the take home was long and tedious for such early stages of the interview process I liked how they were there to give you feed back and did a good job on guiding you with hints to get to the answer on your own. Then the final onsite. This was 5 parts and where things went down hill. 1.Scientific Design, This was where you meet with a scientist and visual designer and go over some feature prompts and ask questions. This was very disorganized, The scientist was supposed to show up first and then 20 min in the designer was going to join in. No one showed up to the interview for the first 23 min, with no email updates on being late. When the designer came in she was frazzled as she was expecting the scientist to already be there answering questions and giving me the prompt. Due to the meeting starting late, there were no intros, no explanations of what we were doing and was kinda just thrown into reading the prompt and then being confused on if they wanted me todo with these fake feature requirements. This meeting ran late as the scientist eventually showed up around the 35 min mark (10 min before it ended). It was also frustrating as the other interviews build off this initial. 2.Technical Design. Then the technical design interview, this was verbal based on the prompt from before. They asked questions about how I would build a feature from the prompt. At times the questions weren't clear and it was difficult to figure out what they were asking. There were also clear indicators of toxic company culture in my opinion. 3.White Boarding. This was just not white boarding, it was algorithms in a IDE of your choice. I think they should have provided a environment or indicated to set one up before. It also shows a level of unprepared unprofessionalism in my opinion when you hop in a interview and the company isn't willing to pay for a interviewing IDE. I also wish they had noted this wasn't going to be white boarding as there were no space to draw anything out and I prepared accordingly. There were also some small red flags for me about the company culture. At this point I was considering pulling out of the interview process as I wasn't sure I would accept a offer if they extended one, but decided to just finish it up. 4.Pixel Perfect. I have never had a pixel perfect interview before, and it makes sense why. They showed you a bunch of pictures and it was essentially spot the difference. This wasn't the best set up in my opinion as the wire frame and the real version had completely different data so it was hard to tell what differences they wanted you to point out and which were just the headers, and what where specific titles based on the data. Also I didn't feel like this interview really had significant value, but to each their own. 5.culture fit and behavioral. Again just disorganized, the interviewer was late, there were a few different people peeping their heads into the interviewers room periodically through the 30 min meeting. There were some other small red flags here for me personally. All in all it was a very lengthy process that I think could have been reduced down. There seemed like there was a lack of internal communication and disorganization. Its a big bummer as I thought they had a really great product, but that doesn't make up for the major red flags I saw while interviewing. Also was a very long process to interview for this role, and wasn't worth spending that much time when they didn't come prepared.