Junior vs Mid-Level vs Senior Developer — what’s the difference? (⚡️YouTube Short)

preview_player
Показать описание
Will Sentance makes a claim about the difference between Junior, Mid-Level, and Senior developers.
Рекомендации по теме
Комментарии
Автор

I feel like this can apply to so many more roles than just developers. Great summary!

kozchrist
Автор

You forgot the most important thing:
Junior = no jobs

eleazarhernandez
Автор

so im a mid level engineer with no job. please somebody hire me, i am dying here

encapsule
Автор

A principal engineer can take the feature they are given and then define for the team what is *actually* required, given the real business and technology context

orterves
Автор

Soo all my previous seniors weren't seniors, 🤯

mirko
Автор

Thanks for this. I guess I really am a senior engineer

themuslimview
Автор

That's a great classification indeed

jorgesanf
Автор

A senior engineer takes a feature they were supposed to build and makes a better one

josephchauvin
Автор

Junior = function
Mid. = module / namespace
Senior = application / project

natescode
Автор

I don’t know… I think any level can do it, each level will take longer though. This is just my opinion, I am the only developer I know and yet to land my first job. I think I can do anything you ask me too, some problems might take longer than others. I often tell my wife, I can do anything with a keyboard and monitor, all I need is time. But I am no senior.

tanglesites
Автор

Due to inflation the new Junior developer is a Mid level developer

angelg
Автор

Any sufficiently smart engineer (junior or senior) can write anything, provided that they have the right technical and domain background.

A senior engineer will leverage their experience into better decision making.

A senior engineer will write less code for the same problem and have picked better compromises in the approach taken.

A senior engineer can make the right tradeoffs between faster short term delivery and long term software quality.

By having a deep understanding of their customers a senior engineer is good at assessing the business impact and risk of their software.

When having influence over more junior members, senior engineers encourage good decision making across the team.

AdamCimarosti
Автор

The whole industry is bs. Nothing but gatekeepers

Dmmesserly
Автор

I have to admit that 1 of the worst things I have to deal with in a daily basis is the chaotic code structure of junior and mid level developers in my projects, and that's why I make an extra effort so that my code is self explanatory and comment it whenever it is not

napapt
Автор

I understand the metric described as a means to provoke the importance of technical communication. But the metric for tiering engineers here is just wrong. By definition, any engineer should surpass the 'senior' level of ability outlined here. If you cannot design and impliment new features from scratch and effectively communicate then you are not an engineer. Higher levels should just be more adept at these things, and their skills should allow them to be more effective.

gavinpayne
Автор

Can't agree with this. A senior dev should have more than simply a soft skill (probably not what OP video meant, but it fragment is so short it makes me think that)

fabianramirez
Автор

just communication? seems not enough idk

trantrungnghia