The assignment was hard for me for a few reasons: There were many requirements; the requirements as stated were quite unclear to me; and it turned out that they were really referencing a certain standard solution to a standard problem that I was unfamiliar with. So we spent half the interview explaining the idea to me (bad!), and then the other half was me trying to code it up, and I just didn't get nearly far enough.
And imagine that the CRDTs are not directly explained in the problem statement, but some supporting data structure of CRDTs is referenced, and like clearly there is some way to make all the pieces referenced work together to create a working system, but it's never made explicit.
And imagine that you need to actually implement CRDTs from scratch in the interview, but also integrate them into this client-server document-editing app, which you also need to code from scratch. All in an hour.
This is why I say the interview felt kind of insane to me. But plausibly if I'd previously studied that problem, so that the implementation details were all clear to me from the start, and if I had used the company's coding assistant to the extent allowed, and if I had been in much better coding-things-from-scratch form, I could have done OK. I don't know. It's fine. They were probably looking for a type of engineer that I'm not. :')