Loom interview questions

My journey interviewing at Loom started promising. The initial conversations with the hiring manager were insightful, and the first coding challenge was conducted professionally and with very clear requirements. The first few interviews made me feel excited to continue and contribute to the Loom team, however as I later progressed through 5.5 hours of interviews across multiple days, the atmosphere took a noticeable turn for the worse. Half way through, the experience began to feel like I was in a hot-seat facing rapid-fire questions rather than a meaningful discussion to evaluate my fit for the roles. By the final interview, questions ventured into uncomfortably specific details, such as the names of people involved in past conflicts. I was even asked to recall the KPIs met, and not met, on a particular project from years ago. Notably absent were questions about my years of career experience, career aspirations, working style, or specific expertise relevant to the roles I was interviewing for. Personally, it felt as if the process was designed to test stress management rather than to get to know candidates. Ultimately, after investing significant time and effort, the rejection message I received was disappointingly brief and impersonal, offering neither feedback nor future considerations. Overall, my experience felt that Loom could benefit from revising their interview experience to be more respectful and informative for candidates.