I think that's the point :)
Just like you'd test an Italian chef by ordering pasta al pomodoro.
I think that's the point :)
Just like you'd test an Italian chef by ordering pasta al pomodoro.
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.
As a restaurant customer, I would prefer a fried egg over a deviled one.
It's weird how different industries work - even if they're both creative ones. If a customer under-specifies what they want, and I just make what I think will wow them rather than what they were thinking of but didn't think to tell me, that's a bad job on my part for not engaging with them and finding out what they actually desired.
You might talk in great detail about SoA design, and the interviewer might be hiring for a monolith, but still respect the acumen, you could still be a great fit.
It doesn't mean the chef's only going to be cooking tasting menus any more than it means the engineer has carte blanche over greenfield design or to rewrite an existing project.
"Assume a female Gallus gallus domesticus lays a capsule containing an unfertilized ovum..."
Efficiently making an egg dish that can be served to customers would be a pass. The standards depend on the restaurant and the chef that does the interview.
Microwave for 3 minutes.
Add chocolate.
I'd be reaching for the polystyrene, spray paint and duck tape. Possibly, a 3D printer to show my technique is up to date.
I suspect I'm far too literal minded for this kind of test but then I'm an engineer.
The man wants to be an egg. The customer gets what he wants.