Clipboard Senior Software Engineer interview questions

Had three coding rounds, which is a bit on the longer side, but each round was manageable and fun, while testing real-world programming abilities, instead of focusing on crazy algorithms and data structures, which you would never use on the job

A Complete Waste of Time! Immediately after submitting my application, I received an assignment via a platform called Woven, consisting of tasks I've detailed in the questions below. The assignment itself was straightforward. Notably, there was no human interaction until the first round of interviews, which was disappointing. Subsequently, I received a well-detailed document outlining their interview process—commendable clarity here. However, the process is excessively lengthy, entailing about seven rounds, including three coding interviews, one system design round, and discussions with various leadership roles up to an executive-level interview. The first round was marred by connectivity issues, and the interviewer seemed disinterested, which did not inspire confidence. One question involved Object-Oriented Programming (OOP), which was relatively simple. Although I admit to a minor error in my approach, the expectation to produce production-grade code within an hour, based on incomplete requirements, seemed unreasonable. In a professional setting, product specifications and engineering efforts are collaborative and clearly defined. If the intent is to mimic a realistic work environment, it should either be executed accurately or not attempted. This experience leaves me concerned that ambiguity in product requirements might be a regular issue at this company, and I consider my rejection a fortunate escape.