Fast Enterprises interview questions

Over the span of roughly a month and a half, I underwent two interviews. The first interview consisted mostly of behavioral questions, along with some queries about SQL and OOP concepts towards the end. These concepts should be quite basic if you're a CS or a related major. Despite my reservations about the process, they moved me forward to the second and final round of interviews. Regrettably, I discovered the soonest interview was a month away, which I found frustrating. I've seen similar complaints in other reviews, leading me to believe that they don't value or respect their candidates' time. For someone actively job hunting, a lot can transpire in a month. The second interview was two and a half hours long. It began with an administrative assistant explaining the process before introducing me to the experienced IC who conducted the interview. Before this introduction, I had to take a cognitive/IQ test akin to the online Wonderlic practice test, albeit a tad more challenging. The IC questioned me about my resume, asked me to demonstrate one of my coding projects, and inquired about agile/waterfall methodology. Following this, I had to write a function that checks if a number is prime and then print the first 100 prime numbers. He allowed me to do this in pseudocode or any programming language of my choice. The session concluded with a challenging brain teaser about 25 horses. I have several reasons for deeming this interview process negative. Firstly, it was excessively prolonged; a month and a half is simply too long. Secondly, I strongly believe their process is flawed. Is the aptitude of a candidate accurately judged by testing one's ability to find an anagram or do multiplication without a calculator during an IQ test, or to solve a riddle? It's worth noting, Fast Enterprises, that most of the riddle questions are posted online, allowing many candidates to feign ignorance to pass the interview. Unfortunately, I ended up wasting my time studying various riddles. Another concern was the absence of feedback after rejection. Despite asking for feedback twice, I was ignored. An interviewer's amiable demeanor doesn't compensate for the lack of communication and feedback, which are highly valued by candidates. While I might seem biased due to my disappointment at the swift rejection following hours of preparation, I must stress the current job market for CS grads is exceedingly challenging. Many people, myself included, would be willing to settle for a job that doesn't offer optimal career growth. If you're contemplating applying to this place or are already in the interview process, I advise caution. Even though the pay might be good, the experience may not contribute positively to your career. It might be better to start with a job that pays less but provides more valuable and transferable experience. They're offering above-market salaries for a reason: to make you work hard and keep you for as long as possible. While this isn't necessarily condemnable, you should carefully consider what you want from your career. Despite my bitterness about the rejection, especially as I felt confident about my performance, I believe I'll look back at this experience with relief. This place wouldn't have aligned with the career aspirations of a budding software engineer or developer.