Well I might not be that Senior but if it's useful, here you go Focus on problem solving and not mastering frameworks and tools, no one cares if you remember the syntax or not. Some Competitive programming skills pays off later along with understanding what each and every line of code you write is doing as performance optimization, securtiy and scalability boils down to that. You are expected to write a better and descriptive code(design patterns -> scalability and modularization), security (knowing what you wrote or you won't be able to find out why a problem is happening) and there is a difference between knowing what a syntax does and knowing what's happening under the hood. Finally and the last important thing is "If your code is not tested, it just doesn't work". This is an old saying in the programming world and testind doesn't mean using your software and see if it crashes, It means writing unit, integration, end to end tests with a fully or a good code coverage might include UI testing and stuff of you are on the frontend side. If you go further it includes performance testing later load testing, spike testing.... etc. So practice writing tests for your code (test your code with another code😁). Check pit best practices for coding and architecting something and know why they are best practices. PLUS: Be cautious of Tutorial hell/loop and imposter syndrome.