If you’ve been writing code for a while now then you may have asked yourself:
When should I start applying for the jobs?
Asking such question is an indication of urgency. Pat yourself in the back as you’re already ahead of other aspiring developers who’re lost in the details, avoiding the bigger picture.
You see, they have forgotten why they started to learn, why they’re going through stress and countless hours trying to figure out the solutions.
In whatever way you might be thinking about the job, the answer is almost always the same.
As soon as you first ask yourself: Should I apply for a job?
The first thing you should do is create a CV and fill it with the basic details. (You can improve it later).
That’s STEP ONE!
Secondly you should go to a job site and apply for any job that matches you skill set. Pay attention to the “Requirements” section. Ignore the wish list or “good to have” section.
And that’s it.
That’s really the only answer to: When to start applying for jobs?
The reason why I suggest this is because nobody can tell you exactly when you’re ready to apply for the jobs. NOBODY!
They are in their own world, lost solving their own problems. They don’t know you. If you asked 10 people you’re going to get 10 different answers, and trust me, settling with one answer, when you have 10 different suggestions/ideas to decide from, is a difficult task.
So that’s my suggestion. If you think you should probably start applying for the jobs, you should definitely do it.
Let the feedback from recruiters and companies tell you if you’re ready or not.