[amorphid]

When I worked as a technical recruiter, I found that a great way to screen candidates was to explain the "box" I was trying to put them in. I described the work I'd done to research the position, why I was screening for certain criteria, and that ultimately I wanted to get their approval on the summary I had written about them. Being non-technical, this worked better for positions I was experienced recruiting for of course.

For example, when recruiting a web developer, I'd start by asking a hiring manager what they wanted.

"Get me a full stack Rails developer who knows OO Javascript."

Then I'd just drill into why they asked for that until I didn' have manh questions. I'd be able to describe roughly what projects needed attention, how the tech stack helped solve that problem, and ask the candidate to help me sell them as someone who can do that. It wasn't perfect, but it worked better than most recruiting attempts I've experienced so far.

Now as a developer with a few years of experience, I feel I have no idea what I am doing, and am winging it at all times :)