Preguntas de entrevista de Mathspace

In my many years in the industry, I have never encountered a more chaotic, unethical, and disrespectful interview process. The interviewer was 20 minutes late, had no idea who I was, and hadn’t even reviewed my design challenge. There was zero transparency about the interview stages or what they expected at each step. They assigned an unnecessarily complex design challenge centered around their product issues—clearly fishing for free work. After reaching the final stage, they lacked the basic courtesy to provide any feedback or outcome. In hindsight, not getting the role feels like dodging a massive bullet. (A missile)

The interview process consisted of three stages. The first stage was a technical interview with the CTO, Alvin, and another employee. The initial 15 minutes were dedicated to Alvin explaining the role and the company, followed by an opportunity to ask questions. Afterward, they asked several questions about React hooks, the differences between const, let, and var, and requested that I discuss a technical feature I had implemented in React, including the challenges faced and how I resolved them. The second stage was a take-home test involving an interactive histogram. In the third stage, I met with two developers, Greg and Kerrin. The first part involved discussing the technical test, focusing on how to improve it, similar to a code review. They had identified some bugs, and I needed to figure out how to fix them. The second part was a live coding challenge, which involved three React scenarios: the event loop, object comparison, and mapping lists.