IDX Senior UI Developer interview questions

I want to be as transparent as possible. Other engineering applicants should be aware of what they can expect from the ID Experts interview process. I applied for a UI Developer job. A recruiter turned me onto the job and sent in my resume. The hiring manager Matt was excited to talk so I scheduled some time. I had a non technical phone interview that went very well. He asked me to complete a take home code test that weekend, mentioning it would only take about 45 minutes. He stressed not to take long as they weren't paying me yet. He also said that the code test was a way to guide in person interview questions. I pulled the repository down from GitHub and read the instructions. It was a very simple test. Complete an Angular component with routing, calling for mock JSON data, and rendering it, all within about an hour. Let me begin by stating that a senior developer should not over solve everything. There is beauty and skill in simplicity, performance, and code readability. I solved their puzzle with relative ease and with good use of modern Angular concepts by doing the following: Lazy loading a new module using the Angular router Creating an injectable service class that uses abstraction to keep all web request logic decoupled from components Coding to interfaces not concrete implementations Using dependency injection for the service into the component Subscribing to an RxJS observable when calling for data Using Angular life cycle hooks to get data and avoid common rendering issues Using SASS and basic concepts like variables Creating Angular animations with trigger, state, and animate I waited nervously to hear back for the rest of the weekend and most of Monday. Eventually the recruiter got back to me and it wasn't good. He said that the manager had concerns over a few things in my solution and they didn't want to proceed with an in person interview. No feedback was provided, nothing specific, no thank you for your time. This was very disrespectful and shows something about the culture of the department. This is important. I don't want to work for people who don't encourage growth. Where feedback is not provided and mistakes are seen as a bad thing. If we don't make mistakes as people, we don't grow. In a way, I'm glad that I learned this before moving my career and life here. BTW. Before I submitted my solution I double checked my code against Google's latest Angular documentation for accuracy. As developers we know that there are people who are scared of competition and others who can't see a solution outside of their own. I'm afraid I came up against this during my interview. Hell, maybe they wanted me to spend 4 hrs and they only said 1 hr to throw me off. Who knows. Either way, I wish you better luck if you choose to apply.