Interview Story: "What level are you at?"

The Issue

The last time I went for a job interview was about 4-5 months ago. Like many others, I went to various places, each with its own interesting experience, and I realized that no two interviews were the same. I prepared myself to be comfortable and set criteria for a new work environment, not focusing too much on theory but rather answering based on my practical work experience.

One day, a CTO asked me a question: "What level do you think you are at?" Without hesitation, I answered, "Actually, I haven't paid much attention to my level. My immediate goal is to keep learning...". - "If you haven't determined your level, you should reconsider!"

It was clear that the interviewer wanted me to choose between three levels: Junior, Mid-Level, and Senior. With over 5 years of experience, I might choose to be at the Senior level, as it is commonly accepted in the local job market that someone with 5 or more years of experience can be considered a Senior. But I think that I haven't reached this level yet, maybe I'm just at the Mid-Level. However, because the perception and market have conflicting views on the distinction between these levels, or in other words, these 3 levels depend on the thoughts of each individual, I am hesitant and unable to give an accurate answer for myself.

The words of the CTO were right, not determining your level is indeed dangerous, but because I didn't express my thoughts, it was misunderstood that I didn't know where I was. Therefore, in today's article, let's discuss the three levels: Junior, Mid-Level, and Senior, to see what it really takes to be a "real" Senior!

Junior, Mid-Level, and Senior

Try searching Google with the keywords "Junior, Mid-Level, and Senior developer" and you will find many results, showing that this is a topic that many people are interested in. Most of us read to find out where we are and what we need to do to achieve the next level.

Among them, many articles list the number of years of experience to determine at which level a person is. For example, fresh graduates are considered Junior, 3-5 years are considered Mid-Level, and 5 years or more are considered Senior...! To be honest, I used to believe in these numbers too. I thought that the longer I work, the higher my "rank" would be.

Or there are articles that point out that the number of years does not solely determine a person's level, but rather it depends on their problem-solving abilities. "They know how to organize code, care about future maintainability, how to ask questions, and how to solve problems..." It sounds reasonable, but it may still not be enough. For me, a programmer should not only know how to code. To reach the highest level in programming, they must go beyond coding and do much more.

By chance, I found a very detailed article about what can be achieved at all three levels. Moreover, it is comprehensive, detailed, and provides advice on how to level up. Readers can find it at Levels of Seniority.

To summarize, the article mainly focuses on the Junior level, introducing the concept, indicators, and what to do to progress. Some notable points include:

• Their mantra is "make it work" rather than paying much attention to the solution. For them, having a functional software and having good software are equivalent.
• They are unaware of the business aspect of the company, meaning they don't care about or know why they are doing this work for the company.
• Blaming others (Somebody else's problem) when they believe that someone else should be responsible for their problem.
• They don't engage in team discussions.
• ...

Afterward, the article provides advice for Juniors, such as:

• Reading a lot of code, not just the code in the projects they are working on, but also the source code of libraries, frameworks, open-source projects, etc.
• Doing personal projects.
• Stop blaming others.
• Don't limit yourself by your job title. Do more and be more proactive.
• Avoid saying "it works on my machine," instead, understand why the application doesn't work somewhere else, as surely someone else is facing the issue, not just you. The above statement is equivalent to denying responsibility.
• Interact with higher-level developers, observe how they work, and if possible, find a mentor. No one likes a person who knows everything, but restrain your ego and be humble to learn from the experienced ones.
• ...

A Mid-level includes all the elements of a Junior, along with problem-solving abilities. They have more knowledge than Juniors but still struggle with applying it. The article emphasizes that Mid-level is very common and is sometimes mistaken for "Senior". However, they need additional mentoring to become a "real" Senior.

A Senior is the next level after Mid-Level developer. They can complete tasks independently without supervision and without introducing any issues during the process. Some of the things a Senior can do include:

• They are practical in their work, not influenced by the best tool.
• They have a holistic view of this field, knowing which tool is the best for the job in most cases.
• They know they are part of a team. They see it as their responsibility to mentor others.
• They have a deep understanding of the field they are working in.
• They think beyond just coding.
• They know how to give feedback without causing harm to anyone...
• ...

In summary, in addition to coding, a Senior can mentor and advise others, have a deep understanding of the business, the industry, and the human aspect.

Conclusion

Junior, Mid-Level, and Senior are the three levels of a programmer, with Junior being the lowest and Senior being someone with extensive knowledge. Determining which level you are at and what you need to do to reach the next level is crucial in everyone's career path.