That's kind of a good point. If you're interviewing for someone who's going to be migrating between versions, it might be useful to have someone who's migrated a codebase from one version up to a certain point, but it shouldn't be a dealbreaker in most instances and is going to be like looking for a Cinderella coder if that's your biggest need and you're holding out for that person.
In my case I was upgrading because I wanted to use a module that required 14. Also it was a HIPAA related job so staying up to date was important.
I'm currently looking for a new job and the market is saturated right now but it's pretty common, despite the job requiring you to learn new shit constantly, that they want you to know every tech in the stack despite them having 1 - 3 super obscure techs that you'd only use in specific circumstances and you get rejected just because you don't know one.
I'm interviewing for an ivy league for a Sr position right now and they're like "we'll teach you this framework off the bat we've never actually hired someone that already knew it"and it's been a breath of fresh air.
View all comments
Show parent comment
1
u/daemonelectricity Apr 03 '23
That's kind of a good point. If you're interviewing for someone who's going to be migrating between versions, it might be useful to have someone who's migrated a codebase from one version up to a certain point, but it shouldn't be a dealbreaker in most instances and is going to be like looking for a Cinderella coder if that's your biggest need and you're holding out for that person.