Re:A guide to learning algorithms through LeetCode
by fn1 on Monday August 17, 2020 @12:59AM
(#24184142)
I would just keep my confidence. After all your job is to develop, not to solve whiteboard-puzzles.
If you have to solve something, and can't because it's dumb, or partially dumb, then just explain your opinion to the interviewer.
If they weigh that against you, then it's not a good company for you anyway.
Example: An interviewer once asked me details about POSIX-portability of shell-commands in devops-pipelines.
I didn't know the answer, but I had done devops successfully for many years so I replied:
"I'm not sure, but I don't really need to know that, because I put all my scripts in http://shellcheck.net/"
Which was a completely satisfying answer for him and one he didn't hear before. So points for me.
If you have to solve something, and can't because it's dumb, or partially dumb, then just explain your opinion to the interviewer.
If they weigh that against you, then it's not a good company for you anyway.
Example: An interviewer once asked me details about POSIX-portability of shell-commands in devops-pipelines. I didn't know the answer, but I had done devops successfully for many years so I replied: "I'm not sure, but I don't really need to know that, because I put all my scripts in http://shellcheck.net/"
Which was a completely satisfying answer for him and one he didn't hear before. So points for me.