I had my first coding test for an interview recently (second dev job but a decade of other experience), over a video call, shared screen in a pre built AWS in b

I had my first coding test for an interview recently (second dev job but a decade of other experience), over a video call, shared screen in a pre built AWS in browser IDE and I assumed I tanked it because it didn’t go perfectly. In hindsight it went like a typical 40 minutes of coding, I started down a path, didn’t quite work, had to console log to see what was up, tried a new tact and then it worked. They were clearly looking to make sure I had some basics of Angular down but also that I could problem solve in the moment and see where I went wrong. I enjoy interviews (I like meeting people and chatting about their projects and problems) and I think running a VC backed company for nearly a decade has set me up well for detaching my performance in the interview to my self worth/abilities (ie. I’ve grown a pretty thick skin). Ultimately it comes down to “can I do the job?” and “is their process set up to accurately reflect that?”. If the answer to the first is no then that’s cool, I’d probably have a miserable time in the role and under perform even to my actual level. If the answer to number two is no then I probably don’t want to work for them anyway as they are unable to accurately measure and analyse prospects/opportunities beyond just hiring.