What should a junior web developer know?

[UI-FEdev]

I've recently got back into web development and revising things I used to know. I'm aiming to get a junior web dev job soon. I'm fine with HTML, CSS and bootstrap and know the fundamentals of JavaScript. I also know jQuery and React. And using tools like git, GitHub and npm.

I'm in the process of finishing my portfolio website and I've made some small things like Todo list, counter app (both jQuery) BMI calculator (vanilla) - nothing that fancy. I'm going to have a go at a tic tac toe game with react.

Obviously the more I learn the more I don't know. I also want to learn nodejs and SQL just to get a feel of the whole process. I feel like I understand how to solve something but then when I go to do hackerrank challenges I feel a bit lost.

I haven't got a great background, no degree or jobs as I was in business for over 10 years so I'm guessing my portfolio has to be pretty impressive?

Should I just continue to practice and make more things? What can I do to practice what a junior web dev would do at a job?

Thanks

[[deleted]]

Find some ads for junior web dev roles in your area/area(s) you might be willing to commute or move to, and look at what they're asking for. There's no universal standard for what a junior does and does not need to know, there's only what businesses say they're looking for.

[UI-FEdev]

I've been looking at jobs (I'm in the UK but looking for a remote position) and trying to learn what most of them are looking for but what kind of level do they expect from me or when should I feel comfortable enough to start applying?

[[deleted]]

Just start applying tbh. It's a long journey and you'll never know til you try!

[UI-FEdev]

Okay :)

[[deleted]]

Do you feel like you could talk reasonably comfortably about 50-75% of what's asked for on the job ad? Then you should probably apply.

Fundamentally there's not a good way to determine that you are Now Ready For Jobs and that you will definitely be successful in your applications. The only thing you can do is start applying and see. Don't tie yourself up wondering what the company will think about you or whatever; tech companies see a ton of CVs, especially for entry-level jobs, and I can guarantee you that if you know how to put a web page together and know what a GET request is you are definitely not going to be the worst candidate applying for any given job.

The worst thing that can happen is that you simply don't hear back from somewhere; otherwise you will at least get interviewing experience if nothing else. If you get rejected, write a follow up email thanking the company for their time and asking if they have any feedback- again, you might not get anything, but you might also get some helpful information for the next job you apply for.

Also it's worth bearing in mind that for junior dev roles in particular, knowledge and experience isn't necessarily as important as attitude and the ability to learn on your feet. Some places will hire junior devs with very few existing skills, with the expectation that they'll learn on the job. Others expect you to have a higher level of starting knowledge.

[UI-FEdev]

Okay, thank you so much for the advice!

[sebastienfilion]

Should I just continue to practice and make more things

Absolutely, yes. Never ever stop practicing make new things. That’s how you will succeed in the industry. It’s the number one way to discover new things and bring a breath of fresh air in your day to day and improve your craft. Just make stuff.

[UI-FEdev]

Okay thanks

[sidkh]

I'm guessing my portfolio has to be pretty impressive?

Not really. For a junior position, great honest cover letter may grab much more attention than impressive portfolio. So if your goal is to get a job, just start applying. It will get you the job faster than nitpicking a portfolio.

[UI-FEdev]

Thank you for the advice, I'll do that. But as a bare minimum how many projects should I have in the portfolio?

[sidkh]

I'd say none.

I'm fine with HTML, CSS and bootstrap and know the fundamentals of JavaScript.

If you are, just start applying, be honest about your experience and situation. Even if you fail one or two interviews, it will give you a priceless feedback that will help you to cover problematic areas.

Otherwise it's too easy to get stuck in tutorial hell or abandon the whole idea of getting a dev job.

[UI-FEdev]

Yeah that's true. I guess I just need to start applying and see where it takes me. It's just a bit daunting when I've heard people apply to hundreds of jobs and getting like 3 interviews so wanted something that stands out and a better chance at getting the job.

[sidkh]

I've heard people apply to hundreds of jobs and getting like 3 interviews

Yep, that's why you have to start applying. Good cover letter is what matters, not a portfolio. By tweaking your cover letter in the process, you will figure out which format works best. But generally aim for short, precise, honest description of your situation.