Great point by Teller, but I would expand on it.
My feedback is on the fact that you seem focused on a specific set of technical skills as the way to get a job. I have two responses:
Response #1 - There is a huge diversity of skills throughout the tech world, and the ones that are in demand can vary by your location.
So what can you do? The only way to know your local job market is to interact with other developers personally. It’s a great start to ask questions on a forum, but the best thing to do is to ask these same questions to hundreds of other developers at local meetups (and conferences, and online too). And the very best time for you to start doing so is now, at the start of this year of learning, before you are actively (and perhaps desperately) looking for a job.
The answers you get to your questions should shape the course of your technical learning over the year as well. There are some cities that still have a huge demand for Java, or for .NET, and if you’re in one of those cities, you should probably change your focus from something like NodeJS or Python.
The answers to your questions should challenge all of your assumptions. If you asked me for advice at a meetup and told me you want to be a back-end developer, I would tell you that in my experience, there are fewer and fewer pure back-end roles on the market. My team recently hired someone for the back end, but the job was called Full Stack Developer (back end focus) because we needed someone who could work on the front end if needed. Of course, I’m just one person, and I haven’t studied the broader job market, and I don’t know if things are different in your area. That’s why you should talk to hundreds if not thousands of developers in your job market over the next year.
Response #2 - Pure technical skill is unlikely to get you your first job.
A lot of developers (myself included) start out with an assumption that pure technical skills will qualify you for a job, and thus the way to separate yourself from the competition is to hole up on a bedroom, basement, or maybe a series of coffee shops, and achieve technical superiority by out-working other people (and maybe Leet-coding your eyeball out too). Even if this does not lead to burn out, it often leads to social isolation, which is the opposite of what will actually help you on the job market.
What you really need on the job market is to know people who can recommend you personally. If you have spent a year meeting developers and discussing what you’re learning and making, those are the people who can recommend you to be considered for an interview. At this point, the interviewers may (or may not) look at the projects in your portfolio, and they may (or may not) give you a technical interview. On the strength of a personal recommendation from another developer, the interview may be just a behavioral interview to check if you are a good fit for the team.