|
|
|
|
|
by Bahamut
3259 days ago
|
|
But how do you screen for these things without tipping off to candidates that that is what you are looking for? As soon as you explicitly mention a set of requirements, you will have candidates looking to game interview processes built around those requirements. |
|
Interviewing people about their experience is a traditional way to verify things. E.g. If I'm looking for someone who can solve hard problems I can ask for examples. If they're beginning programmer who just got handed tasks like "code this function"... they will have no good examples.
I can also explain a problem I'm working on and see how the candidate approaches it.
But writing job posting that hides the fact I need someone who can solve hard problems seems silly.