Read on Twitter
Are you a Junior Developer?
Then you probably have one big disadvantage that often becomes the #1 reason why junior developers are not invited to job interviews
↓
Then you probably have one big disadvantage that often becomes the #1 reason why junior developers are not invited to job interviews
↓
Nobody wants you without work experience.
Picture this
You open a job board website, click on the job ad, look through the requirements, and find such line:
“Looking for Junior developers with 1-2 years of experience”
You open a job board website, click on the job ad, look through the requirements, and find such line:
“Looking for Junior developers with 1-2 years of experience”
Yes, it seems illogical
You are a young developer who has just graduated from university or finished a programming course
You feel ready to get real work experience
But...
Companies don’t want to give it to you before you get it
You are a young developer who has just graduated from university or finished a programming course
You feel ready to get real work experience
But...
Companies don’t want to give it to you before you get it
This is the moment when you face reality:
Nobody wants to hire a developer without real-world experience
Why?
Nobody wants to hire a developer without real-world experience
Why?
Two main reasons:
1. Junior developers need to be trained
2. Junior developers are risky
1. Junior developers need to be trained
2. Junior developers are risky
And here you are
You don’t have work experience
You don’t know where to get it
You don’t know what to do
Solution?
You don’t have work experience
You don’t know where to get it
You don’t know what to do
Solution?
Imitate it
If you have little or no work experience you can imitate it with side projects
If you have little or no work experience you can imitate it with side projects
Generally, work experience shows recruiters and companies that:
• You can code
• You have worked in a team and know how to communicate effectively
• You can do things on your own
• You can code
• You have worked in a team and know how to communicate effectively
• You can do things on your own
Side projects show recruiters that:
• You can code
• You can do things on your own
• You can code
• You can do things on your own
2 of 3
Not bad
Side projects kind of replace work experience in the eyes of recruiters
Not bad
Side projects kind of replace work experience in the eyes of recruiters
What side projects to build?
1. Projects that related to your position and field
2. Crazy ideas from your head that you want to put into reality
TIP: To find ideas for side projects, you can use Google: "[YOUR POSITION] side projects ideas"
1. Projects that related to your position and field
2. Crazy ideas from your head that you want to put into reality
TIP: To find ideas for side projects, you can use Google: "[YOUR POSITION] side projects ideas"
How difficult projects should be?
Average or above average
Some examples ↓
Average or above average
Some examples ↓
Example of “easy” side projects:
• To-do list
• Calculator
• Hello world
• To-do list
• Calculator
• Hello world
Example of “average” side projects:
• Chat application
• Soundcloud like an audio player
• Clone of any big website with basic functionality
• Chat application
• Soundcloud like an audio player
• Clone of any big website with basic functionality
How much side project should you build?
2-3 projects
2-3 projects
Where to list them?
Two places:
1. Resume (to the “Projects” section)
2. Github
Two places:
1. Resume (to the “Projects” section)
2. Github
That's it, go get this job!
Thanks for reading
Your friend,
– Nick
Thanks for reading
Your friend,
– Nick
I'm writing a book on How To Nail The Technical Interview where I've summarized everything I've learned, all my tricks & tips and other developers experience into the proven repeatable system any developer can use to pass the interview and get a job
↓
http://nailthetechnicalinterview.com
↓
http://nailthetechnicalinterview.com
