Asana Senior Software Engineer interview questions

Recruiter reached out to me. We started with an initial phone screen, then scheduled a technical call for the next week via the recruiting coordinator. After the technical call, they completely ghosted me. I tried following up 3 times with no response.

Unfortunately, I had one of the worst interviewing experiences I've ever had with Asana. I've heard nothing but great things for working there, but my interview experience says otherwise. First is a phone screen - cameras off. Odd, since they require cameras in the virtual onsites. Leetcode medium (leans easier). Then there are virtual onsites (7 hours). Overly long. Most of the interviewers were new to interviewing. I would ask about requirements/edge cases for a LC problem and they wouldn't know the answer, so their coach would unmute and provide the req. The new interviewers also got several reqs/answered my questions wrong, which needed to be corrected by both myself and the coaches. They tell you that there is both a "General Design" and a "General Systems Design" round, which, if the wording isn't confusing enough, the actual rounds are nothing like the vague descriptors they provide for the rounds. The final hour of the 7 rounds, the round that was attempting to be system design, was so anti-pattern for standard system design rounds. The problem statement was vague, which is standard, but when the interviewers were asked for baseline requirements , they wouldn't provide any, and appeared to be confusing themselves with their answers. I went on to ask if I may come up with the requirements myself, as that is typical for System Design when reqs aren't provided. They agreed that I should come up with the requirements, and agreed to said requirements. Then, I would begin designing the architecture, and they'd come through with new requirements that were in direct opposition with the requirements that we had just agreed to. This continued to happen over the course of the initial 25 minutes - we were circling and stalling over and over, just to get the requirements set. Reflecting on how bizarre this portion was, I almost wonder if the point of this round is to try to mimic a scenario where product/leadership goes back and forth on requirements/aggravates you to try to gauge how you handle and respond to said situation. I remained calm, but we didn't get anywhere with this round, despite System Design being one of my strongest interviewing suits, which was very frustrating for me. Please consider sticking to the industry interview standard - just ask your candidate how to design a social design app/gmail/etc. I'm sure I'm not the only talented candidate that slipped through due to the bizarreness of this round. Oh, they also require that you meet with a 45 min virtual lunch buddy in the middle of the 7 hours, instead of just giving you an hour break. I received feedback, which I was grateful for, but it was overall a scarring experience, to be honest, and I still feel unease with the interviewers. I don't think I would've accepted the offer, had I received it, due to concerns of the skill level of the engineers employed.