Middle or Junior ❔

Middle or Junior ❔

If you didn't just start your journey in IT yesterday, and especially if you've had experience in a field adjacent to DevOps such as system administration, then you should probably seriously consider positioning yourself as a Middle.

➡️ Let me explain why.

Let's say you want to move into DevOps, but it seems to you that your skills are only enough for a junior position. That's fine, and you're probably assessing your level accurately. However, it's possible that you're no longer a junior, even if you're not yet a middle.

But since you can't be like the monkey in that joke, you'll still have to choose what to write on your resume or which job to apply for.

Competition among juniors will be higher than among middles, while the demands placed on them aren't much lower.

It seems that in this case it really is better to try to be a middle, even if you fall a little short. Skills can be brought up to speed in a fairly short time, which will be useful even if you go in as a junior — it will let you stand out more favorably against the others.

Of course, besides hard skills you also need to level up your soft skills, as well as have a properly formatted resume. But that's a topic for a separate conversation.

By the way, there's also a substantial salary difference between a junior and a middle.

✍️ Come and study in my mentorship program, which will not only quickly bring you up to the required level but also teach you to present yourself in the best light.