You can explore a few things - front-end development using some in-demand libraries/frameworks - react, flutter, etc. Most front-end applications, especially web ones, require Javascript, HTML, and CSS. Backend anything would work - Flask, Django for Python, JavaScript for NodeJS, or any other language for the backend - each language has many good frameworks and libraries. So having an experience of all these is quite helpful.

Then you can also try to learn some DevOps - Docker, CI/CD tools, Kubernetes for deployment cloud tools and services - AWS, GCP, Azure, etc. These are some of the things having exposure to which would undoubtedly help you in bagging software-based roles.

But this is not an exhaustive list by any means - there are way too many other things as well that you can learn and implement. So, an excellent way to learn these things is by building some software. Maybe take up something you find calm and make software for it.

You may also learn app development/game development; you need not stick to web development only.

There is no rule that you must know this and this, and you'll be done. But they do expect that you know how to learn stuff on the go, learn things by yourself, find solutions to bugs and errors, find workarounds, use resources like Google, Stack Exchange, and GitHub properly, go through documentation and understand stuff, can install the dependencies on your own etc. And these skills cannot be taught.

They have to be learnt from the experience alone. Knowledge of version control is a plus, and it is taken for granted when you're applying for software roles.
Having a solid grasp on competitive coding is a requirement - as that helps recruiters evaluate you on two aspects - your problem-solving and thinking skills and your coding skills, especially keeping efficiency in mind.

You understand information workflows, RESTful APIs, and good soft practices - such as keeping the code modular, properly documenting your code, etc.

Following standards set by the workplace where you're working, testing the code - unit testing, functional testing, stress testing, A/B testing, etc; all these things are good to know.

It might not be possible to know all of these, nor is it recommended to know all at once. These things are meant to be learnt gradually.

Similarly, you can explore other fields, such as web3 and AI/ML, and start applying.