Am I still a Junior Developer?
Tags: webdev, programming, juniordeveloper, code
Published: 2017-02-26 22:06:03

---
title: Am I still a Junior Developer?
published: true
description: I ask myself "Am I still a Junior Developer?", and then I walk through how I can answer the question.
cover_image: http://i.imgur.com/yvthM1g.png
tags: Web Development, Programming, Junior Developer, Code
---

I started to learn how to code in August 2014 at General Assembly. After finishing the 3 month Web Development Immersive course there I was able to claim the title “Junior Full Stack Developer”. I landed my first job as a Junior Full Stack Developer at Skyline Technology Solutions in February 2015.
A couple of weeks ago I started asking my self “Am I still a Junior Developer?”, because It's been 2.5 years now that I've been coding and 2 years of coding professionally. How do I know when I leveled up? Am I going to be a Junior Developer forever???

![alt text](https://cdn-images-1.medium.com/max/800/1*T-VmyFjh4tqGpCcRidA9ng.png "Scared Kermit")

So I started to reflect back to when I started and where I am today and I remember not fully understanding callbacks, this, and prototypes in JavaScript. Not knowing why I would need to use JavaScript's .call() or .apply() methods. Or what were tools such as requireJS, webpack, grunt, or gulp actually doing for me. I can't recall when, but I remember everything was starting to click and I finally understood this (Pun Intended)!

![alt text](https://cdn-images-1.medium.com/max/800/1*mHtTVyi5EIB_y9IlF9mjrw.jpeg "Alan from the Hangover Thinking, hard, difficult, math")

Before I answer the question in the title of this post, I'll list out some bullet points on what I think determines the difference between a Junior & Mid-Level Developer.

## Junior

* Understands basic programming concepts
* Will produce code without keeping performance or maintainability in mind sometimes
* Can use libraries & frameworks but will not always understand what the tools are actually doing for them and/or how's it doing them.
* Might copy & paste code from the web (such as Stack Overflow) without understand it, if it just works
* Will need occasional mentorship
* Sometimes won't ask for help when stuck because of fear thinking you're not good enough (You are good! It's ok to ask for help ðŸ˜Š)

## Mid-Level

* Understands one or more languages more deeply
* Will produce code with thinking about performance & maintainability
* Understands what the tools are doing for them, digs into the source code often to understand how it works & also finds undocumented usage of tools.
* Will understand code found on the Web before even thinking about copying & pasting code.
* Will ask for help when they know they're stuck (because asking for help is ok!)

The above bullet points are just high level bullet points I gathered with the help of the internet & talking to my co-workers. So I am proud & confident to say that I am now a Mid-Level Developer ðŸ¤“!

> *WAIT! Can I seriously just answer this question myself and change my title on my own? You actually can because there is no piece of paper you need to claim any title in this field. In my opinion what you should do before changing your title is discuss this question with the people you work with or even the people you interact with in the tech community.*

I'll definitely write a blog post when I feel I've reached Senior Level! :-)

<em>This article originally published on my <a href="https://medium.com/@clickclickonsal/am-i-still-a-junior-developer-1cb0a00ae7ea#.32xfkg8dn">Medium publication</a></em>