[softwaredoug]

Maybe an unpopular opinion, 3 is a bit unimportant, if you're hired for one tech skill, it's not a good place to work IMO. The dev-marketing-blogosphere often outpaces reality. Everyone blogs about <cutting-edge-thing> -- with lots of exageration, no doubt. Nobody blogs about <boring-legacy-code-that-works>.

[peregren]

Thanks. I would have thought this also, but then when my team was hiring this year, the interview questions were quite closely linked to our tech stack (which wouldn't have been my preference). Even though we also can end up moving tech stack entirely, between projects.

[withinboredom]

In that case, they were probably looking for someone that could hit the ground running with very little training or onboarding. I’ve been hired for that case before… I was literally pushing code to production my first day on the job, and let go a few months later once the big push was done on the project. It wasn’t worth it and now stack-specific questions are one of my red-flags.