REXA interview questions

The interview process was the following 1) Phone Screening - HR and Manager 2) In person Interview - Two people interviewed. The first onsite interview was with the manager and then a team member. Walk through the facility - factory and the R&D section

Spent 8 disorganized hours total onsite between first and second visits. First red flag to the state of the tech at this company was I had to manually fill out the voluntary disclosure forms on paper (are you a veteran, disabilities, etc.) Had a technical coding question that the interviewer wouldn’t let me actually work on because they kept talking over me the entire time. They handed me 16 pages of unstapled design specifications for their actual microcontrollers (once I saw his disorganization I asked him if we could keep the double sided non-numbered pages together but he seemed to ignore me and very quickly we had these sheets strewn across the table), they had trouble sorting out the actual question they wanted me to answer, and at the end I think I really was just doing their work for them. Again, they really just talked at me about “how they would approach it” when it was just the most scattered, loosely constructed problem that I was still somehow able to find the solution, but it didn’t have to be as hard as the interviewer was making it, and I would not want to work at a place that vets their coders in such in terrible way. I could not imagine working with the interviewer in a professional collaborative setting. I established pretty early in the first visit that I don’t have professional hardware experience, my specialization was in developing drivers and software, and we seemed in agreement that the roles responsibilities were flexible and that software would be my focus. 8th hour of the process they show me PCU schematics and act frustrated that I am unsure of how to read it. “Passed” the pseudoscience personality test between the first and second visits. Ended the process with a tour where the same interviewer as before insulted the QA in the factory by calling their work red neck engineering (compared to automated testing we were discussing).