A common phrase my colleagues often hear out of me goes something like this: "The two greatest works of 21st century fiction are technical job descriptions and

A common phrase my colleagues often hear out of me goes something like this: "The two greatest works of 21st century fiction are technical job descriptions and the resumes that were written to match those descriptions." A high percentage of the time they aren't looking for all of those skills at all, and sometimes none of those skills at all. They just hope that description will attract resumes. They have cast a wide net and are looking to see what they will catch. I put out an "intern" level job description about 5 years ago now. At first I put down the bare minimum skills we needed. We were not only willing to train but expected we would have to, so the description was little more than "Good personality", "desire to learn to develop software", "can type", things like that. We got zero response. So I added in more and more things until I had a wide enough net to get the right person. We hired a person who had two years of school under his belt and hadn't worked in a professional development position at all. He had no idea how to develop and was scared to death that he didn't have the skills we needed! We convinced him it would be fine and we would train him. He did a lot of learning on his own after he took the job and we did a lot of helping him with training. He didn't make much but he learned a lot. Fast forward 5 years and now he's quite an adept engineer and works consulting in the DevOps area of things, doing exceptionally well (better than many of the people who trained him!). A few take aways for you: First, don't try to learn everything in a job description before going in for an interview. You might find that they don't really want all of that stuff anyway. Second, if you want to know the best skill you can work on as a Web Developer it is simply your personal and speech skills. I hired that guy above because he was nice to talk to, easy for the team to get along with, and honest. He was also obviously smart but definitely new in his skills. His personality got him the job. Finally, as for actual technical skills, HTML, CSS, and Javascript in general will get you through most of the "technical" questions in a junior interview. Keep up on those and you'll do fantastic. Edit: I obviously can't type today. Fixed some of the many typos.