I wish I would have read the reviews on here first. I've been in the industry a long time and have been through many interviews, and I've never quite seen something like this. Apply, get an immediate response that I am within the top 10% of interviewers, a video and a phone number to call them at. Take two tests, one IQ / aptitude (I really don't know what it is), and one dated, and opinionated, frontend test. They find these two to "be the best use of everyone's time". The former was a combination of pattern matching, English / grammar, some sort of "clerical matching", and some short story form math problems. As to the latter, the questions that are "most" true or false, and yet some are bit ambiguous. These were _awfully_ worded, a total mouthful, but not all awful questions in content. Some dated, not as relevant though. Topics range from CSS box model to security to XMLHttpReqest vs. fetch, to Babel. Because Babel is "the most widely adopted transpiler for JavaScript applications". Maybe historically, not so much anymore. The cognitive test is particularly concerning to me. I suspect there are many smart and very good engineers who would “fail” this test in some category. The details of “Clerical matching” is just not what I connect to some of the best engineers I’ve worked with. It will be difficult for someone less proficient in English as well. I’d be pretty curious to see the “profile” of a successful files.com engineer — based on this upfront hiring process, I suspect once I’ve seen one I might have seen them all.

TL/DR Like others have said, the interviewer is fairly rude and hardly someone i'd want to work with. The process was mainly javascript questions in which I feel like I answered 27/30~ correctly. The interviewer made a lot of assumptions regarding my resume instead of just focusing on the interview itself. Most of the questions are just questions you can just google so I don't see how this properly assesses how good anyone is. Even though this job involves Redux I gave them a story of my experience of why I used something else and he felt personally offended although he even agreed that Redux is a ton of boilerplate lol. Conclusion: - future interviewers: I'd suggest googling javascript interview questions, some off the top of my head are, closures, currying, localstorage, sessionstorage, promises, async await, generators. This interview was literally as if you're a glossary lmao. - to people at files.com: I'm sure the smart people of files.com can come up with a better interview process to not lose potential talent, also find a better person to hold the interviews, someone more personable would be great.