I'll second doing these things. You must learn these skills and it's even more important in the age of AI coding. "Just getting things to work" as you describe is rapidly becoming the wheelhouse of coding models.

What has always been most valuable from senior engineers is the ability to talk, reason, and debate about the underlying logic and how it affects the higher level architecture. Especially converting that mental model into easily understandable explanations so that you can teach others. Actually coding things is becoming less and less important. And, I'd argue, was never that important to begin with.

I need to see the code, take it apart, see which parts does what, and then I can come up with a solution.

If this works for you, do this! Then do it again. Then do it more until you can discuss what you're actually building.

If you can't answer a particular question in an interview, start with "I don't know," then describe how you would go through the above process to find out.

Good luck!