Junior vs Mid vs Senior Software Developer
If you have ever wondered what makes a senior engineer, a senior, and what makes a junior developer a junior, in this video I share with you the differences on the workplace that exists among Seniors, mid and juniors software developers. If you wanted to start a career in tech and wondering what the different roles demand and what skills are required I ave good news for you:
Starting from a junior software developer you can expect to write code primarily. You are expected to know the language, but flaws and missing points here and there are not a problem. You are not supposed to be totally independent, on the contrary, and if you were lucky enough to be working in a bigger company with many developers, you can have multiple pair programming sessions where you can really learn a lot. So, my advice is make the best out of those opportunities, don't be afraid to ask questions, make mistakes and experiments. Your journey as just started, try to learn but also have fun
As a mid level developer your workload increases and also your responsibilities. You are now expected to be independent, of course asking questions and counsel to seniors is always a good idea. Better than make a huge mistake, because remember now you are fully responsible of whatever goes into the code, you can be charged with testing your own, or other developers' code, and whatever goes into production is now your problem as well. However, the pay is higher and also the tasks are more challenging and motivating. You get to work on new feature, participate in the design of some of this features. And debugging don't forget about that...good luck 😐
Seniors have the most responsibility, but believe it or not they don't get to work much on the coding part. As a matter of fact, seniors software engineers tend to be worse at coding than juniors. That's because their job now is more administrative, they get to deal with clients, supervisors, even the executive. They can be in charge of an entire product, and fundamental skills to have to thrive in a role like this are solid organisational skills, teamwork and communication. Are you ready for all this? Of course, your technical knowledge is to the roof, you must be able to come up with solutions to problems, bugs and new designs. Lay out a roadmap or workflow for the team and most importantly make sure the team is up to speed, everyone is working well and the code looks coherent. So, prepare to have lots of code reviews sessions.
If you liked this video and would like to help this channel, don't forget to leave a like and share, and also subscribe for more content like this one. And follow me on my social Twitter and Github.
I'll see you at the next one,
BeGeos
Social:
Twitter: [ / begeosdev ]( / begeosdev )
GitHub: [https://github.com/BeGeos](https://github.com/BeGeos)
Music:
https://www.bensound.com
