I will see about sticking with the Software Engineer line of titles (I’m discussing whether or not calling myself a ‘Senior’ would be a good choice with some other commenters). It makes more sense and my supervisor had mentioned that she wants the best title that could represent my skills, responsibilities, and desired future jobs on a resume.
Senior is a nontransferable honorific, as in: it does not translate between organizations.
I have had people who were senior in their old organization demoted to junior (aka. they mostly quit) because they could not write a line of code without internet or IDE to save their life, and I have had people come in as junior even though their started programming when they were 12 and could programm circles around most seniors, buy HR decided they had “no experience” after collage (which, in my opinion, boils down to exploitation of cheap labor). I also met a guy who was an good developer but at his company it was a formal requirement to give a talk to advance to senior. Even though he had 15 years of experience at that company non the less, he could never advance because he was afraid of public speaking.
So seniority is at least as much politics as it is skill or responsibility. In my experience, it boils down to whether or not you feel you deserve it. If the answer is yes, then you should see that you get it and that you are treated (paid) accordingly.
I see! I definitely feel that Senior would be applicable for this given position. All of my hang ups were in thinking there was a more defined requirement to be a “Senior”. Between you and my discussions with others, I’ve learned to not worry about that and instead focus more on my knowledge-level and my direct contribution to the Org - both of which I would say are appropriate in this environment.
MrLuemasG@lemmy.world 1 year ago
Thank you!
I will see about sticking with the Software Engineer line of titles (I’m discussing whether or not calling myself a ‘Senior’ would be a good choice with some other commenters). It makes more sense and my supervisor had mentioned that she wants the best title that could represent my skills, responsibilities, and desired future jobs on a resume.
ck_@discuss.tchncs.de 1 year ago
Well, I do have an opinion on that as well.
Senior is a nontransferable honorific, as in: it does not translate between organizations. I have had people who were senior in their old organization demoted to junior (aka. they mostly quit) because they could not write a line of code without internet or IDE to save their life, and I have had people come in as junior even though their started programming when they were 12 and could programm circles around most seniors, buy HR decided they had “no experience” after collage (which, in my opinion, boils down to exploitation of cheap labor). I also met a guy who was an good developer but at his company it was a formal requirement to give a talk to advance to senior. Even though he had 15 years of experience at that company non the less, he could never advance because he was afraid of public speaking.
So seniority is at least as much politics as it is skill or responsibility. In my experience, it boils down to whether or not you feel you deserve it. If the answer is yes, then you should see that you get it and that you are treated (paid) accordingly.
MrLuemasG@lemmy.world 1 year ago
I see! I definitely feel that Senior would be applicable for this given position. All of my hang ups were in thinking there was a more defined requirement to be a “Senior”. Between you and my discussions with others, I’ve learned to not worry about that and instead focus more on my knowledge-level and my direct contribution to the Org - both of which I would say are appropriate in this environment.
ck_@discuss.tchncs.de 1 year ago
Yeah, I tend to agree, the responsibility should definitely warent it.
Good luck with the whole thing, I hope you get a decent bump out of it :)