4 ms·
I'm routinely seeing postings for "Senior XYZ developer" and generally list "you must have at least 3 years of XYZ". I don't recall it being quite this bad 20
by mgkimsal 7y ago
I'm routinely seeing postings for "Senior XYZ developer" and generally list "you must have at least 3 years of XYZ". I don't recall it being quite this bad 20 years ago, but... the market was different. There's a few "stricter" posts that I see that will list 5 or 7 or minimum 10 years of XYZ, but the most I see (when time experience is listed) is 'minimum 3'.
Outside of something like nodejs, I'm not even sure 3 years will get you through the experience of a version upgrade with some tech stacks, let alone "senior" qualifications. But it will all come down to how you define "senior".
- agumonkey 7y agoI also have a dilemma. Spending 3 years in a project using <tech> doesn't mean much to me. Unless it's a serious gig with regular problem solving .. but if it's mostly management hell, documentation, ... you might not know much more than when you came in. I know a lot of things I learned in python on my own wouldn't happen in a job because you don't have time to play with everything in the language.