Sitemate interview questions

Way too many stages for a junior-level role. Initial stages are extremely time consuming (lots of repetitive questions about information that is already in your resume) before even getting in front of someone for an interview. Seems like no one wants to take accountability during the hiring process and so they involve 6 levels of management before someone feels comfortable making a decision. The convoluted process doesn't take into account people's time and the effort that goes into the application just to potentially be wasted.

The job I applied for turned out to not be a specific vacancy but instead a generic vacancy / ghost job so Sitemate can build a candidate pool to pick from. This is similar to how big tech companies operate. They used a lengthy multi-round process: 1. Extensive job application form with many questions 2. Record and submit a 2 minute video 3. HackerRank test with 2 questions 4. Technical interview I was rejected after the technical interview with feedback that I needed to show more depth when working through the ambiguous problem space, and also advocate for improvements to the existing code. Like many other companies, they weren't transparent up-front about their assessment criteria, so I didn't correctly guess which skills to demonstrate during the limited time available for the live coding interview ("pair programming"). Also, I picked up some important info during the interview: 1. They used JavaScript, not TypeScript, in both coding challenges (HackerRank + technical interview). This could be a sign that they don't use TypeScript, which could be painful if you prefer TypeScript. 2. They use VS Code instead of a fully featured IDE, which could also be painful if you're used to a more productive and rich IDE like WebStorm.