3 ms·
Maybe the recruiter was looking for somebody who used a specific tool rather than someone who knows the fundamentals and could use any tool. In the early 00's,
by Tangaroa 14y ago
Maybe the recruiter was looking for somebody who used a specific tool rather than someone who knows the fundamentals and could use any tool. In the early 00's, I was turned down from a web job after they found out in the interview that I developed web sites using notepad, vim, and text files instead of Dreamweaver. The same thing might have happened to you.
- iamdave 14y agoIf it turns out to be the case, I'll still go to the interview but never work with that recruiter again. We've reached a point in tech now where processes are (nearly) tool agnostic; and to focus on that given the context of the resume (which the role based on my experience in the role with other companies), this is especially true. I don't need to rely on notepad to manipulate CSV data, I can easily use Excel, Sublime or any other tool that can open a comma separated file. So I'm going to softly reject the notion that this recruiter was looking for someone who uses a specific tool. With the experience you mentioned, I can absolutely see why they'd want a certain toolset because perhaps their internal development lifecycle relies on features not present elsewhere. If that's the case with a recruiter, it's entirely their job and responsibility to their candidates to find this out and outline it in a job post to explain this without inundating interested prospects with tool-speak. This could have easily been accomplished, but it wasn't.