Didn't move past the phone screen. Just like others mentioned, the screen consisted of a multi-part question with a very long description. New parts were revealed after solving the previous ones.

I'm encouraged to do thorough unit testing, but don't fall for it! It will take time away from solving all parts, which is the key task. Just use the example test cases and move on.

The initial two parts were really basic. Part 3 was a bit more involved but still not about LC-style algorithms. By the time I reached part 3, there was barely any time left to code it, so the interviewer asked me to verbalize the approach.

I did, but in hindsight, I was so rushed reading the problem statement for this part that I misunderstood bits and didn't have the approach 100% clear.

Picking Go as the language definitely didn't help because of its verbosity. The interviewer was very friendly. I'm not entirely sure this approach is better than LC, though, as it heavily prioritizes speed over thoughtfulness.

Involved string parsing and easy array manipulations.