How do you reject solving these challenges? Do you simply say it like this - no, I won't be solving it? :) Though I'm sure you have a very polite but firm way of saying it.
I don't necessarily reject entirely but I redirect them to fit the context of the job I'm interviewing for, almost always a .NET/C# developer position. For example, I would explain that I would use built-in language features, such as LINQ and generics, to handle sorting, linked lists and so forth. I would emphasize that I don't want to reinvent the wheel when the language offers a rich set of features that have been exhaustively tested.
Thank you, Frank. This is very interesting.
How do you reject solving these challenges? Do you simply say it like this - no, I won't be solving it? :) Though I'm sure you have a very polite but firm way of saying it.
I don't necessarily reject entirely but I redirect them to fit the context of the job I'm interviewing for, almost always a .NET/C# developer position. For example, I would explain that I would use built-in language features, such as LINQ and generics, to handle sorting, linked lists and so forth. I would emphasize that I don't want to reinvent the wheel when the language offers a rich set of features that have been exhaustively tested.
That's a good advice on how to handle this, thank you!