Domain Group Senior JavaScript Engineer interview questions
based on 1 rating - Updated 4 Sept 2020
Easyinterview difficulty
Very negativeinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
1 interviews
Domain Group interviews FAQs
Candidates applying for Senior JavaScript Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Domain Group overall takes an average of 21 days.
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Domain Group (Sydney) in Aug 2020
Interview
Before I describe the interview process, let me advise you this: Don't waste your invaluable time by completing their take-home coding test. They don't value the work at all. If you want a fair interview process, then Domain is definitely not worth a try. Don't get me wrong, I prefer take-home-project interviews any time to the useless white-board style interviews. But, unfortunately, Domain don't know how to execute this interview model correctly.
The interview process itself was easy. It has 4 stages:
1. Phone screen with a recruiter
2. Non-technical interview with a manager
3. Take-home project
4. Final interview to discuss the project + technical interview
I had pleasant experience with the first 3 rounds. The problem started during the 4th stage. One of the vital interviewer didn't show up and I was not informed about that. The interview went ahead anyways. Although I was a bit sceptical about it, I decided to continue.
The remaining 2 recruiters seemed to be completely unaware of what was asked in the take-home project intructions. They asked why didn't I write unit tests for the project. I told them that the "requirements" section in the project instructions didn't list to write unit tests, and that it required me to only spend 4-5 hours for the entire development process. I also clarified them that the requirements are complex enough to take up the whole 5 hours time frame. They sounded as though they were convinced by my answer.
And then after awhile, annoyingly, they asked why didn't I use any state-management library. I clarified them (again) that there was no mention of such requirement and the project itself was too simple to use state-management libraries. I then screen-shared them to show how I used other libraries to handle form validation, styling the components, etc. Again, they seemed to be convinced. And the interview completed after a few questions about JavaScript concepts.
The judgement day arrived. The recruiter called me and said that they were happy to offer me a job, but, it's gonna be for a mid-level role and not for the senior-level role I originally applied for. The reasoning I heard was really absurd. They said I failed to demonstrate the required skills like "state managent", "writing unit tests", and "application architecture". No comments to the state management, and the unit tests part but "application architecture? Seriously? I swear, I was never asked a single question about that at all. I just learnt a lesson. Before spending time on developing take-home projects, I should first research a bit about the quality of the interview from that company.
Interview questions [1]
Question 1
You'll ace the technical interview if you memorized whatever page that shows up after googling like "Basic JavaScript & React Interview Questions" (yep, it's how naive their interview is).
Try to use any of the state management libraries like Redux or Mobx. They won't mention that in the so-called "Requirements" section. But you are expected to use that. Also, write some unit tests, and end-to-end tests. Again, they will not mention that, but somehow they will expect you to write them. Note: The ridiculous thing is, whatever mentioned in the "requirements" section will be ignored by them!