What do Python coding rounds in interviews actually test?
They test four things, and only one of them is whether you can write code. The earlier questions in this topic covered the individual tools, so this answer is about what the interviewer is really looking for while you use them.
The first thing is problem decomposition. Can you restate the problem in your own words, identify the inputs and the outputs, and see that it is a smaller version of a problem you already know how to solve? Candidates who jump straight into code are usually the ones who solve the wrong problem for the first fifteen minutes, and then they have to throw all of it away.
The second thing is the choice of data structure. Which container are you going to use, and why? A list versus a dictionary versus a set is often the entire difference between an O(n squared) solution and an O(n) solution, and being able to justify the choice out loud is the whole point.
The third thing is the handling of edge cases. Empty input, a single element, duplicates, negative numbers, very large values, and the boundary between two states are where most solutions break. Interviewers will often hand you an empty list on purpose, simply to see what you do.
The fourth thing is communication. Narrating your approach, saying what you are about to do before you do it, and stating your complexity as you go are all part of what is being assessed. A quiet candidate who writes correct code can still be marked down, while a candidate who thinks out loud and gets it slightly wrong usually is not.
What is not tested is syntax trivia or obscure built-in functions. Nobody has ever been rejected for not remembering the argument order of a rarely used function. The Python that matters in a coding round is the Python you use every day, which means lists, dictionaries, sets, strings, loops, and comprehensions.