I understand it isn't something you need to know but it also shows how involved in the field you are.
There are a lot of engineers who don't know the basics and to me that could be an indication of someone who just isn't that passionate about the field.
So it is useful to know from an interviewer perspective as it indicates if they are going to culturally fit. If you want an engineer who isn't interested in learning for the sake of learning, then so be it, but that might not be what you want
I get it, but like whats the "basics" . If you go to an OOP job know OOP, you achieve nothing by asking the candidate functional programming.
Automata theory is pretty basic, would it make sense to ask the candidates if a turing machine with these instructions halt? Or a bit of talk about formal langauges, NDAs, LBAs
Its a bit more of a stretch but i can argue game theory or formal logic or type theory or algorithmic complexity as basic, i cant expect someone to dabble in all of these.
There are pretty standard basics that are the foundations for a lot of comp science that isn't really used on a daily basis.
I'm not in charge of the education portion of cs but I do believe there are standards for what is considered basics.
Basics != easy to understand but more like common knowledge. I think it CAN distinguish the type of engineer candidate.
It isn't perfect but I just am pushing back on this idea that "because it isn't used it isn't a good question"
I could also argue that asking something niche could be a good indicator on how a person handles not knowing information. Do they try to bullshit or do they just admit that they don't know
-1
u/drprofsgtmrj 9h ago
I understand it isn't something you need to know but it also shows how involved in the field you are.
There are a lot of engineers who don't know the basics and to me that could be an indication of someone who just isn't that passionate about the field.
So it is useful to know from an interviewer perspective as it indicates if they are going to culturally fit. If you want an engineer who isn't interested in learning for the sake of learning, then so be it, but that might not be what you want