The interview process involved two stages of technical questions, read from a list to prevent bias – a fairly standard approach. This was followed by a home working task.

Subsequently, there would have been a presentation, a team meet-and-greet, and a discussion with HR.

The first two stages took a couple of weeks to complete. I was then given a week to finish the home working task. This task was estimated to take 5 hours, but it actually required 10 hours to complete to a standard I was satisfied with. This was due to the need to create many components and my attempt to set up a mono-repo with a mini design system.

After submitting the task, it took nearly three weeks to receive a response. I found this delay and the subsequent lack of feedback disrespectful to candidates. They simply rejected without offering an opportunity to discuss the reasons. Having interviewed numerous candidates myself, I can recognize good quality code. I believe they ultimately have an issue with EmberJS bias. They are possibly the only large company using EmberJS for all their products, given its low number of weekly NPM installs. The project I submitted was 95% native web components and 5% EmberJS (which I had to learn). My intention was to demonstrate native web components being utilized with Ember. The only feedback I received was "EmberJS isn't his primary framework." This missed the point entirely; the app worked fine and addressed every requirement provided. It was very frustrating!

While I enjoyed the first couple of stages, the home task was a letdown. If you're going to ask candidates to spend five hours building something relatively detailed, the least you could do is spend fifteen minutes formulating some constructive feedback.

General topics on security, HTML, CSS, and JavaScript.

What upcoming features am I looking forward to? How does CORS work? What is the difference between const, let, and var? How do you copy objects? Describe the box model.