I had coding and k8s tests before my current role. As they role is platform engineering, it may not be quite the same as if you’re going for an actual coding job, but - it was open book, and you could pick your language - they weren’t trying to test “do you know [language]”, they were trying to test your analytical and thinking skills.
The only part of it I remember now (vaguely) was something about flipping a coin. It wasn’t actually a coding test so much as a logic and problem solving test. The only thing I actually brought to the table was knowing most languages have a modulo function and how to make use of one for various thing (from experience, I’ve never actually been formally taught any coding), and I basically then Googled the pieces to put it together. They know that’s what you’re going to do on the job anyway, as literally everyone does, so why keep you from doing it in an interview?
100% agree on “car” and came to the comments with it in mind.
As much as it sits unused the majority of the time though, that isn’t what I was thinking - what I was thinking is how I’ve never get to “fully use” it, or any sports car I’ve owned for that matter, as to me fully using it would entail bringing it to a track, REALLY putting it through it’s paces, and pushing it to the limits it was actually designed for. While it is great fun to drive (safely) around town, and comfort and luxury were absolutely large parts of the engineering that went into it, it’s hardly living up to it’s full potential!