What is a Senior Software Engineer? Junior vs Mid vs Senior Level Developers | The Difference

Subscribe for more!

📽 Gear:

Thanks for watching:
What is a Senior Software Engineer? Junior vs Mid vs Senior level Developers | The Difference
#SeniorSoftwareEngineer #SoftwareEngineer #WebDeveloper

[Basta]

Senior is just a title. What it means can vary between companies. It can mean just someone who is not junior. It can mean someone with just enough of years of experience. It can mean someone who can work independently with little supervision. It could mean that they are in charge of a project. It could mean that they are a subject matter expert at something. It could mean that they make higher level engineering decisions.

[danielrazulay]

Being senior is not about the amount of work perse. It's about delivering the correct amount of added value with the least changes/risk and about setting examples for less senior employees. Most of all it's about being able to delegate, collaborate and plan.

[sheikh]

As a Senior Dev, you have single handedly cured me of my impostor syndrome.
Thank you!

[tamasbalint]

I was search for this content / video for a while on YouTube. The best I have ever found. Very well explained. Thank you.

[ASDFANDYX]

undoubtedly the BEST video I watched this year - please continue the influx of incredibly valuable insight!

[danhnguyen]

Thanks a lot for sharing your experience! Great video!

[jackx]

Great video! As a mid-level engineer this content is spot on. Underrated channel.

[Doctorcraft]

This video is awesome! Thanks so much for sharing your knowledge!! :)

[PedrDiniz]

Great video man, thanks for the advice.

[rohans]

Thanks you answered all my doubts.
The video was very informative 😊

[alefratat]

Never been promoted in 15 years of career. I am happy to stay an individual contributor that brings his experience to the company without being burdened with responsibilities and management pressure.

[angelicamanjarres]

Just found you channel, very insightful. You're a nice down to earth guy and I really appreciate it. Some software developers act like they're rockstars at their jobs, which has never been my experience.

[TrafalgarLaw]

I am an engineer and live in spain and everyone, in supermarkets, bus stops, gyms, calls me a senior. This is what is a senior.

[pprathameshmore]

In here India, Companies except that Junior Developer to do Mid Level Developer's work

[matt-]

As a senior dev I can relate to this and in spades. Plan and deliver stuff that makes your customers (and org) happy, keep things on "auto-pilot" for managers, guide your teammates, take their pain away, and you will thrive.  Never cared for promotions, they just happened, increasingly found myself leading others and high stakes projects. Great vid!

[infinteuniverse]

So, essentially, you became a senior engineer after enough time in the field. Just goes to show you, there's no shortcuts. A Jr dev wanting to jump to Sr after 2 years is like a LoL player wanting to be Diamond after 2 season. Or a beginner Chess player wanting that 2k elo after 1 year.

[smetkicaprah]

Starting as mid level, and becoming a senior in 2-3 years? Shish, come on. It took me 8 years, and 25+ successful projects, to get the senior title. Just because you succeeded at one project, it doesn't mean you'll hit the ground running on your next one. I'm wondering how experienced is your manager, to propose such a step based on these facts, after working with you for just a few months.

[GrandpaRanOverRudolf]

work time wouldn't matter for senior vs junior (though experience in developing or running projects is a must, but that doesn't mean job-related necessarily and you can do/learn much more solo)

a senior would pick up libraries and languages quicker because they take design paradigms from each other. A senior also would find and solve bugs quicker, do more accurate estimates, and can do designs a junior does not have the expertise to, which will tend to work more often and not need as many tweaks when implementing. They would get more more done and/or to a higher quality (longevity, less bugs, code is easier to work with when specs change, less chance of necessity for a rewrite or blockers that need reinvention due to evolution of a project, concise but better coverage tests, well exercised organisation skills in terms of issues/versioning/releasing and app/feature/library itself but also documentation because they would have had experience in observing people read the docs and integrated feedback from that audience into their writing style). You very much do become a better, faster developer from experience. Though yeah, overthinking your performance and being anxious about it wouldn't help learning, you should only go at the pace that feels natural to you, and if anyone is going to be judgemental about that for some arbitrary non-deadline related reason that's a them problem, not yours.

I clicked this video because I interviewed somewhere and the guy impromptu called me junior when rejecting me, I found this very rude because I didn't claim to be a senior (though ironically the job I got after that interview was a senior title). I was trying to figure out what that even meant. I think, now, that he said it because they couldn't pay my salary I guess (which was just the average for a mid level here). He also kept saying he found my code in my hobby projects confusing, which I think said more about his poor understanding of the language... I've only gotten the opposite remarks in regards to my coding style if I exclude him. Very odd experience. It still rattles in my mind sometimes because it made no sense lmao

edit: NEVER execute on someone else's will, ALWAYS get direct responsibilities. Favours and clout with one person puts you at the mercy of that one person, and if they're greedily hoarding them like that they are not your friend and WILL NOT be good on that promise. You need to remove or re-educate that person, and that whole project has a high chance of slow burning out people (which WILL be new hires over time) and then just dying regardless of the actual original quality of the product because literally no one wants to work for something like that in lieu of their mental health... huge huge red flag. Say what you will about management procedures, but this is the only one that's actually going to save your team if you need HR's help due to the drama that very much will result when someone is operating like this, and even if they're honourable at the start it's far far too easy to slip up and go to the dark side, with perfectly good and totally valid excuses but you need to know and accept your limits amicably, and this will help both you in your future career and whatever projects, people, and even your own sense of belonging and value later on (you'll find people will support you of their own free will and not force you to do things you have weaknesses in, but at the same time you'll discover your actual strengths because they will end up relying on you more heavily in those specific areas, which means you'll "fit" and have a specific role and purpose you are exceptionally good at yourself, this is the whole point of human cooperation as an evolved, thinking species and it's hella cool). Direct responsibilities only.

[joebrooks]

Imo anyone who has prior mgmt or quality experience usually becomes a Senior Developer/Engineer overnight who may not even know the basics of code or bare bones basics but they lead the team based on their prior experience not tech stack or anything

[valcrist]

For me, my best bet is the amount "time" and "experience" the person has gone through with regards to his personal career. Also, the amount of "Ownership" to their work.. ownership like if something went wrong.. he is the person should be responsible answering.

Even a new graduate may be more "updated" to a Senior Engineer because he has a one year experience to the system.. and a new employee (who is a senior) just went in.. but a Senior Software Engineer has a significant "Real" stories to tell and how it was handled.

Also knows what things should be "properly delegate" to it's subordinates.. protecting the team and it's subordinates. Maintaining harmony and sustainability.

Also, it can foresee farther than a junior... most of the time... but not always.

Also with regards to Salary.. Remember.. it's not the salary that you deserve.. it's the salary the "you asked for". You have to take it. But please for the good of the universe.. be reasonable as well.