Don’t sell yourself short.
Seriously, don’t be a Junior Developer. A Junior Developer puts this title in their resume, emails, and LinkedIn… They announce it to the world. Don’t.
When you do that, this is what recruiters and companies see:
“Hi, I’m desperately looking to get hired as a developer.
I’m still new at this, but can you please please please place a bet on me and hope that I turn out to be an asset and not a liability for your company.
Oh, and I’m also going to need a lot of help from your current employees for the first 6 months!”
If that is the case, then you will have better long-term success if you focus on improving your skills to become an intermediate developer.
Only then should you start applying to jobs.
Dedicate yourself full-time to learning proper skills. This way, you don’t pigeonhole yourself to the “junior” developer role that you brand yourself as.
Remember, first impressions are important.
By getting hired as a junior developer, you will have to spend a longer time getting out of that role than if you would have spent a little more time getting comfortable calling yourself an intermediate developer (or just a "developer") and getting hired into that role right away.
There won’t be a magic moment. You will always feel like you don’t know enough. You will always feel like others are smarter than you.
This is called impostor syndrome. It’s normal and every developer feels it.
Here is a simple test to determine if you are a junior developer:
Yes to all the above? Good. You are not a junior developer.
Stop that short-term thinking.
Unless your job involves you working with really smart people that you can learn from every day, on technologies that are relevant and current (few junior developer roles offer you this) then your time would be better invested learning skills to get out of the junior mindset.
Long term, you will earn more money, be working with better developer teams, and you will be more likely to work for a company that teaches you and let’s you work with up-to-date technologies every day.
Don’t work on updating a Wordpress plugin as the resident junior developer of a law firm.
That won’t help you long term.
If you apply for junior developer roles, the best case scenario: you get hired as a junior developer.
If you apply for intermediate developer roles, the best case scenario: you get hired as an intermediate developer.
Don’t sell yourself short.
Fair point. That's why I created The Complete Junior to Senior Web Developer Roadmap, the ultimate resource to get people out of the “junior mindset”.
The best way to do that is to understand the whole developer ecosystem on the web and even the selective knowledge known by only senior developers.
This course teaches you the things that nobody else teaches you in one go. At best, you could learn fragmented parts of what I'll teach you from vague and outdated tutorials online.
Here are the topics I cover:
These are the topics that will make sure you are not a junior developer.
The course is focused on connecting the dots between all of these so that the next time you are in an interview, you can speak intelligently about current tactics for building projects, architecture, and setting up developer environments.
It is the follow-up course to my complete web developer bootcamp.
If you're not ready to fast track your journey, then here's the exact topics and skills you need to learn to go from Junior to Senior in the next 12 months, using mostly free resources.
To become a Senior Developer, you will need more than just technical skills. I have written extensively about the other “peripheral” skills (i.e. people skills) in my article How To Become A Senior Developer.
Ok, enough chatter. Let’s get started and have a look at what skills you need, and how to get you out of being stuck as a Junior Developer in 2024.
Here's the assumption I'm going with here:
If this is not the case, go learn all of this here first).
However...
Then you need to work on the skills I outline below.
As with all of my articles and courses, our focus is on efficiency. We all have the same hours in a day, but some people are able to learn and do more than others.
Side note: That's actually a skill you can learn. So my #1 suggestion is to first become an efficient learner.
I'm going to save you a ton of time because rather than having to jump around to a bunch of different articles and youtube videos, I've outlined everything that I recommend you learn below.
These are the skills (and resources... mostly free) that will make you stand above a Junior Developer role:
Update: All these above are still great resources but if you want to learn everything above and more, all in one place... you can also check out my Advanced JavaScript Concepts Course.
Update: Already a member of ZTM? You can learn React, Redux, and more and become a top 10% React developer with our Complete React Developer Bootcamp.
You'll get to implement your knowledge by building a massive E-commerce app with Redux, Hooks, GraphQL, ContextAPI, Stripe, Firebase.
Want to learn Vue or Angular instead?
No problem, take our Complete Vue Developer Bootcamp or Complete Angular Bootcamp instead!
Ok, back to the list.
Of course, we also talk about testing in almost all of our programming courses but we also have a dedicated testing course here as well.
Or, if you want to learn everything in one place, then take our TypeScript course.
This course covers everything from beginner to advanced topics, so if you're a JavaScript developer who is serious about taking your coding skills and career to the next level, then this is the course for you.
You thought I was going to leave this one out didn't you?!
To be clear, I haven't added this to the list for 2024 just because it's the hot and trendy thing right now.
I've spent 200+ hours going deep and these tools are definitely here to stay and are going to become a key part of the developer's toolkit to become more efficient and deliver more value.
However... there is a right way and a wrong way to use AI tools.
Also I feel strongly that AI tools aren't meant to completely replace programmers.
Keep these 2 rules in mind:
But should you use it to help you learn? Absolutely.
However, you need to be careful because you can use it in the wrong way that negatively affects your learning and fundamental understanding to become a senior level developer.
I created a workshop for ZTM students to show them the right way but recently made it free to anyone to take advantage of. I hope it helps.
As I'm sure you've noticed by now, the difference between junior developers and senior developers isn't just the technical skills listed above.
That's not enough.
There is also a set of non-technical skills that are just as important. I wrote a whole post that covers these 5 other important non-technical skills you need to become a senior developer so I won't re-write it here.
But the high-level answer is:
A Junior Developer writes code and just does the work they're told to do.
A Senior Developer is someone who brings an incremental benefit to the table. A Senior Developer is someone that:
Does your head hurt yet?
This will take a while for you to go through but at least you have a roadmap of what is important for you to learn in 2024 to go from Junior to Senior Developer.
Being a developer is a never ending journey of learning as technologies always change.
In order to keep up with the industry, your best bet is to be efficient and be wise about what you spend time on because it is impossible to learn and know everything.
Focus your efforts on connecting the dots.
By learning the fundamentals, you are more resistant to change.
This is the theory behind all of the courses that I teach.
And just in case you're wondering... yes, I do have a course that teaches all of the topics mentioned above. It's called The Complete Junior to Senior Web Developer Roadmap.
It has over 37 hours of professional, HD video lessons and gives you everything in one place to guide you along your journey to becoming a Senior Developer.
You don't have to take my word for it either. Check out the screenshot below which is from a post by a ZTM graduate.
Will 37 hours be enough for you to call yourself a senior developer?
No! Of course not. That's just silly. But it will guide you along the right path.
Stop calling yourself a Junior Developer. But always keep a Junior Developer mindset.
What does that mean?!
This means that you are constantly looking to learn from others and improve (junior mindset), no matter how senior you are but you never settle for a junior developer role.
Apply for roles for which you are underqualified, not overqualified.
Remember that if you never ask (or in this case, never apply to the intermediate role), the answer will always be no.
Don’t overestimate the world and underestimate yourself. You are better than you think.
These days, my full-time job is to teach people to code, get hired and advance their careers in the most efficient way possible as the Lead Instructor of the Zero To Mastery Academy. You can see a few of my courses below or see all of our courses by visiting the courses page.