My background is more on the design side, but I helped recruit and manage some front end devs over a few years.
When we were recruiting, we wanted to see a portfolio demonstrating the candidate's knowledge and problem solving abilities. A candidate with a portfolio that featured a range of pieces of work (explaining how they solved various development problems and what they learnt) was a big thumbs up from our perspective. Unfortunately we received quite a lot of applications which said things like 'confident in CSS' but when you receive loads of those there's no real way of telling them apart. The portfolio is your key there because you can actually demonstrate what you can do.
As for learning, there are loads of really good free courses out there. If you're starting at the beginning, Codecademy is a good place.
When we were recruiting, we wanted to see a portfolio demonstrating the candidate's knowledge and problem solving abilities. A candidate with a portfolio that featured a range of pieces of work (explaining how they solved various development problems and what they learnt) was a big thumbs up from our perspective. Unfortunately we received quite a lot of applications which said things like 'confident in CSS' but when you receive loads of those there's no real way of telling them apart. The portfolio is your key there because you can actually demonstrate what you can do.
As for learning, there are loads of really good free courses out there. If you're starting at the beginning, Codecademy is a good place.