tldr -> A broken, confusing, very poor code challenge that seemingly stored none of my answers, being ghosted when asked if something had gone wrong, and generally a waste of time. The hiring process involves multiple steps, of which, I have not made past the first two, so I can not comment beyond that. However, the experience has not been positive at all compared to other similar. First step is to introduce oneself by answering a number of questions by email in regards to past experience and a self-assessment of skills, and the second one is to solve a coding test. I have never obtained any feedback on the first step, but the questions seemed relevant, and I believe they're reasonable as a first filtering option. The second step is, however is the worst technical test I've seen. This coding challenge was performed on a browser, under a timer and consisted of four categories of entirely multiple-choice question. You could go back and forth on each category of questions and redo your answers, however, you were disallowed from leaving the tab the test ran on or perform any browser actions. This was not a big deal as the questions were, quite frankly, a mixture of very introductory Node/React knowledge and some vaguely relevant stuff about Patterns. But I'm unsure what the goal of most the questions even was. For every single question aside from two (which I'll later touch on), you'd be presented with 4 options, all of which have nearly-duplicate 20 lines of code where the difference is frequently either a syntax error that has nothing to do with the supposed knowledge request, or it's something that requires no more and no less that simple memorization of implementation details anyone could resolve in 5 seconds of looking up the relevant task for. On the latter of these, I recall one very stupid example where you essentially got asked to know the props names for React.Suspense, but in the immediate, following question, you were given a working example of that JSX tag. So you could just go back. An highschooler with no coding knowledge could answer that one. Even with less egregious instances, such as questions about setting up express servers, require you to know the exact way you add the likes of morgan/body parser/cors/etc. as middleware, which end up being less about knowledge of middleware or express setup proper, but just a test of how little google-fu a developer uses, which is a pointless, if not, strictly detrimental ability... and only only one answer had the correct `app.use(cors())` line and no weird accompanying syntax errors, anyways, so all those other middleware functions end up, again, confusingly untested. Another weird thing was the ordering of questions. You are asked for specific knowledge about the likes of styled components (which I fully endorse btw) or linked state mixins. These are not inherent parts of a React Enviroment and I would not be surprised if a senior dev never encountered them while still deploying fully fledged commercial products. But I'm not trying to criticize the google-fu-ness of the question again. My concern is that these questions showed up prior to what could be considered "amateur filtering" questions such as ones asking essentially testing if you know what a React Hook is. Very basic questions, that a developer could learn to answer in less than a day, being placed not before but ahead of essentially, a third party library and a non-standard add-on. And even then, those questions did a fairly poor job of it, as both the useState and useEffect hooks surrounded the concept of incrementors/decrementors and ended up having, for example, bad import syntax as the elimination process. But even then we can be fair, and consider all so far as a test of attentiveness. But we can't excuse the broken questions. Because there were three or four questions which required looking at an image and have you either choose which answer produced the displayed result, or conversely, choose the result of the code in the picture. Which I couldn't see, as those images didn't load, and I could not side-load, as the browser would warn me if I tried to inspect the element. Mind you, there WAS a flagging mechanism for these questions, and I labeled one of them. I also cannot excuse factually wrong questions. The first question on Patterns asked us the following: "Which of these would be best to implement the Singleton pattern in JS". The given possible answers were Stacks, Arrays, Enums and Serialization. This got me stumped, so I wrote this down in my notebook and brought it up with JS developers, who were equally baffled by what goal could this question convey. All solutions we came up with looked like array hacks, and were in no way the correct way to guarantee single-instantiation. Even ChatGTP refused to answer without giving us a 5th, correct option with a class object. Another broken element occurred during the two questions that are not multiple question. They w
