this post was submitted on 15 Dec 2025
8 points (90.0% liked)

CSCareerQuestions

1895 readers
1 users here now

A community to ask questions about the tech industry!

Rules/Guidelines

Related Communities

Credits

Icon base by Skoll under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS
 

As in, either at an early age or early in their career.
Because I'm 26 with about 3-4 years of experience (maybe 5 if I count my apprenticeship), and my company keeps reiterating how they promote based on skill and knowledge, and not based on age. I know that I fit the soft skill requirements for senior dev on the internal checklist. And I know that I could absolutely handle the 6-week project that potential Seniors are asked to do, because all of my experience is extremely specialized into the exact current field and position I work at.

So I'm playing with the idea of asking to become a senior next year, because I plan on leaving the company and the title would look good on my resume.

Does anyone around here have experience with doing something like that?

top 2 comments
sorted by: hot top controversial new old
[โ€“] Mikina@programming.dev 3 points 2 weeks ago

I'd say go for it.

I can't speak for development, because I worked in Cybersecurity as a pentester, so it might be different, but my experience is that the main difference is how much oversight you are getting. I've seen super skilled juniors that didn't need any oversight and seniors whose work I'd describe as mediocre.

If you trust in your work, then it's mostly just a fromality that will get you more money. And even then, I'd say the main difference is that if you don't know something, you have to ask for help (which should be ok and encouraged, if it's not extremely often), instead of having someone watching over you (or in my case of pentesting, doing the project with you). In all cases, if someone, senior or not, wasn't sure about something, needed feedback, help with a bug/script or just to discuss something, just asking others was never a problem.

So, yeah, if you fullfill the requirements your work has, then there's not really a reason not to ask for promotion unless you are really insecure in your work and preffer to have more guidance.

I didn't really rush for promotion because I was more comfortable with the leeway it gives me, and not having that much responsibility, but tbh even if I did ask for it it wouldn't really change much - I was already working mostly independend, reliably and had the required knowledge. It has, however, cost me a lot in sallary over the years, so it probably wasn't worth it.

[โ€“] graycube@lemmy.world 2 points 2 weeks ago

It doesn't hurt to ask. Before you do, think about how you will handle possible rejection. What is your next step if they say "not yet"? Will you quit on the spot? Will you try to find out why and focus on resolving any shortcomings they highlight? Will you slog on with the rate race and ask again in 6 months?

Besides the title, why do you want the promotion? Is it the increased responsibility? The money? The challenge? To impress your parents? As a reward for your hard work so far?

Lastly, expertise in a niche does not always translate into broader expertise and experience in a field that could make it easier to find new employment or implement a career refresh. The title might not be as helpful as you hope unless you plan on staying in that niche. And of course, locking in a specialization may not mean changing jobs changes much.

These are just things to ponder. There are no wrong answers. If you asked me for the promotion, as your boss, I'd probably ask you these questions before going to bat to get you the title upgrade.