I interviewed for a DevOps position last year, and referenced over a decade worth of continuous integration tools, configuration management, business analysis, team management, and engagement, in including many of the watch words such as Puppet, Fireman, Jenkins, was turned down as I had not been actively using Puppet in the previous few months. Sometimes the job requirements are strict.
Oh, don't get me wrong, these things happen. For me it's been a couple of times : more than a decade work with WebLogic, Tomcat, JBoss and GlassFish, but nope, no Websphere, no job (for purely front end jobs.) Or like this: 12 years doing Java/JEE, then I *took a break* and went to do embedded C/C++ work for 4 years. Trying to come back to Java? Nope, you are a C/C++ developer the interviewer or headhunter says.
So it happens, but to me when it happens, I see it as a blessing, a bullet that I dodged. Think of the kind of organization that pigeonholes roles over absurd trivial shit like that? Do you think *you* could not have pumped it up back to Puppet in a few days? Those aren't requirements but some bozo doing word matching against a list of keywords.
Very rarely a stringent requirement like that is really valid, like you need to know PIC assembly to implement this urgent hotfix before our delivery date, you know, shit like that that does not give the person ramp up time.
But something like that is for a consultant position, for an emergency, get-in/get-out kind of a job. For anything more than 6 months, it is ridiculous. Obviously we need to get a paycheck every other week, but in general, not getting picked up for some bullshit like that, I consider that a blessing.