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.

English Version (Glassdoor Review Style) I applied for this role in mid-December and received an email in early January informing me that I had passed the resume screening stage and would be invited to complete an online test. The online test was not LeetCode-style and was more focused on practical problem-solving. The first task involved using Axios to fetch data from a URL and return the result based on specific rules. The second task was a front-end exercise where I needed to sort a list of items based on one of their properties. The second stage also included recording a Loom video, where I was asked to explain one of my projects and how I approached and solved the problems. Both of these stages went smoothly, and I received timely and helpful feedback. The third stage was a technical interview. In the invitation email, I was informed that I would be interviewed by a team member and should have my IDE ready. This stage involved pair programming. I was given a LeetCode-style problem from GitHub, which I needed to clone and solve locally. The problem itself was not very difficult and was relatively simpler compared to the earlier stages. It involved mapping numbers to text. However, I was not able to complete it within the allocated time. After the coding exercise, I was asked some general questions, such as my daily development workflow, an introduction to myself, and details about the team size and structure. Around the day after the third-stage interview, I received an email informing me that I was unsuccessful. I believe this was mainly because I was not able to complete the coding task within the given time.