Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Is there a senior level position out there waiting for you?
I'm a little wary of this theory this "if years = 3.5 seinorPosition = true", but let's assume that's the case.... why wouldn't you do that thing?
You haven't really given a lot of info that would indicate there's anything else to consider, but career choices and etc involve a lot of other things.
coffeeholic146035dwhichever pays more
C0D46165635dAre you a senior though?
Can you manage a team?
Can you manage the business bullshit and keep it from the team?
Can you plan, implement and deliver major projects inside business timelines?
Also when your resume says 3 years experience, that's not a senior, that's a mid level dev at best, but you do you and good luck.
The-Real-Jack4635dIt's never wrong to switch it up if it doesn't feel right
What @C0D4 said. Personally with my 5 years of professional experience (and some hobbyist stuff before that) I currently see myself as Mid-level.
Some examples for what I consider improvements in myself over the years:
- Years ago I wrote some quite "clever" code, but it has bitten me in the ass to overengineer (and overcomplicate) often enough. Nowadays I also consider whether my colleagues can work with my code (e.g. when I'm on holiday / sick leave) and whether some micro-optimization is worth the reduced readability (or testability or debugability).
- I learned (am learning) to recognise my limits and to ask for help (or say no to a task) before I burn out. However this doesn't mean not to accept challenges.
- Having a better skillset, which you could also call experience. Experience != time.
- I'm still bad at organizing myself and time management, but I'm working on those.
This (and some other stuff) makes me feel mid-level, but I definitely wouldn't call myself senior.
However the senior title in a job description may just be a HR thing, because they don't really know what they want or equate time with actual experience (which is difficult to quantify). Unfortunately that happens rather often.
If you think you're qualified for the things asked for I wouldn't put too much weight on the title. In general I would consider the job title the most meaningless part of a job. "Senior DBA God" is no better than Database plumber, really. Both can be good or shit.
Also if you switch companies every 6 months in this field I would consider it a red flag on your CV. Not when it's once in a while or when you have good reasons for it (e.g. short project based work), but working 3 years at 5 or 6 companies means the risk to lose you before you could make significant contributions is quite high (because it simply takes a while to get used to the codebase, especially on large and old products).