Help! Hiring a Jr Dev

twitter logo ・1 min read

Hi All, We just got the green light to go a head and start the process to hire a jr dev for the team? Currently I am the only developer on the team, and I am going to be leaned on heavily on the interview process.

I want to make sure that I vet the person properly. This is all new to me any help and or pointers are greatly appreciated.

twitter logo DISCUSS (9)
markdown guide

Focus more on enthusiasm. I’ve always found that the best junior devs are the ones with the greatest enthusiasm for the work. They’re the ones who won’t get discouraged when they’re presented with a challenge.


Exactly this. Remember that you are hiring Jr. Developer not an Intermediate Developer, he probably doesn't know much, what is important is the willingness to learn.

Ask about hobbies, involvement in dev communities like, freecodecamp, etc...

And most importantly, make sure you hire a nice guy, you don't want to work with an asshole.


You mustn't lose the focus of why are you hiring somebody to your team. It's easy to hire a poor candidate for the wrong reasons.

For example, if you are hiring somebody and he or she is not prepared for the job, then you will spend your time training him/her. How is it a gaining for the project?.

Also, you could think of somebody that it's a compliment to your small team, i.e. somebody that knows something that you don't know (or you don't want to work). SRP speaking, it's easy to integrate a new member to the team, if the new member will work on a specific part of the project (versus picking an all-in-one-developer). For example, somebody for the database, testing, creating the UI and so on.


If you are in fact hiring a "jr" developer, you should absolutely expect to spend time training them...


You are asking to hire somebody that studied at least 2 years (or 4 years) somewhere. There is part of the training (that you must do to the new kid) is the induction, teaching about the database model, about the code, naming convention, business logic (what the project does) structures of the folders, and that's it. Now, if you want to be a teacher, then it will hurt your deadline.

I am trying to hash out expectations from management on what they want from the new role as well as myself with training said new person.

If you are that worried about a deadline you don't want a real "jr dev". You want a "dev". I'm not disagreeing with you, I'm just clarifying what I believe should be a company's or team's attitude towards hiring a "jr" developer. You are describing basic on-boarding of bringing somebody on. That is the same from jr all the way to senior. If you don't have time to "teach" somebody because you are worried about a deadline, then you aren't looking at a "jr" dev to begin with.


Technical expectations of junior Devs should be lower. As others stated, enthusiasm and interested to learn is more important. The question is not what they know, but what can they learn?

There are several reasons to hire junior devs.

  • If no one hires them, then junior devs will not ever become intermediate or senior devs.
  • Perk of teaching a junior dev is their questions will help you write code more clearly.
  • Junior devs can learn a lot and accomplish tasks you may find repetitive or boring, yet bring value

so what are you exactly looking for to be done?

Classic DEV Post from Mar 21

How to find open source projects as a new developer?

Maybe I'm missing something, but it seems hard to find meaningful open-source p...

Ken Darling profile image
A solo C# programmer mostly converting VBA/Access applications to C#