I received a coding challenge two days after applying. I did well on it and received a non-technical phone screen with the recruiter. After that phone screen, I received and email stating that I did not get an offer because I did not have enough experience.

Began with typical HR phone call, followed up with project submission. Afterwards I was invited for technical video/codepen interviews. After 2 1-on-1 technical interviews about basic JS concepts (at this point we are 3 weeks in the interview process) they invited me onsite but then withdrew this due to employees unavailability. Instead they give me 2 more technical 2-on-1 technical screens (not sure why there are two people this time as this definitely did not contribute to the call but instead made it much more awkward) to which they then decline. Seems like they had filled the role and were looking for excuses. Also was not provided feedback as well

Interviewer asked many textbook Javascript questions. When I say textbook, I mean you must answer them all textbook style. Step by step, chapter by chapter. That's how you get the position. No experience or knowledge, but being able to answer Javascript textbook questions. The fundamentals and concepts are important and they build the founding blocks but to a certain degree, they don't help much anymore because we built tools to deal with those problems and we stopped thinking about them. Instead, attention is diverted to newer challenges. Quizzing people on old challenges doesn't help. It's like asking a fireman to put out fire but not letting them use a firehose. They're only allowed to use the old fashion way, which would be carrying buckets of water from a nearby water source. My mind is worrying more about how to deal with async instead of call back scoping problems. I haven't had to deal with Callback hell because I'm not an idiot who writes in that pattern. It's people like these that really kill the motivations of being an engineer. Taking all the fun of learning and keeping up to date with tools. Do you know how many senior engineers don't know http/https? Or can even explain how the browser works from start to end?