Earlier quoted context omitted.
There's coding interviews and coding interviews. Asking basic questions that will be directly applicable to the job? Sure Filtering for basic knowledge to make sure the candidate isn't lying about their experience? Sure. Examining my thought process and producing working code is a nice-to-have? Sure. Asking me to solve an extremely esoteric problem that has zero relevance to my day-to-day and if the solution I come u…
I run coding interviews. I would never give an esoteric algorithms question, or even really an algorithms question. I have prompts that test very basic concepts and nearly everyone fails. Resume fraud is rampant.
I study hours every day for many years now. I know many complex systems however studying algorithms bore me to tears.
I've built HPC clusters, k8s clusters, Custom DL method, custom high performance file system, low level complex image analysis algorithms, firmware, UIs, custom OS work.
I've done a lot of stuff because I can't help wanting to learn it. But I fail even basic leetcode questions.
Am I a bad engineer?
There seems to be no way for me to show my abilities to companies other than passing a leetcode but at the same time stopping learning DL methods to learn leetcode feels painful. I only want to learn the systems that create the most value for a company.
I imagine if you interviewed me you would think I wrote a fraudulent resume. Not sure how I am supposed to convince someone otherwise though. Perhaps I've been dumb in not working on code that can be seen outside of a company.