I think that Engineers are forgetting that practiced skills are easier than experienced skills. being tested on a bunch of weird-ass algorithms and data structu

I think that Engineers are forgetting that practiced skills are easier than experienced skills. being tested on a bunch of weird-ass algorithms and data structures requires an experienced programmer with a traditional education perhaps a few short weeks of studying. this doesn't make these problems hard, it just makes them inconvenient and a poor measure. there are only a handful of Advanced algorithms that I have had to implement from scratch in industry. data structures on the other hand are usually the bottleneck where I find myself needing to be more creative. this is possibly the same category as white boarding, this is not hard just inconvenient. I would even argue that whiteboarding is much more necessary than algorithms problems, as a measure of ability to communicate over a technical Topic over a live edited interim document. the biggest problem against these algorithms and data structures tests, is that they discriminate against those without a traditional academic background. if your company does not often enough run into inability to solve these problems, then you're testing for the wrong thing two things I have found useful in this space, for every interview I ask in advance whether I'm going to be asked to these questions, and I am very specific about what I have experienced in. If any questions are asked outside of my experience I can lay claim, and reference my resume for a lack of note. Every time that I have expose myself as unexperienced in a topic during an interview, the interviewer has changed the question for me