this post was submitted on 17 Sep 2023
90 points (95.9% liked)

Programming

17655 readers
282 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

I've seen people call themselves "senior" after 3 years on the job, other become CTOs in the same time, and others still have a senior title after 20(!) years in the industry yet have a fuckton of technical experience.

I've heard that they are all just titles and opinions from "if you don't have the technical skill you can't call yourself a senior", to "senior and staff are just a feeling, principal is the actual senior" and "staff? above senior? we call that manager".

What's your story? Is there a ladder? Do you feel like you belong on it? Where are you on it? Does it make sense? Did you see major bumps in salary? Did titles count at all?

you are viewing a single comment's thread
view the rest of the comments
[–] Sigmatics@lemmy.ca 5 points 1 year ago

Some countries are shit with titles though and the technical ladder ends at senior. To go higher means being coming a team leader in those countries.

/thread

At some point climbing the career ladder just means taking on vastly different responsibilities. If all you want to do is code, there isn't always the career ladder you might know from big tech. It just ends at senior.

Which doesn't mean that your career end there, your experience is just measured by years of experience and what you achieved, not some title.