4 signs your junior role is TRULY a junior role

Avoid "fake" junior roles by looking for these characteristics

If you want to avoid the heartache of losing your job due to lack of skill and performance, it’s critical you understand what a junior position should look like.

I‘ve experienced “fake” junior positions in the past because I didn’t ask the right questions during the interview process and I ignored the warning signs while on the job. I’ve also experienced real junior positions that fit my skill set and came with the resources every junior needs. 

With this in mind, lets’ discuss four signs that indicate your position is truly a junior position.

You’ll receive training and mentorship from senior devs or mid level devs.

At my current company (as of this writing) NorthBuilt, I receive both mentorship and training in the following ways:

• I receive feedback and encouragement via PR comments 

• I have huddles with senior devs when I’m stuck on a problem and they give guidance on how to approach a difficult problem

Notice I said feedback and encouragement. Feedback or constructive criticism is crucial for the growth of a junior dev. However, corrective feedback without encouragement can lead to discouragement. I suspect there’re many senior devs who believe being stoic during PR reviews is the way to go and giving encouragement isn’t in their job description. In my opinion, this is a horrible attitude. If senior devs are in a leadership position, how can a good leader not be encouraging? 

Application - During the interview process, ask if you will receive mentorship or training. If the answer is no, this might mean the position is more mid than junior

You'll be given the opportunity to learn and grow

Currently I’m allotted an hour (sometimes more if I have the time) of personal study time before my work begins. My company gives me the opportunity to set educational goals during quarterly meetings and encourage me to complete my goals at a specified date.

You'll be challenged according to your skillset

If a position is truly Junior, you shouldn’t be expected to handle the same issues in the same manner a lead or senior would. You may think this is obvious but common sense isn’t always common.

I was once hired as a junior but the owner expected me to “architect” and “design” the whole app by myself with very little guidance or design mock ups. I was stressed and filled with anxiety during that time until I was eventually let go because I didn’t meet expectations. This should NEVER happen to a junior developer. 

My current job gives me task that fit my current skill set as a React and React Native developer.

Application - During the interview process, ask if you will be working with a lead dev. If you’re working by yourself with little guidance, the role your interviewing for is probably a senior position

You'll be challenged outside your skillset but with understanding and patience

When I am given tasks outside my current skill set, it comes with patience and guidance. My supervisors will even say something like this,”We’re dumping in you the deep end to see what you can do.” It’s encouraging and it gives me a chance to grow.

Closing

By expressing my own experiences as a junior developer, I hope you won’t settle for roles that won’t meet your needs. Instead, I hope you ask questions during the interview process that will reveal if the position you’re applying for is truly meant to guide you as a junior so you can add value to your team.