I've had so many people tell me that it is unreasonable to ask in an interview "What's the difference between an array and a set?"... Then I ask how they'd feel about reviewing PRs from a person that does not know the difference and they mostly of change their minds about it.
To be fair, it does depend on the question. Yours is fine.
I've also seen things like "Why would you specify the # of elements when initializing an ArrayList in Java?", and you just know the person asking is the guy that sprinkles magic constants all over his code. And gives negative reviews when you don't put random (often relatively small) numbers in yours too.
Instead of hardcoding, you can specify a million configuration variables to be determined at runtime, and shift the responsibility to SRE to draft a deployment plan for that :P
Or test a bartender by ordering a fizzbuzz and see if they're a former software engineer who got fed up with the crunch and left to go work in a bar (something I think all of us have considered at least once).