An outside recruiter tried to hire me for my own opening.
They had taken our Shutterstock job post, reworked it, and sent it back to me as a possible fit.
“Are you interested in a Linux Administrator Job?”
Very interested. I was the person hiring for it.
I replied with the obvious question: “Is this for Shutterstock?” Then I forwarded the message internally with the short version of what had happened: external recruiters took our posting, revamped it, and were trying to hire me for the job I was hiring for.
The rewrite had problems. Zenoss had become “Znos.” The official title would be WebOps Administrator or WebOps Developer, depending on the person.
Not that it mattered much.
The rest of the posting made it obvious why I recognized it. It described Linux administration in a high-volume environment with more than 200 servers. It named Puppet, Git, and MCollective. It wanted somebody with open-source experience and said the company would train the person on some of the tools.
It also said the job involved adding equipment such as phones and laptops. That was a strange compression of the opening, but it was sitting beside enough of our actual language to make the source recognizable.
The recruiter called it a Linux Administrator position. I was still describing the official role as WebOps Administrator or WebOps Developer depending on the individual. Those were not two different postings. They were the two titles we might use for the person we hired.
It was one recruiter message, forwarded twice by me. One forward explained that recruiters were trying to hire me for my own opening. The other asked whether the posting was ours and corrected “Znos.”
It did.