> This actually might not be so nuts if it were clearly a way to evaluate how you handle unfamiliar problems
Why not seek applicants who are familiar with the problems they’ll be regularly encountering for the position you’re trying to fill? And as an employee I’d rather interview for positions that will require me to solve problems I’m familiar with.
Because even if you're familiar with all the tech we use, you're not going to be familiar with the business domain, our cobbled-together solution on top of the tech stack, and the tens or hundreds of thousands of lines of code we nurtured over the past N years.
How you handle unfamiliar stuff is critical when evaluating an engineer. That's like the whole job.
Unless your goal is to churn out copycat CRUD apps and marketing pages your whole life. Then carry on :)
everyone is looking for their flavour of 'full stack' because in the mind of middle managers human resources need to be fluid across organisational projects.
Why not seek applicants who are familiar with the problems they’ll be regularly encountering for the position you’re trying to fill? And as an employee I’d rather interview for positions that will require me to solve problems I’m familiar with.
That’s kinda like the whole point.