Great advice. As someone who is on the self-taught path, and employed as of recently, I would recommend the following as well - Start digging into data structu

Great advice. As someone who is on the self-taught path, and employed as of recently, I would recommend the following as well - Start digging into data structures and algorithms early and often. Leetcode is meme status now, but it does help to practice routinely. Don't wait until 2 days before an interview to try to learn how to these things. Grokking Algorithims, the Algorithm Design Manual, and Cracking the Coding Interview all helped me out along with constant practice - assuming you'll be front end focus to break in, get a good understand of how the internet works (and be able to describe it well). It's a go-to interview question for front end positions - Dig deep into Javascript. Understand why it's useful, and more importantly, what the issues are with it so you can avoid those pitfalls when working with it. - Learn React. Vue/angular/etc are all helpful and good to know, but React is getting more widespread by the day. It's pretty easy to pick up once you have a good JS foundation, and there's tons of learning materials. - Learn about webpack and what it does. You don't need to know how to configure it from scratch or memorize its docs, but know when and why its used and how it helps your project. - Most importantly, learn how to get stuck. Try things that are really hard, get stuck until you want to give up, then try some more. Get comfortable not knowing how to do something, but figuring it out. - Don't get too bogged down learning the right tech stack. Pick one and go hard on it for most of your time learning. No matter where you end up, the stack will be different. Starting over is common and most places expect you to have 'ramp up' time to get used to their dev environment/stack