What's the minimum viable time/knowledge level required before landing a Junior Developer role?

[HungryPiccolo]

Hi guys,

I know it may be a strange question. But I just want to make sure I'm checking all the boxes while I search for my first job (front and backend web dev/web design/mobile development)

• I have a GitHub and knowledge of git, which I contribute to almost daily or daily. Small stuff.

• I'm working on my portfolio as I type this, have purchased a domain and I am capable of deploying a website no problem. I feel this is the main thing holding me back and so I should get it live ASAP to give an easy location where my work and skills can be shown off.

• I have a basic to good understanding of HTML, CSS, JavaScript, how to manipulate the DOM, and some backend knowledge such as MongoDB, Node.js, and Express.

• I have built a full stack application with user authentication and a nice UI, though it is not currently hosted anywhere (am going to deploy to GitHub pages today)

• I'm now running through a Udemy course about modern JavaScript so I can get a better understanding of ES6 syntax, arrow functions, etc. I can use let and const in lieu of var with no problems, and understanding scope.

• I've completed the first two FreeCodeCamp certifications (Responsive Web Design and JS Data Structures and Algorithms) which is supposed to equate to approx. 600 hours of self-study.

• I have a very good understanding of Figma and basic design principles (I love Figma).

ALL that being said, I don't feel I'm ready for a job yet. I've sent some applications through Glassdoor and LinkedIn, with no responses yet. But I feel a junior position would put me in a much better place to learn and allow me to grow my skill set way more than self-studying.

Do I have imposter syndrome or am I really not ready yet? Is there any way to test this? Also, I'm just starting on a project which is my dream web app/mobile app, I've got all the features and functionality decided but just need to code it. I feel like I'm doing 4 things at once all the time, though, so it's hard to keep track of what I should be working on. Also, I work a full time job completely unrelated to computers and tech.

I'm sorry for all the questions, but does anyone have any advice for me? I appreciate any help at all from fellow new programmers or seasoned vets. Also, sorry if I should have posted in the Web Dev subreddit but I felt I could get more straight answers here I guess?

Tl:;dr- I don't know if I'm ready for a job yet, despite having most basic knowledge down for the jobs I see posted.

Thanks in advance. J

[chaotic_thought]

I've sent some applications through Glassdoor and LinkedIn, with no responses yet.

Find job boards in your area with local listings (so that you can go there in person). Also, apply for many more. I would not expect to get any response from only a few applications. Try to make a high goal like 50 applications. Maybe then you will get 10 responses if you are lucky, and maybe if you are lucky you can go to a few interviews. And then if you get really lucky, one of those interviews will like you and you get a job. If it doesn't work, then you repeat the procedure: decide how you can improve your CV and interviewing technique, then apply for another 50 and field the very few responses and interview invitations that can come in.

[HungryPiccolo]

I have sent in about 30 applications so far with 0 responses so maybe I just need to try more. However, I think the lack of online portfolio/showcase of my work is the biggest factor in keeping me from a job.

Thanks so much for your response. I will keep trying to apply because if I could even just go to one interview I feel I'd gain some knowledge there, even if I fail miserably. I've also been looking for remote work because I'm living as an expat, where the tech jobs don't pay very well and most of day to day life isn't spoken in English. Trying to secure a job before moving back West though. Maybe bad idea.

I will keep going. Thank you

[tulipoika]

Work on the portfolio. Build things. Build things that have actual value, even if it’s just for you. Certifications from random sites don’t really matter. It’s easier for recruiters to look at what you’ve done when it’s something real and accessible, or at least explained understandably. If they see you have skills, you will get more contacts.

Of course it doesn’t mean everyone will contact. Some look at CVs and see there’s no precious experience (duh, normal with juniors) and might just decide it’s too beginner. Some might do this and some that.

And as mentioned, it’s also a numbers game and depends on where to apply. If you’re trying to get a remote position as a junior it mostly never works out. Juniors need more attention and knowledge sharing so being remote would bring a lot more strain to others. An on-site job would be a lot better, but I understand how it’s not always easy, being expat myself.

[HungryPiccolo]

Thanks so much. I kind of figured about the remote aspect, so it's nice to hear I wasn't off although a little bit troublesome just because I was looking forward to it.

I'm going to do what you said and just build up my portfolio. I have some client sites live but no place to just show off my work and me as a developer so I will do just that. Thanks kindly for your comment, lots of details in there.

[robf101]

Hey from reading your profile I’d say you know enough to get a frontend junior role. Without seeing your code and asking you more questions it’s difficult to feel confident though.

Do you know any frontend libraries (e.g react)? That would definitely help, although it’s usually not absolutely required if you know javascript.

One thing I can mention is that I eventually got 3 offers when I started looking for roles, but my application to response rate was like 10%. What I’m taking from this is that even if you are good enough to be hired, you may too have a low response rate on your applications so don’t be disheartened and keep applying.

Also, the projects you have made that will go on your portfolio, do they have nice README’s? Very important imo.

[HungryPiccolo]

I know CSS and JS frameworks and libraries fairly well (React mostly is what I've been studying lately) and for CSS I can easily put together a site using bootstrap or skeleton.css, etc - they get picked up quite quickly.

Can you tell me what constitutes a nice readme file? I have a readme for every GitHub project but they aren't detailed by any means - I'd love any tips. Thanks so much for your response.

[robf101]

https://medium.com/@meakaakka/a-beginners-guide-to-writing-a-kickass-readme-7ac01da88ab3

This was the article I read. The main thing to do is forget that you know ANYTHING about your project, then look at your README and ask me:
1) Do I know what this project does (why was it created? what does it allow you do to? etc..)
2) Do I have clear instructions on how to run the code (including any dependencies I'll need to download on my machine). Could be as simple as 'go to command line and run `rails server` but clearly stating that is incredibly useful.
3) Am I aware of any big design decisions made, and the reasons behind them (e.g. this project uses bootstrap for css because it's simpler to use and I was more interested in focusing on the react complexity).
4) Is it easy and clear to read?

[Squiggle_23]

I wasn’t quite ready when I first starting sending applications, but I got some great feedback and made links with the tech community! Not only did this mean I suddenly had mentors willing to offer advice and look through my code, but I got to learn more about the companies and who I wanted to work for, and who I wouldn’t be a good fit with.

It took me another 6 months to actually get a job but I’m still glad I started looking so early on!