Cloudability interview questions

HR person contacted me after I sent in my CV with an outlined process as follows: Resume screening Technical assignment Phone Screen - here we walk through your career history, we focus on each role, what you were hired to do, your experience there, and what you learned. In the case of a short work history, we will also examine technical projects or educational experiences. On site interview in our Portland office typically 5 hours. In each interview you will meet with multiple team members. The technical assignment was super easy. You just have to write a basic api with CRUD functionality that integrates with a JSON file for storage. Of course, this still takes time....2-3hrs in my case. I sent a github link of a 100% working and well written api (far from my first). Then crickets. I followed up three times. Silence each time. They are a complete waste of time. Obviously, there's loads of dev work out there. I'm kind of shocked that they are this disrespectful when they should be competing hard for quality candidates. I certainly wouldn't have wasted my free time building a pointless api for them if I'd known they were just gonna ignore that I even did it in the first place.

The first thing they do is send you an assignment. Not just a few coding problems that you can do under an hour, but a whole CRUD API project that would take a fast developer at least 2-3 hours to throw together. But if you need to do research will take much longer. Next is video interview with hiring manager and another engineer. They go through each company you worked at and ask you the same exact five questions: What's your biggest accomplishment, relationship with boss, why did you leave, etc. It was almost comical. Reminded me of the 90s style "what is your biggest weakness" interview questions that everyone makes fun of. So they are looking for people with good presentations skills - not creative dev skills. I got rejection email day later, but I knew that I failed before that. I tend to concentrate on negative things too much, but that's what makes me a good developer! The whole process felt very bureaucratic, formal and lazy. The experience left me with a negative feeling, but it is very unlikely that I would have joined anyway. I just regret wasting a good part of weekend on that silly project. Seems like they missed the whole flat organization movement are looking for followers instead of creative devs that take ownership.