I conducted coding interviews for a few years at a startup before moving to a bigger company where I had a smaller role.

For me, I never cared about if someone got the right answer. I have actually said no to people who got the right answer and yes to people who got the wrong answer (or didn’t finish). The purpose of the interview is to see if I want to work with that person. If someone can write a perfect program, but can’t tell me why it works, that gives me no insight into how they solve problems or if they even know how to solve problems. What I want to hear is their thought process.

First repeat the question, and emphasize the key details. Speak an example input and output of the function so the interviewer (and you!) knows you understand the problem. Then start talking about what kind of algorithms or data structures you might use to solve this problem. Reference other common problems that might be similar, and how they differ. Specify patterns that could be used for this problem or even your comparison problem, and whether or not that will work for this one.

Doing all of these steps with spoken words helps your interviewer understand how you think, and they may give away hints to mistakes in your thought process, or even point out that you are misunderstanding the question entirely. And that’s okay! It’s better to work out the details when speaking about it before writing any code.

Treat the interview like you are solving a problem with a colleage in pair programming. Bounce ideas off them and see what they think. They are very likely to give hints if you talk to them in this way. If you are stuck, tell them! They might be able to reword a part of the question to help you think about the problem in a different way, leading you towards the solution.

AFTER you and the interviewer are both confident that you understand the problem, and you have discussed all the algorithms, data structures, patterns, etc. that you need, maybe spoken through a some pseudocode, or maybe written down a table of example inputs and outputs, only then start coding.

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?

Have a spare laptop/desktop that you can use to lookup answers quickly.

Coding tests are there to present problems from the computer science side of things and rank people on how well they are able to solve them. The whole point is to judge applicants on their understanding of the knowledge they would have gained in university programs. Universities became accreditation factories during a boom in programming and technology hiring and employers needed some way to filter people who just skated by.

You are failing them because you don’t have or cannot express formal training.

Short term, cheat. Use a second computer and look shit up, form an llc and register on all the test websites (they often have free trials just like anything else) so you can send dummy applicants to learn their tests, etc.

Long term, audit some of the many university programs available online up past the 200 level.

One of the examples in this thread looks like the calculator problem (I might be wrong, it’s been 25 years!). They say “you can’t use these libraries, write a pocket calculator, no ui required” and provide a picture of a pocket calculator as the reference. The student is supposed to learn that even stuff that they thought was simple isn’t and that their language has unique quirks that many libraries work around.

Someone who solved this in 102 would crack their knuckles and knock it out. Someone who never had to do something so inane would find it very hard.

May or may not be a formality. Take it and don’t sweat it. What’s the worst that will happen? It’ll rip your leg off?

Before I go looking for non-obvious answers for you, why is the obvious answer not working for you?